You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/08/03 23:25:04 UTC

[jira] [Commented] (ARCHETYPE-462) Filter fileNames when creating archetype from existing project

    [ https://issues.apache.org/jira/browse/ARCHETYPE-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652542#comment-14652542 ] 

ASF GitHub Bot commented on ARCHETYPE-462:
------------------------------------------

Github user ptahchiev closed the pull request at:

    https://github.com/apache/maven-archetype/pull/3


> Filter fileNames when creating archetype from existing project
> --------------------------------------------------------------
>
>                 Key: ARCHETYPE-462
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-462
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Creator
>    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.3.4#6332)