You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/07/27 16:32:58 UTC
[jira] Closed: (MNG-607) implement release-pom.xml from design docs
[ http://jira.codehaus.org/browse/MNG-607?page=all ]
John Casey closed MNG-607:
--------------------------
Resolution: Fixed
resolving the remaining release plugin issues in MNG-662
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org