[ http://jira.codehaus.org/browse/MNG-607?page=comments#action_43417 ]
John Casey commented on MNG-607: -------------------------------- 95% complete. Need to switch to newer version of maven-scm to allow us to use a remove command in order to delete release-pom.xml from the HEAD/trunk. I'll revisit this once I've talked to Emmanuel, and he's done with API changes for maven-scm. > implement release-pom.xml from design docs > ------------------------------------------ > > Key: MNG-607 > URL: http://jira.codehaus.org/browse/MNG-607 > Project: Maven 2 > Type: New Feature > Components: maven-plugins, maven-core > Reporter: Brett Porter > Assignee: John Casey > Priority: Blocker > Fix For: 2.0-beta-1 > > > 2 components to this: > - writing the pom during the release plugin and doing the scm operations > - using it instead when present at build time, instead of pom.xml > For the second, I'm not sure if this should be automatic or controlled by a > -f switch. I think it should be automatic, and the -f switch should be > implemented to allow pom.xml to be used when release-pom.xml is there. (As > well as other pom files). > Design: > http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution -- 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]
