You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thorsten Heit (JIRA)" <ji...@codehaus.org> on 2008/12/12 12:25:19 UTC
[jira] Created: (MRELEASE-398) release:prepare: endlessly asking
for the next development version on a multi-module project when not
entering the expected value
release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
---------------------------------------------------------------------------------------------------------------------------------
Key: MRELEASE-398
URL: http://jira.codehaus.org/browse/MRELEASE-398
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-8
Environment: Maven 2.0.9
Windows XP SP3
JDK 1.6.0_11
Reporter: Thorsten Heit
Attachments: release-prepare-patch.txt
I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
\\
{code}(...)
[INFO] Checking dependencies and plugins for snapshots ...
There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
(...){code}
(see also bugs MRELEASE-158 and MRELEASE-269)
The solution for that behaviour is quite easy; see attached patch.
Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
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] (MRELEASE-398) release:prepare: endlessly asking for the
next development version on a multi-module project when not entering the
expected value
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-398.
-----------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.5)
Assignee: Robert Scholte
> release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-398
> URL: https://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
> Reporter: Thorsten Heit
> Assignee: Robert Scholte
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-398) release:prepare: endlessly asking for the
next development version on a multi-module project when not entering the
expected value
Posted by "Antony Stubbs (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315971#comment-315971 ]
Antony Stubbs commented on MRELEASE-398:
----------------------------------------
Great news!
> release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-398
> URL: https://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
> Reporter: Thorsten Heit
> Assignee: Robert Scholte
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-398) release:prepare: endlessly asking
for the next development version on a multi-module project when not
entering the expected value
Posted by "Antony Stubbs (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183605#action_183605 ]
Antony Stubbs commented on MRELEASE-398:
----------------------------------------
I also have this problem. Is there a work-around?
> release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-398
> URL: http://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
> Reporter: Thorsten Heit
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
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-398) release:prepare: endlessly asking
for the next development version on a multi-module project when not
entering the expected value
Posted by "Cliff Evans (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225466#action_225466 ]
Cliff Evans commented on MRELEASE-398:
--------------------------------------
This bug is still in version 2.0. What does it take to get things fixed around here? Thorsten has supplied a patch, is it not good enough? Are there issues with it? Is something more needed? I have no idea because there's no feedback or activity on stuff around here.
> release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-398
> URL: http://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
> Reporter: Thorsten Heit
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
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] Updated: (MRELEASE-398) release:prepare: endlessly asking
for the next development version on a multi-module project when not
entering the expected value
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-398:
-------------------------------------
Component/s: prepare
> release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-398
> URL: http://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
> Reporter: Thorsten Heit
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
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] (MRELEASE-398) release:prepare: endlessly asking for the
next development version on a multi-module project when not entering the
expected value
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-398:
------------------------------------
Fix Version/s: 2.4
For MRELEASE-511 this part of the code will be refactored, so this issue should be fixed as well.
> release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-398
> URL: https://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
> Reporter: Thorsten Heit
> Fix For: 2.4
>
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-398) release:prepare: endlessly asking for the
next development version on a multi-module project when not entering the
expected value
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310000#comment-310000 ]
Robert Scholte commented on MRELEASE-398:
-----------------------------------------
I've tried to fix this issue, but I can't reproduce it.
The code has changed a lot since the patch was created, so there's a reasonable chance this is already fixed.
Would be nice if somebody could verify this, otherwise I'll close it as "Can't reproduce".
> release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-398
> URL: https://jira.codehaus.org/browse/MRELEASE-398
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Maven 2.0.9
> Windows XP SP3
> JDK 1.6.0_11
> Reporter: Thorsten Heit
> Fix For: 2.4
>
> Attachments: release-prepare-patch.txt
>
>
> I'm working on a multi-module project that has dependencies to other modules which were released recently. When trying to release my project, release:prepare doesn't stop asking me for a dependency's next development version as long as I'm entering a version string that doesn't equal the expected one:
> \\
> {code}(...)
> [INFO] Checking dependencies and plugins for snapshots ...
> There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : yes
> Dependency type to resolve,: specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
> Resolve Project Dependency Snapshots.: 'de.ukv.verbund.base:verbund-base' set to release? (yes/no) yes: :
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 2.0.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: : 1.2.0-SNAPSHOT
> What is the next development version? (1.2-SNAPSHOT) 1.2-SNAPSHOT: :
> 'de.ukv.verbund.form:verbund-form' set to release? (yes/no) yes: :
> (...){code}
> (see also bugs MRELEASE-158 and MRELEASE-269)
> The solution for that behaviour is quite easy; see attached patch.
> Note: I've seen this only when the release plugin asks for new versions of snapshot dependencies, not when asking for the new version of the project itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira