You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/12/29 01:10:56 UTC
[jira] Updated: (MNG-1885) Uniquely identify modules by module name
and version number
[ http://jira.codehaus.org/browse/MNG-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-1885:
------------------------------
Fix Version/s: (was: 3.x)
> Uniquely identify modules by module name and version number
> -----------------------------------------------------------
>
> Key: MNG-1885
> URL: http://jira.codehaus.org/browse/MNG-1885
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Design, Patterns & Best Practices
> Environment: This is a platform independent issue. Windows XP, Java builds
> Reporter: John Reynolds
> Priority: Trivial
>
> Currently when buiding project dependencies and/or performing a build via the reactor "-r option" it will not build projects that have the same project id. This works in most unique project scenarios, but in scenarios where you may have the directories for a project broken out by version number, you end up with the same artifact-id for the multiple projects. The only difference would be that they are target at different versions.
> Example Layout
> Project X
> |
> +------Dev (pom.xml contains artifact "ProjectX" version Dev (Dev head contains latest release)
> |
> +------1.0 (pom.xml contains artifact "ProjectX" Version 1.0
> |
> +------2.0 (pom.xml contains artifact "ProjectX" Version 2.0
> We may actually build multiple versions of plug-ins that could be deployed and built as a whole. It would simplify the builds if the "-r" option would build each project and version it finds. Today it will only build one of them.
> The same issue or set of problems is presented to the module concept. It's difficult for a parent project that needs to build multiple projects to point at specific versions. Today they project would require a unique artifact and a module pointing to each directory for the pom. It will only build one of the instances of the artifact ID. This forces changes to the parent pom, to deal with the issue. It would be nice to be able to build a specific version or all the versions related to a module.
> Multi-Project module builds should have the knowledge of versions when deciding what to build, with an option of including specific versions or all versions of an artifactId
> The "-r" reactor option should all directories to be recursed and build multiple projects of the same artifact id, regardless over version.
--
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