[
https://jira.codehaus.org/browse/ARCHETYPE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330505#comment-330505
]
Eric Barber commented on ARCHETYPE-392:
---------------------------------------
I've recently experienced the same problem as Stefan when using m2e 1.4, Oracle
Java 7, and Eclipse 4.3. Even after hardcoding the version to 1.0-SNAPSHOT,
the problem persists. I've used the archetype contained in the attached zip
and can repo this with ease.
Does anyone know of a workaround other than using the command line?
> Multi-module archetype creation substitutes parent groupId and artifactId in
> sub-module even if explicitly set to something different
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARCHETYPE-392
> URL: https://jira.codehaus.org/browse/ARCHETYPE-392
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
> Affects Versions: 2.1
> Environment: Verified on Windows
> Reporter: Stefan Ullrich
> Attachments: test.zip
>
>
> I have an archetype for a multi-module project with 2 sub-modules: one is a
> child of the multi-module project, the other one is the child of a different
> parent pom. The groupId and artifactId of that different parent is explicitly
> written in the archetype's sub-module pom (no variables).
> When creating a project from the archetype both sub-modules turn out to have
> the same parent (the multi-module).
> I have attached a zip-file containing
> _the template multi-module project
> _the archetype generated from that project
> _the archetype-catalog.xml for the archetype
> _the two parents
> _a test project generated with the archetype showing the described Symptoms
> Steps to reproduce:
> 1. Install the parents and the archetype
> 2. Create a test project using the archetype - make sure to use the same
> groupId ("groupId") and version ("1.0-SNAPSHOT") as the parent as it will not
> build otherwise.
> 3. In the created test project look at the pom of the sub-module
> "childModuleProjectWithDifferentParent": the parent is "groupId:test"
> 4. Have a look at the pom of the same sub-module in the archetype: the parent
> is explicitly set to "differentGroupId:differentParent"!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
