[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=188451#action_188451 ] François LEIBER commented on MJAR-28: - Any progress on this? I'm still having the issue with latest available versions of maven (2.2.1) and of all plugins... Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Assignee: John Casey Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=165937#action_165937 ] Dale Wyttenbach commented on MJAR-28: - Currently the Fix Version for this issue is None. In what release is it likely to appear? Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Assignee: John Casey Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105944 ] Todd Nine commented on MJAR-28: --- I'm also experiencing this. We're working on a huge project with about 15 sub projects. This really causes problems with our deployable artifacts. Is there anyone working on it? If not, where would I begin looking to fix this? Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105948 ] Max Bowsher commented on MJAR-28: - Todd: The local workaround that I'm using consists of: 1) Check out maven-archiver-2.2 Apply MNG-2456-maxb.patch Deploy to local organization repository as (e.g.) 2.2-maxb-1 2) Check out maven-jar-plugin-2.1 Change maven-archiver dependency version in pom to 2.2-maxb-1 Deploy to local organization repository as (e.g.) 2.1-maxb-1 3) Reference maven-jar-plugin 2.1-maxb-1 in poms. This is adequate when using maven-assembly-plugin 2.1. maven-assembly-plugin 2.2-beta-1 has broken things again though. (MASSEMBLY-211) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_78430 ]
Martin Desruisseaux commented on MJAR-28:
-
Maybe related to this issue: the manifest classpath generated by Maven ignores
the real JAR name as specified in {{finalName}}. For example the Geotools
project tried the following configuration:
{code:xml}
build
finalNamegt-${artifactId}-${version}/finalName
{code}
but the manifest classpath generated by Maven contains only
{{${artifactId}-${version}.jar}} entries, which are non-existent JARs.
*Note:* this problem happen only when the JAR dependencis come from the
repository. The manifest classpath is correct if all dependencies were compiled
in the same {{mvn install}} cycle.
Using the jar plugin with addClasspath and snapshots can create manifest
classpath with incorrect jar versions
--
Key: MJAR-28
URL: http://jira.codehaus.org/browse/MJAR-28
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Mark J. Titorenko
Attachments: MJAR-28-patch.txt
When the POM contains dependencies to snapshot versions of jars, and snapshot
versions of those jars are downloaded from a remote repository, the name of
the jar contained in the classpath added to the manifest, of the form
artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar
downloaded, which contains version information of the form
artifactID-X.X-MMDD.HHmmss-V.jar.
This does not affect snapshot versions which have been directly installed
into a local repository and have no uploaded version within the remote
repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar
form.
--
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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74197 ] Max Bowsher commented on MJAR-28: - Perhaps this issue should be closed, then, if the problem is located entirely within maven-archiver, and the patch attached here does not relate to the problem described? Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74095 ] Max Bowsher commented on MJAR-28: - Baerrach: Do you mean MJAR-28-patch.txt ? If so, I don't see how it can do that, since it seems mostly to be a tree reorganization and deletion of dead comments and code. Is it possible that the wrong file is attached to JIRA ? Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74100 ] Baerrach bonDierne commented on MJAR-28: Sorry you are right. The changes I needed to make for this are in maven-archiver in the linked issue MNG-2456 as the archiver does all the actual work, jar just invokes archiver. Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74020 ] Max Bowsher commented on MJAR-28: - I do not agree that this issue should be closed. It is true that outputFileNameMapping provides a workaround, but it is only a workaround, not a true fix. I am investigating how to make the jar plugin add the actual timestamped name to the classpath. Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74025 ] Baerrach bonDierne commented on MJAR-28: The patch I provided does just that, for SNAPSHOTS it uses the timestamped version instead of -SNAPSHOT. Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko Attachments: MJAR-28-patch.txt When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_72186 ]
Baerrach bonDierne commented on MJAR-28:
In MASSEMBLY-67 John Casey says
The solution here is to use an outputFileNameMapping such as this:
${artifactId}-${baseVersion}.${extension}
Using ${baseVersion} for cases where you want to preserve the -SNAPSHOT naming,
the plugin retains the ability to use ${version} for the timestamp-buildnumber
naming, which is useful for describing the exact library version included in
the assembly.
(This issue can be closed)
Using the jar plugin with addClasspath and snapshots can create manifest
classpath with incorrect jar versions
--
Key: MJAR-28
URL: http://jira.codehaus.org/browse/MJAR-28
Project: Maven 2.x Jar Plugin
Issue Type: Bug
Affects Versions: 2.0
Reporter: Mark J. Titorenko
Attachments: MJAR-28-patch.txt
When the POM contains dependencies to snapshot versions of jars, and snapshot
versions of those jars are downloaded from a remote repository, the name of
the jar contained in the classpath added to the manifest, of the form
artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar
downloaded, which contains version information of the form
artifactID-X.X-MMDD.HHmmss-V.jar.
This does not affect snapshot versions which have been directly installed
into a local repository and have no uploaded version within the remote
repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar
form.
--
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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_70120 ] Baerrach bonDierne commented on MJAR-28: Most of the comments I have made have been against MASSEMBLY-67 but the bug I believe is definitely in Maven Archiver (no bug has yet been raised for it) MNG-775 doesn't affect this because: - if the artifact is released this bug does not occur - if the artifact is not deployed (only installed) then the correct value is -SNAPSHOT so the only time this problem occurrs is when the artifact is deployed but not yet released. If the artifact is deployed it has been placed in a repository with a timestamped snapshot version (complete with build number) and hence MNG-775 does not apply. My current work around is to manually rename the assembled artifacts to -SNAPSHOT. The notes in MASSEMBLY-67 list the cause of the problem, the use of Project.getRuntimeClasspathElements() instead of using the runtime artifacts. I'm looking into test cases now and should know more by the end of the week. Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Mark J. Titorenko When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_69271 ] Baerrach bonDierne commented on MJAR-28: Woops, I've attached the comments to bug MASSEMBLY-67. Never mind, they are related. Request for advice sent to dev list, see http://www.nabble.com/MJAR-28-Advice-from-dev%3A-Mainfest.mf-Class-Path-entries-by-MavenArchiver%2C-Assembly-and-Jar-tf1908862.html Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Type: Bug Versions: 2.0 Reporter: Mark J. Titorenko When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions
[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_68535 ] Brett Porter commented on MJAR-28: -- yep, the manifest should contain the actual file name (ie, timestamped) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions -- Key: MJAR-28 URL: http://jira.codehaus.org/browse/MJAR-28 Project: Maven 2.x Jar Plugin Type: Bug Versions: 2.0 Reporter: Mark J. Titorenko When the POM contains dependencies to snapshot versions of jars, and snapshot versions of those jars are downloaded from a remote repository, the name of the jar contained in the classpath added to the manifest, of the form artifactID-X.X-SNAPSHOT.jar, does not match the actual name of the jar downloaded, which contains version information of the form artifactID-X.X-MMDD.HHmmss-V.jar. This does not affect snapshot versions which have been directly installed into a local repository and have no uploaded version within the remote repository, as these jars are named using the artifactID-X.X-SNAPSHOT.jar form. -- 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
