[
http://jira.codehaus.org/browse/ARCHETYPE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150514#action_150514
]
Raphaël Piéroni commented on ARCHETYPE-207:
-------------------------------------------
this issue comes from create-from-project
> package with artifactId isn't replaced by archetype:generate
> ------------------------------------------------------------
>
> Key: ARCHETYPE-207
> URL: http://jira.codehaus.org/browse/ARCHETYPE-207
> Project: Maven Archetype
> Issue Type: Bug
> Affects Versions: 2.0-alpha-4
> Reporter: nicolas de loof
> Priority: Minor
>
> On a multimodule project
> (https://platina.svn.sourceforge.net/svnroot/platina/platina-archetype/trunk),
> each module use as convention groupid + artifactid + module as package.
> When used to create an archetype and the generate a new project, the
> generated project still have the orinigal ("archetype") name as package, not
> the expected new project artifactId.
> sample :
> original : com.capgemini.archetype.domain (project artifactId is
> "archetype")
> actual : {groupid}.archetype.domain
> expected : {groupid}.{artifactId}.domain
--
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
