maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brad Szabo (JIRA)" <>
Subject [jira] Updated: (ARCHETYPE-191) Ability to filter filenames (rename files) during project generation
Date Sat, 13 Sep 2008 01:36:49 GMT


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:

Example Generated output (where -DartifactId=sample2 -Dmy-property=arbitrary):

> Ability to filter filenames (rename files) during project generation
> --------------------------------------------------------------------
>                 Key: ARCHETYPE-191
>                 URL:
>             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:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message