Creating archetypes and disabling velocity

Discussion:

Doug Hughes

2009-05-10 03:06:43 UTC

Hi,

I'm in the process of creating my first archetype. I've based it on the
simple-webapp archetype, but I've added the entire ColdFusion application.
This is 4114 files total. I can build and install the archetype just fine
using mvn install just fine. However, when I use mvn archetype:create to
create a new project based on my archetype I get this in the resulting
output:

[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 20] : $coldfusion is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 31] : $tagext is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 38] : $lang is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 43] : $RegistryTag is not a valid reference.
[WARNING] org.apache.velocity.runtime.exception.ReferenceException:
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 62,column 244] : $Lcoldfusion is not a valid reference.
[ERROR] ResourceManager.getResource() parse exception:
org.apache.velocity.exception.ParseErrorException: Lexical error:
org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 206,
column 35. Encountered: <EOF> after : ""

I think that what's going on is that the Velosity templating system is
seeing $ or ${ or something like that in the ColdFusion files. I'm trying
to find a way to tell velosity to ignore these files. Any tips on this?
I've read every line of documentation on the archetype plugin I can find,
but there's no clear answer.

I did find one page which discussed a file called archetype-metadata.xml.
The simple-webapp archetype I based this on didn't have one of these files.
I added it under src/main/resources/META-INF/maven, with the following XML,
but it didn't seem to have any effect at all the next time I tried to create
my archetype:

<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="basic">
<fileSets>
<fileSet filtered="false" packaged="true">
<directory>src/main</directory>
<includes>
<include>**/*.*</include>
</includes>
</fileSet>
</fileSets>
</archetype-descriptor>

I get the impression that there are two versions of the archetype plugin and
that the I might be building my archetype based on documentation on the
archetype 1 plugin and that the archetype-metadata.xml file is specific to
version 2?

Thanks for your help,

Doug Hughes, President
Alagad Inc.
***@alagad.com
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Doug Hughes

2009-05-10 12:58:49 UTC

Permalink

I wanted to add to my last message. I found some instructions on using
archetype:create-from-project to create a new archetype. I followed them to
create a new archetype project. This had a slightly different file layout
than the webapp archetype I was trying to customize before. However, I'm
still having the same problem I did before. Specifically, archetype:create
seems to be trying to send every file through the velocity system.

The archetype:create-from-project did create an archetype-metadata.xml file
which I've modified as such in an attempt to completely remove all filtering
from my archetype.

<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="ColdFusion-archetype">
<fileSets>
<fileSet filtered="false" packaged="true">
<directory>src/main</directory>
<includes>
<include>**/*.cfm</include>
</includes>
</fileSet>
</fileSets>
</archetype-descriptor>

Unfortuantly, when I run archetype:create I'm still getting the same errors
from velocity. Am I going about this the right way? Is there any good
documentation on this stuff? Or maybe a useful book I could buy?

Thanks,

Doug Hughes, President
Alagad Inc.
***@alagad.com
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Post by Doug Hughes
Hi,
I'm in the process of creating my first archetype. I've based it on the
simple-webapp archetype, but I've added the entire ColdFusion application.
This is 4114 files total. I can build and install the archetype just fine
using mvn install just fine. However, when I use mvn archetype:create to
create a new project based on my archetype I get this in the resulting
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 20] : $coldfusion is not a valid reference.
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 31] : $tagext is not a valid reference.
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 38] : $lang is not a valid reference.
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 17,column 43] : $RegistryTag is not a valid reference.
reference : template =
archetype-resources/src/main/webapp/CFIDE/adminapi/_datasource/getaccessdefaultsfromregistry.cfm
[line 62,column 244] : $Lcoldfusion is not a valid reference.
org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line 206,
column 35. Encountered: <EOF> after : ""
I think that what's going on is that the Velosity templating system is
seeing $ or ${ or something like that in the ColdFusion files. I'm trying
to find a way to tell velosity to ignore these files. Any tips on this?
I've read every line of documentation on the archetype plugin I can find,
but there's no clear answer.
I did find one page which discussed a file called archetype-metadata.xml.
The simple-webapp archetype I based this on didn't have one of these files.
I added it under src/main/resources/META-INF/maven, with the following XML,
but it didn't seem to have any effect at all the next time I tried to create
<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="basic">
<fileSets>
<fileSet filtered="false" packaged="true">
<directory>src/main</directory>
<includes>
<include>**/*.*</include>
</includes>
</fileSet>
</fileSets>
</archetype-descriptor>
I get the impression that there are two versions of the archetype plugin
and that the I might be building my archetype based on documentation on the
archetype 1 plugin and that the archetype-metadata.xml file is specific to
version 2?
Thanks for your help,
Doug Hughes, President
Alagad Inc.
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Doug Hughes

2009-05-10 13:13:14 UTC

Permalink

Sorry to keep harping on this topic. I'm hoping someone can offer some
advice. :)

As a last test, I intentionally put invalid XML in the
archetype-metadata.xml file. I was able to run archetype:create without it
reporting an XML error. This tells me it's ignoring my metadata file
anyhow.... any ideas on what I can do to work around this?

Thanks,

Doug Hughes, President
Alagad Inc.
***@alagad.com
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Post by Doug Hughes
I wanted to add to my last message. I found some instructions on using
archetype:create-from-project to create a new archetype. I followed them to
create a new archetype project. This had a slightly different file layout
than the webapp archetype I was trying to customize before. However, I'm
still having the same problem I did before. Specifically, archetype:create
seems to be trying to send every file through the velocity system.
The archetype:create-from-project did create an archetype-metadata.xml file
which I've modified as such in an attempt to completely remove all filtering
from my archetype.
<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="ColdFusion-archetype">
<fileSets>
<fileSet filtered="false" packaged="true">
<directory>src/main</directory>
<includes>
<include>**/*.cfm</include>
</includes>
</fileSet>
</fileSets>
</archetype-descriptor>
Unfortuantly, when I run archetype:create I'm still getting the same errors
from velocity. Am I going about this the right way? Is there any good
documentation on this stuff? Or maybe a useful book I could buy?
Thanks,
Doug Hughes, President
Alagad Inc.
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Martin Gainty

2009-05-10 15:50:46 UTC

Permalink

can you display the maven-metadata.xml (and your project's pom.xml) and display the command you are using which *should* reproduce this error?

thanks,
Martin
______________________________________________
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

Date: Sun, 10 May 2009 09:13:14 -0400
Subject: Re: Creating archetypes and disabling velocity
Sorry to keep harping on this topic. I'm hoping someone can offer some
advice. :)
As a last test, I intentionally put invalid XML in the
archetype-metadata.xml file. I was able to run archetype:create without it
reporting an XML error. This tells me it's ignoring my metadata file
anyhow.... any ideas on what I can do to work around this?
Thanks,
Doug Hughes, President
Alagad Inc.
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

_________________________________________________________________
Hotmail® has ever-growing storage! Dont worry about storage limits.
http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage1_052009

Heinrich Nirschl

2009-05-10 16:41:38 UTC

Permalink

Post by Doug Hughes
As a last test, I intentionally put invalid XML in the
archetype-metadata.xml file. I was able to run archetype:create without it
reporting an XML error. This tells me it's ignoring my metadata file
anyhow.... any ideas on what I can do to work around this?

I think, this file is only used, if you use the archetype:generate goal.

Post by Doug Hughes
[line 17,column 31] : $tagext is not a valid reference.

For the references that should go unchanged into the generated sources
I usually do

#set ($d = "$")

... ${d}{target} ...

This will expand to ${target} and will not raise a warning.

- Henry

Doug Hughes

2009-05-10 17:37:17 UTC

Permalink

Rather than editing my source files, is there not a way to disable
velocity for spcific files or folders? I ask because some of the
problem files in my archetype are binary. I'm not too comfortable
editing those by hand as you suggest. And I think they may be related
to the problems I'm seeing.

Thanks,

Doug

Post by Heinrich Nirschl

I think, this file is only used, if you use the archetype:generate goal.

Post by Doug Hughes
[line 17,column 31] : $tagext is not a valid reference.

For the references that should go unchanged into the generated sources
I usually do
#set ($d = "$")
... ${d}{target} ...
This will expand to ${target} and will not raise a warning.
- Henry
---------------------------------------------------------------------

Heinrich Nirschl

2009-05-10 19:39:31 UTC

Permalink

Rather than editing my source files, is there not a way to disable velocity
for spcific files or folders? I ask because some of the problem files in my
archetype are binary. I'm not too comfortable editing those by hand as you
suggest. And I think they may be related to the problems I'm seeing.

Did you try the filtered="false" attribute in the
archetype-metadata.xml file when you used the archetype:generate goal?

- Henry

Martin Gainty

2009-05-10 20:26:24 UTC

Permalink

how about adding includes for wanted extensions and excludes for files to be excluded
such as this FileSet declaration for archetype-metadata.xml file?

<archetype-descriptor>

<fileSets>
<fileSet filtered="true" packaged="false">
<directory>src/site</directory>
<includes>
<include>**/*.ftl</include>
</includes>
<excludes>
<exclude>**/*.vm</exclude>
</excludes?
</fileSet>
</fileSets>
</archetype-descriptor>

http://ant.apache.org/manual/CoreTypes/fileset.html
?
Martin Gainty
______________________________________________
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
This message is confidential. If you should not be the intended receiver, then we ask politely to report. Each unauthorized forwarding or manufacturing of a copy is inadmissible. This message serves only for the exchange of information and has no legal binding effect. Due to the easy manipulation of emails we cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

Date: Sun, 10 May 2009 21:39:31 +0200
Subject: Re: Creating archetypes and disabling velocity

Rather than editing my source files, is there not a way to disable velocity
for spcific files or folders? I ask because some of the problem files in my
archetype are binary. I'm not too comfortable editing those by hand as you
suggest. And I think they may be related to the problems I'm seeing.

Did you try the filtered="false" attribute in the
archetype-metadata.xml file when you used the archetype:generate goal?
- Henry
---------------------------------------------------------------------

_________________________________________________________________
Hotmail® goes with you.
http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009

Doug Hughes

2009-05-10 21:57:44 UTC

Permalink

Martin,

Thanks for the suggestion.... the thing is, that's what this tread started
about. I have an archetype-metadata.xml file and followed the documentation
(not at the link you provided which, fyi, doesn't document the filtered or
packaged attributes).

Anyhow, it seems that the archetype-metadata.xml file is being ignored. No
mater what I put in that file (including invalid xml), it makes no
difference. It's like the file doesn't even exist.

I'll send more information on the structure of the archetype project and my
various files and the commands I'm running later.

Thanks,

Doug Hughes, President
Alagad Inc.
***@alagad.com
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Post by Martin Gainty
how about adding includes for wanted extensions and excludes for files to be excluded
such as this FileSet declaration for archetype-metadata.xml file?
<archetype-descriptor>

<fileSets>
<fileSet filtered="true" packaged="false">
<directory>src/site</directory>
<includes>
<include>**/*.ftl</include>
</includes>
<excludes>
<exclude>**/*.vm</exclude>
</excludes?
</fileSet>
</fileSets>
</archetype-descriptor>
http://ant.apache.org/manual/CoreTypes/fileset.html
?
Martin Gainty
______________________________________________
Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung/Note
de déni et de confidentialité
This message is confidential. If you should not be the intended receiver,
then we ask politely to report. Each unauthorized forwarding or
manufacturing of a copy is inadmissible. This message serves only for the
exchange of information and has no legal binding effect. Due to the easy
manipulation of emails we cannot take responsibility over the the contents.
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire
informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
de ceci est interdite. Ce message sert à l'information seulement et n'aura
pas n'importe quel effet légalement obligatoire. Étant donné que les email
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.

Date: Sun, 10 May 2009 21:39:31 +0200
Subject: Re: Creating archetypes and disabling velocity

Post by Doug Hughes
Rather than editing my source files, is there not a way to disable

velocity

Post by Doug Hughes
for spcific files or folders? I ask because some of the problem files

in my

Post by Doug Hughes
archetype are binary. I'm not too comfortable editing those by hand as

you

Post by Doug Hughes
suggest. And I think they may be related to the problems I'm seeing.

Did you try the filtered="false" attribute in the
archetype-metadata.xml file when you used the archetype:generate goal?
- Henry
---------------------------------------------------------------------

_________________________________________________________________
Hotmail® goes with you.
http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009

Doug Hughes

2009-05-11 09:40:16 UTC

Permalink

Ok, I managed to get this to work (mostly).

What I did initially that wasn't working was this:

1) I created a new maven project and set it up the way I wanted it to be.
2) I then used archetype:create-from-project to create a new archetype.
3) I went under /target/generated-sources/archetype in my project to see my
generated archetype.
4) In that location I ran mvn install which built and installed the
archetype.
5) I edited the archetype-metadata.xml to remove filtering on all files.
6) I created a new project using archetype:create or archetype:generate

As I stated in previous messages this resulting in the
archetype-metadata.xml file being ignored and all of my project's files
being filtered by velocity.

After a lot of playing around, I noticed that there was a file that was
generated (and not a part of my previous project) underneath this folder:
/src/main/resources/archetype-resources/src/main/resources/META-INF/archetype.xnl.
Note that the extension is xnl (with an n), not xml. I changed this to have
the xml extension and it seems that caused my archetype-metadata file not to
be ingnored. I also have started using only archetype:generate. As of now
running archetype:generate doesn't fail, which is a good start.

I do, however, still have another problem: Every single txt, xml, and java
file in my archetype is being prepended with this:

#set( $symbol_pound = '#' )
#set( $symbol_dollar = '$' )
#set( $symbol_escape = '\' )

This is causing my new project created from the archetype to fail.

This is happening when the archetype is being installed. I'm not sure when
or why, as my archetype-metadata.xml file is supposed to be causing all
files *not* to be filtered:

<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="ColdFusion9Beta">
<fileSets>
<fileSet filtered="false" packaged="false">
<directory>src/main/webapp</directory>
<includes>
<include>**/*.*</include>
</includes>
</fileSet>
</fileSets>
</archetype-descriptor>

Thanks,

Doug Hughes, President
Alagad Inc.
***@alagad.com
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Post by Doug Hughes
Martin,
Thanks for the suggestion.... the thing is, that's what this tread started
about. I have an archetype-metadata.xml file and followed the documentation
(not at the link you provided which, fyi, doesn't document the filtered or
packaged attributes).
Anyhow, it seems that the archetype-metadata.xml file is being ignored. No
mater what I put in that file (including invalid xml), it makes no
difference. It's like the file doesn't even exist.
I'll send more information on the structure of the archetype project and my
various files and the commands I'm running later.
Thanks,
Doug Hughes, President
Alagad Inc.
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Date: Sun, 10 May 2009 21:39:31 +0200
Subject: Re: Creating archetypes and disabling velocity

Post by Doug Hughes
Rather than editing my source files, is there not a way to disable

velocity

Post by Doug Hughes
for spcific files or folders? I ask because some of the problem files

in my

Post by Doug Hughes
archetype are binary. I'm not too comfortable editing those by hand

as you

Post by Doug Hughes
suggest. And I think they may be related to the problems I'm seeing.

Did you try the filtered="false" attribute in the
archetype-metadata.xml file when you used the archetype:generate goal?
- Henry
---------------------------------------------------------------------

_________________________________________________________________
Hotmail® goes with you.
http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009

Raphaël Piéroni

2009-05-11 11:08:41 UTC

Permalink

Hi Doug,

Please raise a jira for the xNl instead of xMl.

One can configure the create-from-project mojo to have the file
unfiltered by default using:
-DarchetypeFilteredExtentions=unknownExtension
which sets the file extension for files that will be filtered. by
default there is java, js, xml and some more i don't remember.

Hope this helps

Raphaël

Post by Doug Hughes
Ok, I managed to get this to work (mostly).
1) I created a new maven project and set it up the way I wanted it to be.
2) I then used archetype:create-from-project to create a new archetype.
3) I went under /target/generated-sources/archetype in my project to see my
generated archetype.
4) In that location I ran mvn install which built and installed the
archetype.
5) I edited the archetype-metadata.xml to remove filtering on all files.
6) I created a new project using archetype:create or archetype:generate
As I stated in previous messages this resulting in the
archetype-metadata.xml file being ignored and all of my project's files
being filtered by velocity.
After a lot of playing around, I noticed that there was a file that was
/src/main/resources/archetype-resources/src/main/resources/META-INF/archetype.xnl.
Note that the extension is xnl (with an n), not xml. I changed this to have
the xml extension and it seems that caused my archetype-metadata file not to
be ingnored. I also have started using only archetype:generate. As of now
running archetype:generate doesn't fail, which is a good start.
I do, however, still have another problem: Every single txt, xml, and java
#set( $symbol_pound = '#' )
#set( $symbol_dollar = '$' )
#set( $symbol_escape = '\' )
This is causing my new project created from the archetype to fail.
This is happening when the archetype is being installed. I'm not sure when
or why, as my archetype-metadata.xml file is supposed to be causing all
<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="ColdFusion9Beta">
<fileSets>
<fileSet filtered="false" packaged="false">
<directory>src/main/webapp</directory>
<includes>
<include>**/*.*</include>
</includes>
</fileSet>
</fileSets>
</archetype-descriptor>
Thanks,
Doug Hughes, President
Alagad Inc.
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Date: Sun, 10 May 2009 21:39:31 +0200
Subject: Re: Creating archetypes and disabling velocity

Post by Doug Hughes
Rather than editing my source files, is there not a way to disable

velocity

Post by Doug Hughes
for spcific files or folders? I ask because some of the problem files

in my

Post by Doug Hughes
archetype are binary. I'm not too comfortable editing those by hand

as you

Post by Doug Hughes
suggest. And I think they may be related to the problems I'm seeing.

Did you try the filtered="false" attribute in the
archetype-metadata.xml file when you used the archetype:generate goal?
- Henry
---------------------------------------------------------------------

_________________________________________________________________
Hotmail® goes with you.
http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009

Doug Hughes

2009-05-11 11:50:44 UTC

Permalink

Thank you! That was extremely helpful!

I used -DarchetypeFilteredExtentions as you recommended and was able to
create my archetype and generate based on this and my new project was setup
perfectly (or so it seems right now).

I've logged the Jira ticket as your requested for the xNl file extension.

Thank,

Doug Hughes, President
Alagad Inc.
***@alagad.com
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Post by RaphaÃ«l PiÃ©roni
Hi Doug,
Please raise a jira for the xNl instead of xMl.
One can configure the create-from-project mojo to have the file
-DarchetypeFilteredExtentions=unknownExtension
which sets the file extension for files that will be filtered. by
default there is java, js, xml and some more i don't remember.
Hope this helps
Raphaël

Post by Doug Hughes
generated archetype.
4) In that location I ran mvn install which built and installed the
archetype.
5) I edited the archetype-metadata.xml to remove filtering on all files.
6) I created a new project using archetype:create or archetype:generate
As I stated in previous messages this resulting in the
archetype-metadata.xml file being ignored and all of my project's files
being filtered by velocity.
After a lot of playing around, I noticed that there was a file that was

/src/main/resources/archetype-resources/src/main/resources/META-INF/archetype.xnl.

Post by Doug Hughes
Note that the extension is xnl (with an n), not xml. I changed this to

have

Post by Doug Hughes
the xml extension and it seems that caused my archetype-metadata file not

Post by Doug Hughes
be ingnored. I also have started using only archetype:generate. As of

now

Post by Doug Hughes
running archetype:generate doesn't fail, which is a good start.
I do, however, still have another problem: Every single txt, xml, and

java

Post by Doug Hughes
#set( $symbol_pound = '#' )
#set( $symbol_dollar = '$' )
#set( $symbol_escape = '\' )
This is causing my new project created from the archetype to fail.
This is happening when the archetype is being installed. I'm not sure

when

Post by Doug Hughes
or why, as my archetype-metadata.xml file is supposed to be causing all
<?xml version="1.0" encoding="UTF-8"?>
<archetype-descriptor name="ColdFusion9Beta">
<fileSets>
<fileSet filtered="false" packaged="false">
<directory>src/main/webapp</directory>
<includes>
<include>**/*.*</include>
</includes>
</fileSet>
</fileSets>
</archetype-descriptor>
Thanks,
Doug Hughes, President
Alagad Inc.
888 Alagad4 (x300)
Office: 919-550-0755
Fax: 888-248-7836

Post by Doug Hughes
Martin,
Thanks for the suggestion.... the thing is, that's what this tread

started