[
http://jira.codehaus.org/browse/MVERSIONS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223757#action_223757
]
Stephen Connolly commented on MVERSIONS-103:
--------------------------------------------
It would be nice if you could write a patch with integration tests that
implements this feature ;-)
> Add a mojo that validates a multimodule project's parent tree
> -------------------------------------------------------------
>
> Key: MVERSIONS-103
> URL: http://jira.codehaus.org/browse/MVERSIONS-103
> Project: Maven 2.x Versions Plugin
> Issue Type: Wish
> Reporter: Bryan Loofbourrow
> Priority: Minor
>
> The ask here is for a mojo which, when run, would product a dump of all
> pom.xml files, in the project tree extending from the current directory, for
> which the specified parent version does not match the version of the actual
> parent pom in source. Whether such a dump is to the console, or to a file in
> target, is immaterial to me, as long as the output can be regex'ed to
> discover a list of offending poms.
> A page of the plugin documentation
> (http://mojo.codehaus.org/versions-maven-plugin/examples/update-child-modules.html)
> says that you will get a Maven build error in this case, but that is only
> true if the referenced pom version does not exist in a repository. It is the
> case when the referenced pom version does exist that I'm interested in.
> For background, here's my situation:
> I have a large, multimodule project. Not only does it release periodically,
> but it also branches, so that different instances of the project, of course
> with distinct version trees, exist on multiple SCM branches. We have internal
> tools to manage the merging of changes between branches. As you can imagine,
> performing branch integration, and making sure that you get the changes you
> want, while keeping the appropriate version tree for the branch you're
> integrating to, is fairly complex. Sometimes it goes wrong. When it does,
> it's highly probable that any incorrect parent version references do exist in
> our corporate repository -- they are, after all, built on the branches on
> which they originated. So the Maven build will not catch this sort of thing.
> It would be nice to have a tool that could tell me when the parent version
> tree of my build is inconsistent, and it seems like something within the
> scope of what the versions plugin is trying to accomplish. Thanks for reading.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
