You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by nklein <no...@gmail.com> on 2009/12/15 02:44:20 UTC

Enabling fileset packaging with archetype-metadata.xml

I trying to set up my Maven archetype so the directory layout for
ActionScript files can be updated through the package setting. This provides
ActionScript with the same functionality available to Java files.

I've read
http://maven.apache.org/plugins/maven-archetype-plugin/advanced-usage.html
and performed a
$ mvn archetype:create-from-project
-Darchetype.properties=../archetype.properties

where the archetype.properties file contains:

archetype.filteredExtensions=as
archetype.languages=ActionScript

When this command is executed, then the archetype-metadata.xml file is
updated so that filtering is enabled for *.as files:

<fileSet filtered=”true” encoding=”UTF-8”>   // packaged defaults to false
    <directory>src/test/flex</directory>
     <includes>
         <include>**/*.as</include>
     </includes>
 </fileSet>

But to get the package setting to be recognized, then the packaged option
also needs to be enabled for this fileset. 

It doesn't seem like I can just update this file to turn on
packaging="true", because then Maven seems to become confused and doesn't
perform directory layout correctly (it prepends the new package name but
doesn't remove the old one in some places but not all); it also isn't a good
idea to be directly modifying Maven's internal XML files. This type of
modification should only be performed through Maven commands.

I have looked through archetype:create-from-project's optional parameters
but haven't found any optional parameter that turns on the packaged
attribute for a particular language (analogous to
archetype.filteredExtensions) that can be added to the properties file. 

Thanks, Norman



-- 
View this message in context: http://old.nabble.com/Enabling-fileset-packaging-with-archetype-metadata.xml-tp26783357p26783357.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Enabling fileset packaging with archetype-metadata.xml

Posted by Raphaël Piéroni <ra...@apache.org>.
Hello Norman,

The property "archetype.languages" is a list of values containing the names
of the directories containing packaged sources.
For you example this could be "archetype.languages=flex"

Regards,

Raphaël


2009/12/15 nklein <no...@gmail.com>

>
> I trying to set up my Maven archetype so the directory layout for
> ActionScript files can be updated through the package setting. This
> provides
> ActionScript with the same functionality available to Java files.
>
> I've read
> http://maven.apache.org/plugins/maven-archetype-plugin/advanced-usage.html
> and performed a
> $ mvn archetype:create-from-project
> -Darchetype.properties=../archetype.properties
>
> where the archetype.properties file contains:
>
> archetype.filteredExtensions=as
> archetype.languages=ActionScript
>
> When this command is executed, then the archetype-metadata.xml file is
> updated so that filtering is enabled for *.as files:
>
> <fileSet filtered=”true” encoding=”UTF-8”>   // packaged defaults to false
>    <directory>src/test/flex</directory>
>     <includes>
>         <include>**/*.as</include>
>     </includes>
>  </fileSet>
>
> But to get the package setting to be recognized, then the packaged option
> also needs to be enabled for this fileset.
>
> It doesn't seem like I can just update this file to turn on
> packaging="true", because then Maven seems to become confused and doesn't
> perform directory layout correctly (it prepends the new package name but
> doesn't remove the old one in some places but not all); it also isn't a
> good
> idea to be directly modifying Maven's internal XML files. This type of
> modification should only be performed through Maven commands.
>
> I have looked through archetype:create-from-project's optional parameters
> but haven't found any optional parameter that turns on the packaged
> attribute for a particular language (analogous to
> archetype.filteredExtensions) that can be added to the properties file.
>
> Thanks, Norman
>
>
>
> --
> View this message in context:
> http://old.nabble.com/Enabling-fileset-packaging-with-archetype-metadata.xml-tp26783357p26783357.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>