[ http://jira.codehaus.org/browse/MNG-1063?page=comments#action_50709 ]
John Casey commented on MNG-1063: --------------------------------- the release pom was meant to create a completely static build, to enable reproduction of a particular release's build from SCM if needed...without pollution from any changes in the environment post-release (or pre-release-where-env-is-stale, I suppose). The prompt/warning when using the release-pom.xml for release:perform is meant to keep people from releasing a completely static POM. It's possible to build using the release pom, and specify a different pom file to deploy (eg. the regular pom.xml) using a configuration parameter...but I can see where this ability is a bit dangerous. If we have the release-pom generation turned off by default (as it currently is in SVN, IIRC), then none of this is an issue, right? > 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]
