Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
2.0.4, 2.0.5, 2.0.6, 2.0.7
-
None
-
None
-
None
Description
<version>[1.1.0,)</version>
This version range can resolve to the latest dev SNAPSHOT which causes the release plugin to fail due to a SNAPSHOT dependency. The release plugin should check that the original version specification includes a non-SNAPSHOT version (1.1.0) and so can be released without harm.
Attachments
Issue Links
Activity
John Andrunas
made changes -
Admin-Comment-Bulk Update Author | [ markh#1 ] | [ Mark Hobson ] |
John Andrunas
made changes -
Admin-Comment-Bulk Update Author | [ Mark Hobson ] | [ Mark Hobson ] |
Mark Thomas
made changes -
Workflow | jira [ 12950007 ] | Default workflow, editable Closed status [ 12986221 ] |
Mark Thomas
made changes -
Project Import | Sun Apr 05 21:45:26 UTC 2015 [ 1428270326204 ] |
Mark Thomas
made changes -
Workflow | jira [ 12713021 ] | Default workflow, editable Closed status [ 12752854 ] |
Mark Thomas
made changes -
Project Import | Sun Apr 05 08:49:45 UTC 2015 [ 1428223785911 ] |
Mark Hobson
made changes -
Mark Hobson
made changes -
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
brianfox
made changes -
Summary | Release prepare fails with version ranges | version ranges can include snapshots |
brianfox
made changes -
Key | MRELEASE-134 |
|
Project | Maven 2.x Release Plugin [ 11144 ] | Maven 2 [ 10500 ] |
Affects Version/s | 2.0.7 [ 13138 ] | |
Affects Version/s | 2.0.4 [ 12527 ] | |
Affects Version/s | 2.0.5 [ 12294 ] | |
Affects Version/s | 2.0-beta-4 [ 12367 ] | |
Affects Version/s | 2.0.6 [ 13010 ] |
Dave Hoffer
made changes -
Mike Perham
created issue -