Multiple <versions> tags not allowed in RC-1 (Duplicated tag: 'project')
------------------------------------------------------------------------
Key: MAVEN-1825
URL: http://jira.codehaus.org/browse/MAVEN-1825
Project: Maven 1.x
Issue Type: Bug
Affects Versions: 1.1-rc1
Reporter: G.J. Sterenborg
We have combined multiple modules into components:
* component 1
root-module-generic -- project-descriptor (project.xml,project.properties)
-- sub-module-1
-- sub-module-2
-- ...
* component 2
root-module-specific -- project-descriptor (project.xml,project.properties)
-- generic-component-descriptor
(project.xml,project.properties)
-- sub-module-1
-- sub-module-2
-- ...
* component 3
root-module-specific2-- project-descriptor (project.xml,project.properties)
-- generic-component-descriptor
(project.xml,project.properties)
-- sub-module-1
-- sub-module-2
-- ...
* ...
Every module is released seperately in one big 'component-release'.
This component-release checks if a module has changed since the last release
and if so ups the version (and adds a <version>-entry to module's pom.)
Sub-modules <extend> root-module and the root-pom extends all dependent
component-descriptors.
The root-pom is specifies the component-version.
Every module gets it's own version and cvs-tag (including root-pom for the
component-version.)
After testing RC-1, seeing the 'Duplicated tag: 'project'' error and reading:
http://www.mail-archive.com/users@maven.apache.org/msg55210.html
I'm very surprised that tag duplication in parent/child modules isn't allowed
anymore.
Doesn't the parent-pom specify the entire project and the sub-module-poms their
own?
--
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
