[jira] Commented: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
[
http://jira.codehaus.org/browse/MNG-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=134770#action_134770
]
manuel aldana commented on MNG-2456:
i got same problem. for the start i workarounded this by setting
uniqueVersionfalse/uniqueVersion in distribution management for snapshots.
Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
snapshots
Key: MNG-2456
URL: http://jira.codehaus.org/browse/MNG-2456
Project: Maven 2
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.0.4
Reporter: Barrie Treloar
Assignee: Kenney Westerhof
Fix For: 2.0.x
Attachments: MNG-2456-maxb.patch, MNG-2456-patch.txt,
MNG-2456-step1-refactoring-patch.txt,
MNG-2456-step2-add-test-cases-patch.txt, MNG-2456-step3-fix-bug-patch.txt
See related problems MJAR-28 and MASSEMBLY-67.
Summary:
The Maven-Archiver uses the file part of the artifact's filename to create
the Class-Path entries in the Manifest.
This works fine for released artifacts and non-deployed snapshot.
The problem occurs when using a deployed snapshot as the assembly plugin will
copy the dependency as ${artifactId}-${version}-timestampedversion.jar and
the entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
thus use of java -jar jarfile will fail because of the differing names.
--
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: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
[
http://jira.codehaus.org/browse/MNG-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126536
]
Brian Fox commented on MNG-2456:
Can someone produce an IT for this?
Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
snapshots
Key: MNG-2456
URL: http://jira.codehaus.org/browse/MNG-2456
Project: Maven 2
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.0.4
Reporter: Barrie Treloar
Assignee: Kenney Westerhof
Fix For: 2.0.x
Attachments: MNG-2456-maxb.patch, MNG-2456-patch.txt,
MNG-2456-step1-refactoring-patch.txt,
MNG-2456-step2-add-test-cases-patch.txt, MNG-2456-step3-fix-bug-patch.txt
See related problems MJAR-28 and MASSEMBLY-67.
Summary:
The Maven-Archiver uses the file part of the artifact's filename to create
the Class-Path entries in the Manifest.
This works fine for released artifacts and non-deployed snapshot.
The problem occurs when using a deployed snapshot as the assembly plugin will
copy the dependency as ${artifactId}-${version}-timestampedversion.jar and
the entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
thus use of java -jar jarfile will fail because of the differing names.
--
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: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_84865 ]
Christian Goetze commented on MNG-2456:
---
I would like to see a fix that does not involve adding extra configuration
items to the assembly... whatever happened to convention instead of
configuration - and yes, the onus is on -you- to determine which behaviour
should be standard...
Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
snapshots
Key: MNG-2456
URL: http://jira.codehaus.org/browse/MNG-2456
Project: Maven 2
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.0.4
Reporter: Baerrach bonDierne
Assigned To: Kenney Westerhof
Attachments: MNG-2456-maxb.patch, MNG-2456-patch.txt,
MNG-2456-step1-refactoring-patch.txt,
MNG-2456-step2-add-test-cases-patch.txt, MNG-2456-step3-fix-bug-patch.txt
See related problems MJAR-28 and MASSEMBLY-67.
Summary:
The Maven-Archiver uses the file part of the artifact's filename to create
the Class-Path entries in the Manifest.
This works fine for released artifacts and non-deployed snapshot.
The problem occurs when using a deployed snapshot as the assembly plugin will
copy the dependency as ${artifactId}-${version}-timestampedversion.jar and
the entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
thus use of java -jar jarfile will fail because of the differing names.
--
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: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_74484 ]
Max Bowsher commented on MNG-2456:
--
I think the true issue is in the core component maven-artifact-manager, in the
DefaultArtifactResolver class - which, in the case of a snapshot version,
explicitly overrides the artifact's file property from the version name to
the baseVersion name. Search for the line artifact.setFile( copy ); to find
the relevant place in the code. I suggest that that line should simply be
deleted, allowing artifact.getName() to remain returning the version name.
Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
snapshots
Key: MNG-2456
URL: http://jira.codehaus.org/browse/MNG-2456
Project: Maven 2
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.0.4
Reporter: Baerrach bonDierne
Attachments: MNG-2456-patch.txt,
MNG-2456-step1-refactoring-patch.txt,
MNG-2456-step2-add-test-cases-patch.txt, MNG-2456-step3-fix-bug-patch.txt
See related problems MJAR-28 and MASSEMBLY-67.
Summary:
The Maven-Archiver uses the file part of the artifact's filename to create
the Class-Path entries in the Manifest.
This works fine for released artifacts and non-deployed snapshot.
The problem occurs when using a deployed snapshot as the assembly plugin will
copy the dependency as ${artifactId}-${version}-timestampedversion.jar and
the entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
thus use of java -jar jarfile will fail because of the differing names.
--
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: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_74198 ]
Max Bowsher commented on MNG-2456:
--
I think this issue should be reopened. It is true that an outputFileNameMapping
can provide a workaround, but that's only a workaround, not a fix.
Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
snapshots
Key: MNG-2456
URL: http://jira.codehaus.org/browse/MNG-2456
Project: Maven 2
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.0.4
Reporter: Baerrach bonDierne
Attachments: MNG-2456-patch.txt,
MNG-2456-step1-refactoring-patch.txt,
MNG-2456-step2-add-test-cases-patch.txt, MNG-2456-step3-fix-bug-patch.txt
See related problems MJAR-28 and MASSEMBLY-67.
Summary:
The Maven-Archiver uses the file part of the artifact's filename to create
the Class-Path entries in the Manifest.
This works fine for released artifacts and non-deployed snapshot.
The problem occurs when using a deployed snapshot as the assembly plugin will
copy the dependency as ${artifactId}-${version}-timestampedversion.jar and
the entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
thus use of java -jar jarfile will fail because of the differing names.
--
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: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots
[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_71722 ]
Baerrach bonDierne commented on MNG-2456:
-
Oops. Classpath is missing file extension...
Need to update tests and repatch.
Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
snapshots
Key: MNG-2456
URL: http://jira.codehaus.org/browse/MNG-2456
Project: Maven 2
Issue Type: Bug
Components: maven-archiver
Affects Versions: 2.0.4
Reporter: Baerrach bonDierne
Attachments: MNG-2456-step1-refactoring-patch.txt,
MNG-2456-step2-add-test-cases-patch.txt, MNG-2456-step3-fix-bug-patch.txt
See related problems MJAR-28 and MASSEMBLY-67.
Summary:
The Maven-Archiver uses the file part of the artifact's filename to create
the Class-Path entries in the Manifest.
This works fine for released artifacts and non-deployed snapshot.
The problem occurs when using a deployed snapshot as the assembly plugin will
copy the dependency as ${artifactId}-${version}-timestampedversion.jar and
the entry in the Class-Path will be ${artifactId}-${version}-SNAPSHOT
thus use of java -jar jarfile will fail because of the differing names.
--
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
