Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Cannot Reproduce
-
2.0-beta-8
-
None
-
None
-
Maven 2.0.9
Windows XP SP3
JDK 1.6.0_11
-
Patch
Description
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:
(...) [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: : (...)
(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.
Attachments
Attachments
Issue Links
- relates to
-
-
- Closed
-