You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dmitriy Volk (JIRA)" <ji...@codehaus.org> on 2014/05/31 02:46:10 UTC

[jira] (ARCHETYPE-455) Flexible Modulename

    [ https://jira.codehaus.org/browse/ARCHETYPE-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=347335#comment-347335 ] 

Dmitriy Volk commented on ARCHETYPE-455:
----------------------------------------

Would there be an explanation why it's a bad idea to do what Michael suggests? Or is there any chance to see this fixed? I seem to be the only other person in the world who needs this flexibility, but I need it really bad :)

> Flexible Modulename
> -------------------
>
>                 Key: ARCHETYPE-455
>                 URL: https://jira.codehaus.org/browse/ARCHETYPE-455
>             Project: Maven Archetype
>          Issue Type: Wish
>          Components: Generator
>            Reporter: Michael Kopf
>         Attachments: archetype-common-flex-module-name.patch, archetype-multi-module-project-1.1.jar
>
>
> I have to create a multi-module project from maven-archetype with free configurable modulenames. This should be possible with required properties in the archetype.
> Up to now this is only possible with artifactId or rootArtifactId and you have to use it in form of prefix__rootArtifactId__postfix for the module directory.
> What I want is to set a required property while setting up the new project with the archetype. Within the archetype you have to configure the module with directory __yourproperty__ and in the archetype-metadata.xml the module entry like as follows: 
> {code}
> <module id="${yourproperty}" dir="__yourproperty__" name="${yourproperty}">
> {code}
> I made a patch which works for me.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)