[ http://jira.codehaus.org/browse/MNG-1063?page=comments#action_50165 ]
Brett Porter commented on MNG-1063:
-----------------------------------
actually, no need to fill in the super pom - the modelVersion will control that.
currently, it warns about the deployed version having fixed versions when using
the release pom. This is an issue - we do not want that to be the case. Some
more thought is needed here. Perhaps release:perform, using deploy, defaults to
not using the release-pom, while generally building from a checkout defaults to
using it (ie, commit the release pom containing resolved versions, but
release:perform would use -f pom.xml).
Another thought is to revisit why we had release pom. If it is in fact just the
versions, then we could go back to populating an extra version tag (eg
suggestedVersion) that would be used as the suggested version in conjunction
with the given range.
The release pom was meant to capture any other environmental influences at the
time, however we don't really have a way to tell which of those actually modify
the build and which should be retained (eg profiles that attach artifacts,
${basedir}, etc).
> release-pom is changed too much
> -------------------------------
>
> Key: MNG-1063
> URL: http://jira.codehaus.org/browse/MNG-1063
> Project: Maven 2
> Type: Bug
> Components: maven-release-plugin
> Reporter: Brett Porter
>
>
> this needs a full review.
> Expressions are populated that shouldn't be (only external settings should be
> filled in, but not those like basedir or are otherwise path dependant like
> project.file...)
> basically need to use the pre-interpolation, post inheritence pom... or can
> we live with the original one without inheritence and just fill in resolved
> versions?
--
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, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
