You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Baerrach bonDierne (JIRA)" <ji...@codehaus.org> on 2007/01/02 03:31:09 UTC
[jira] Created: (MRELEASE-188) release:perform is not updating some
modules to the next version identifier correctly.
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: Baerrach bonDierne
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
[jira] Closed: (MRELEASE-188) release:perform is not updating some
modules to the next version identifier correctly.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-188) release:perform is not updating
some modules to the next version identifier correctly.
Posted by "Baerrach bonDierne (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=comments#action_83779 ]
Baerrach bonDierne commented on MRELEASE-188:
---------------------------------------------
After modifying my pom to look like:
{noformat}
<dependency>
<groupId>abc</groupId>
<artifactId>abc-abcdefgh-abcdefghijklm-ancdefg</artifactId>
<version>0.4-SNAPSHOT</version>
<type>ejb</type>
</dependency>
{noformat}
the version was correctly updated to have the -SNAPSHOT removed.
> 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: Baerrach bonDierne
>
> 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
[jira] Commented: (MRELEASE-188) release:perform is not updating
some modules to the next version identifier correctly.
Posted by "Baerrach bonDierne (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=comments#action_83774 ]
Baerrach bonDierne commented on MRELEASE-188:
---------------------------------------------
I think it may be because of the formatting of the pom...
Here is a copy of my pom with names changed to protect the guilty...
{noformat}
<dependency>
<groupId>abc</groupId>
<artifactId>
abc-abcdefgh-abcdefghijklm-ancdefg
</artifactId>
<version>0.4-SNAPSHOT</version>
<type>ejb</type>
</dependency>
<dependency>
<groupId>abc</groupId>
<artifactId>abc-abcde-abcdefgh</artifactId>
<version>0.4</version>
</dependency>
{noformat}
The one that is multi-line is the one that always appears to have the problem.
> 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: Baerrach bonDierne
>
> 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
[jira] Commented: (MRELEASE-188) release:perform is not updating
some modules to the next version identifier correctly.
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93594 ]
Emmanuel Venisse commented on MRELEASE-188:
-------------------------------------------
I don't consider an artifactId written on multiple lines is correct. But if you consider it's correct too, I'll let you fix it ;)
> 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: Barrie Treloar
>
> 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
[jira] Reopened: (MRELEASE-188) release:perform is not updating
some modules to the next version identifier correctly.
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barrie Treloar reopened MRELEASE-188:
-------------------------------------
Assigning to me to look into.
> 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: Barrie Treloar
>
> 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
[jira] Closed: (MRELEASE-188) release:perform is not updating some
modules to the next version identifier correctly.
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed MRELEASE-188.
-------------------------------------
Assignee: Emmanuel Venisse
Resolution: Won't Fix
> 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: Emmanuel Venisse
>
> 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
[jira] Commented: (MRELEASE-188) release:perform is not updating
some modules to the next version identifier correctly.
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93668 ]
Barrie Treloar commented on MRELEASE-188:
-----------------------------------------
Fair enough.
I vaguely remember something about text data of XML tags to allow whitespace before and after the text.
It should at the least fail with an error, but I don't remember it doing so, it just failed to transform the file correctly.
> 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: Barrie Treloar
>
> 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
[jira] Commented: (MRELEASE-188) release:perform is not updating
some modules to the next version identifier correctly.
Posted by "Barrie Treloar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93537 ]
Barrie Treloar commented on MRELEASE-188:
-----------------------------------------
Would you be able to comment on why this has been closed as won't fix?
The problem is a valid one poms that have their artifactIds span multiple lines:
<artifactId>
abc-abcdefgh-abcdefghijklm-ancdefg
</artifactId>
This will cause transformation issues.
> 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: Emmanuel Venisse
>
> 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