[ 
http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Bentmann closed MRELEASE-188.
--------------------------------------

         Assignee: Benjamin Bentmann  (was: Barrie Treloar)
       Resolution: Duplicate
    Fix Version/s: 2.0-beta-8

Done by applying a patch from MRELEASE-267.

bq. I don't consider an artifactId written on multiple lines is correct.
Compare [XML Specification 1.0, 2.10 White Space 
Handling|http://www.w3.org/TR/REC-xml/#sec-white-space]. The POM XSD is not 
using {{xml:space="preserve"}} and the {{MavenXpp3Reader}} is indeed trimming 
the text for those elements so the Release Plugin should not break with this.


> release:perform is not updating some modules to the next version identifier 
> correctly.
> --------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-188
>                 URL: http://jira.codehaus.org/browse/MRELEASE-188
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>            Reporter: Barrie Treloar
>            Assignee: Benjamin Bentmann
>             Fix For: 2.0-beta-8
>
>
> For some reason the release:prepare is not correctly removing -SNAPSHOT from 
> some module files, most of them have been correctly transformed only one has 
> not been.
> I am manually double checking whether the tagged version of the file has been 
> modified correctly prior to running release:perform.
> I hope to put together a test case for this problem.  I'm not sure why it is 
> occurring and without a test case it will be impossible for someone else to 
> resolve.
> Work around:
> If there is an error, copy the pom.xml to a safe place.
> From the CVS History get the contents of the tagged version for release and 
> then make the necessary modifications and commit them. The file then needs to 
> be retagged to use the release tag.
> Now copy back the contents of the saved pom.xml, which contains the version 
> id's updated to the next snapshot identifiers. Make sure to fix the same 
> versions that had problems as above to the correct new snapshot value.

-- 
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

        

Reply via email to