Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: maven-archiver
-
Labels:None
-
Number of attachments :
Description
If you have a version range for one of your dependencies, then the exported POM (the one that's placed in the repository and in the jar itself) will still have a range there. This seems at odds with (one) point of exporting a POM, which is to have all the information you need to reconstruct the state of a build at a particular moment in time. Without knowing which version number was chosen, you can't be sure you're reconstructing the same build later.
It also seems to be at odds with the behavior elsewhere in this exported artifact: the plugins section shows the actual version number used, and active profiles are quietly merged into the main POM.
Activity
Vincent Massol
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Workflow | Maven [ 46607 ] | Maven New [ 48169 ] |
John Casey
made changes -
| Fix Version/s | 2.0.5 [ 12294 ] |
Kenney Westerhof
made changes -
| Fix Version/s | 2.0.5 [ 12294 ] | |
| Fix Version/s | 2.0.6 [ 13010 ] |
Jason van Zyl
made changes -
| Fix Version/s | 2.0.6 [ 13010 ] | |
| Fix Version/s | 2.0.x [ 13141 ] |
Brett Porter
made changes -
| Component/s | maven-archiver [ 13268 ] | |
| Project | Maven 2 [ 10500 ] | Maven Shared Components [ 11761 ] |
| Component/s | maven-archiver [ 11520 ] | |
| Fix Version/s | 2.0.x [ 13141 ] | |
| Affects Version/s | 2.0.2 [ 12125 ] | |
| Key | MNG-2007 | MSHARED-40 |