[
http://jira.codehaus.org/browse/ARCHETYPE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Szabo updated ARCHETYPE-191:
---------------------------------
Attachment: ReplaceAnyContextPropertyEnhancement.patch
Here is a patch that improves upon the token replacement to work with any
available context properties (not just {{artifactId}} & {{rootArtifactId}}). It
includes a test.
With this patch, any properties that are set can be used.
Example Archetype file:
{noformat}
example-archetype/src/main/resources/archetype-resources/module1/src/main/resources/__my-property__.properties
{noformat}
Example Generated output (where -DartifactId=sample2 -Dmy-property=arbitrary):
{noformat}
sample2/module1/src/main/resources/arbitrary.properties
{noformat}
> Ability to filter filenames (rename files) during project generation
> --------------------------------------------------------------------
>
> Key: ARCHETYPE-191
> URL: http://jira.codehaus.org/browse/ARCHETYPE-191
> Project: Maven Archetype
> Issue Type: New Feature
> Components: Generator
> Affects Versions: 2.0-alpha-3
> Reporter: Wendy Smoak
> Fix For: 2.0-alpha-4
>
> Attachments: ReplaceAnyContextPropertyEnhancement.patch
>
>
> When generating a new project from an archetype, I need to filter not only
> values within files, but the names of the files themselves.
> For example, in .NET projects, the project files (.sln, .csproj) match the
> name of the solution or project rather than having a fixed name like Maven's
> pom.xml does.
> Another user raised a similar issue on the mailing list, the ability to
> filter in the name of Java source code files.
> See: http://www.nabble.com/Archetype%2C-define-file-name-ts18430983.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
