[
http://jira.codehaus.org/browse/MNG-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268464#action_268464
]
Edward Staub commented on MNG-624:
----------------------------------
Dennis, sorry, I wasn't clear. I know about the release plugin.
Regardless of automation of the editing itself, for large workspaces, this is
not a good solution.
See
http://stackoverflow.com/questions/6109814/when-should-mvn-release-be-used-in-the-project-lifecycle
for the problems with bulk-renumbering as seen by a current and apparently
experienced Maven user.
We put out three numbered builds a week, and have hundreds of projects. The
numbers are used to track where defects are found and where they are fixed -
snapshots are not an option, unless we use snapshots with some other numbering
system. A need to change hundreds of POMs - automated or not - on every build
is not likely to be well-received. Just the accumulation of 10,000+ junk POM
versions per year in the version-control system is even a bit of a problem.
> automatic parent versioning
> ---------------------------
>
> Key: MNG-624
> URL: http://jira.codehaus.org/browse/MNG-624
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Inheritance and Interpolation
> Reporter: Brett Porter
> Assignee: Ralph Goers
> Priority: Blocker
> Fix For: 3.1
>
> Attachments: MNG-624-maven-2.0.x-r507648.patch, MNG-624-tests.tar.gz
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> (this may be bumped to 2.1 or even made WON't FIX as it is contentious - see
> MNG-521)
> currently, you have to specify the parent version when extending which makes
> a project stand alone very easily, but has the drawback of being a
> maintainance problem when you start development on a new version. Tools can
> help, but it would be nice not to have to rely on them.
> One alternative is to allow the parent version to be omitted, and when it is
> it is assumed you want the latest. The parent is used from the reactor or the
> universal source directory. IT may also be read from a LATEST in the
> repository though this is contentious - it may be better to simply fail in
> that environment and require builds be in a known checkout structure for
> building individual projects.
> This also introduces the need for tool support to populate the version on
> release and deployment for reproducibility.
--
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
