[
https://jira.codehaus.org/browse/ARCHETYPE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351482#comment-351482
]
Petar Tahchiev commented on ARCHETYPE-462:
------------------------------------------
Here's the pull request:
https://github.com/apache/maven-archetype/pull/3
> Filter fileNames when creating archetype from existing project
> --------------------------------------------------------------
>
> Key: ARCHETYPE-462
> URL: https://jira.codehaus.org/browse/ARCHETYPE-462
> Project: Maven Archetype
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Petar Tahchiev
>
> Hi guys,
> i'm trying to create an archetype from an existing project. Some of my
> classes are named xxxProduct where I would like to xxx to be replaced by a
> custom property from the client. That's why I have defined my custom property
> in the {{archetype.properties}} file:
> {code}
> project-name=xxx
> {code}
> It all works great - the class name becomes {{WhateverISpecifyProduct}} but
> the filename is still {{xxxProduct.java}}. I have created a simple pull
> request to allow also the filenames to be filtered with custom properties.
> Please review it and merge if everything is OK.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
