You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mike Power (JIRA)" <ji...@codehaus.org> on 2010/01/08 17:27:56 UTC
[jira] Created: (MSHARED-140) MANEFEST class path attribute uses
repository style name despite setting classpathMavenRepositoryLayout to
false
MANEFEST class path attribute uses repository style name despite setting classpathMavenRepositoryLayout to false
----------------------------------------------------------------------------------------------------------------
Key: MSHARED-140
URL: http://jira.codehaus.org/browse/MSHARED-140
Project: Maven Shared Components
Issue Type: Bug
Components: maven-archiver
Environment: Ubuntu 9.04 64bit
Reporter: Mike Power
Attachments: pom.xml
I ran into this while porting a windows maven build to linux. Thanks to all your guy's work is was very error free.
However I did run into one problem where I was getting class not found exceptions for ejb.
After digging in deep I found our MANIFEST.MF file looked something like this:
Class-Path: someintuitlib-ejb-1.0-20090513.083158-9-client.jar
As opposed to windows where it looked like:
Class-Path: someintuitlib-ejb-1.0-SNAPSHOT-client.jar
When the jars are wrapped up in linux they use the someintuitlib-ejb-1.0-SNAPSHOT-client.jar for the file name. Thus the classpath fails and a class not found exception results.
This seems to be specific to linux and ejb relying on SNAPSHOTs built on another machine and uploaded to a shared repository. There are other SNAPSHOTs in the dependency list and their names are used correctly. Those SNAPSHOTs are built locally as part of the build. Thus I think it is specific to SNAPSHOTs built remotely and uploaded to a shared SNAPSHOT repository.
I have supplied a sample pom.xml that may generate the bug but I can not test it out as I do not have a remote repository that I can push SNAPSHOTs to.
--
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] Updated: (MSHARED-140) MANEFEST class path attribute uses
repository style name despite setting classpathMavenRepositoryLayout to
false
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MSHARED-140:
------------------------------------
Attachment: MSHARED-140.zip
I modified your pom.xml slightly and added a public SNAPSHOT repository. See attached sample project.
Then I tried it on Windows, and I get the following Class-Path entry in the MANIFEST.MF:
{noformat}
Class-Path: commons-math-2.0-20090723.185718-6.jar
{noformat}
> MANEFEST class path attribute uses repository style name despite setting classpathMavenRepositoryLayout to false
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-140
> URL: http://jira.codehaus.org/browse/MSHARED-140
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Environment: Ubuntu 9.04 64bit
> Reporter: Mike Power
> Attachments: MSHARED-140.zip, pom.xml
>
>
> I ran into this while porting a windows maven build to linux. Thanks to all your guy's work is was very error free.
> However I did run into one problem where I was getting class not found exceptions for ejb.
> After digging in deep I found our MANIFEST.MF file looked something like this:
> Class-Path: someintuitlib-ejb-1.0-20090513.083158-9-client.jar
> As opposed to windows where it looked like:
> Class-Path: someintuitlib-ejb-1.0-SNAPSHOT-client.jar
> When the jars are wrapped up in linux they use the someintuitlib-ejb-1.0-SNAPSHOT-client.jar for the file name. Thus the classpath fails and a class not found exception results.
> This seems to be specific to linux and ejb relying on SNAPSHOTs built on another machine and uploaded to a shared repository. There are other SNAPSHOTs in the dependency list and their names are used correctly. Those SNAPSHOTs are built locally as part of the build. Thus I think it is specific to SNAPSHOTs built remotely and uploaded to a shared SNAPSHOT repository.
> I have supplied a sample pom.xml that may generate the bug but I can not test it out as I do not have a remote repository that I can push SNAPSHOTs to.
--
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: (MSHARED-140) MANEFEST class path attribute uses
repository style name despite setting classpathMavenRepositoryLayout to
false
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205987#action_205987 ]
Dennis Lundberg commented on MSHARED-140:
-----------------------------------------
The parameter classpathMavenRepositoryLayout specifies if the Class-Path of the manifest should contain a Maven repository like *path* or not. It doesn't affect the name of the *file* in the manifest. See
http://maven.apache.org/shared/maven-archiver/#class_manifest
> MANEFEST class path attribute uses repository style name despite setting classpathMavenRepositoryLayout to false
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-140
> URL: http://jira.codehaus.org/browse/MSHARED-140
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Environment: Ubuntu 9.04 64bit
> Reporter: Mike Power
> Attachments: pom.xml
>
>
> I ran into this while porting a windows maven build to linux. Thanks to all your guy's work is was very error free.
> However I did run into one problem where I was getting class not found exceptions for ejb.
> After digging in deep I found our MANIFEST.MF file looked something like this:
> Class-Path: someintuitlib-ejb-1.0-20090513.083158-9-client.jar
> As opposed to windows where it looked like:
> Class-Path: someintuitlib-ejb-1.0-SNAPSHOT-client.jar
> When the jars are wrapped up in linux they use the someintuitlib-ejb-1.0-SNAPSHOT-client.jar for the file name. Thus the classpath fails and a class not found exception results.
> This seems to be specific to linux and ejb relying on SNAPSHOTs built on another machine and uploaded to a shared repository. There are other SNAPSHOTs in the dependency list and their names are used correctly. Those SNAPSHOTs are built locally as part of the build. Thus I think it is specific to SNAPSHOTs built remotely and uploaded to a shared SNAPSHOT repository.
> I have supplied a sample pom.xml that may generate the bug but I can not test it out as I do not have a remote repository that I can push SNAPSHOTs to.
--
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: (MSHARED-140) MANEFEST class path attribute uses
repository style name despite setting classpathMavenRepositoryLayout to
false
Posted by "Mike Power (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206462#action_206462 ]
Mike Power commented on MSHARED-140:
------------------------------------
You are right I get the same behaviour on both my windows and linux. Thanks for the snapshot repsitory. I'll do some more triage and see if I can narrow the bug down. I'll upload a new project once I figure out what is going on.
> MANEFEST class path attribute uses repository style name despite setting classpathMavenRepositoryLayout to false
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-140
> URL: http://jira.codehaus.org/browse/MSHARED-140
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Environment: Ubuntu 9.04 64bit
> Reporter: Mike Power
> Attachments: MSHARED-140.zip, pom.xml
>
>
> I ran into this while porting a windows maven build to linux. Thanks to all your guy's work is was very error free.
> However I did run into one problem where I was getting class not found exceptions for ejb.
> After digging in deep I found our MANIFEST.MF file looked something like this:
> Class-Path: someintuitlib-ejb-1.0-20090513.083158-9-client.jar
> As opposed to windows where it looked like:
> Class-Path: someintuitlib-ejb-1.0-SNAPSHOT-client.jar
> When the jars are wrapped up in linux they use the someintuitlib-ejb-1.0-SNAPSHOT-client.jar for the file name. Thus the classpath fails and a class not found exception results.
> This seems to be specific to linux and ejb relying on SNAPSHOTs built on another machine and uploaded to a shared repository. There are other SNAPSHOTs in the dependency list and their names are used correctly. Those SNAPSHOTs are built locally as part of the build. Thus I think it is specific to SNAPSHOTs built remotely and uploaded to a shared SNAPSHOT repository.
> I have supplied a sample pom.xml that may generate the bug but I can not test it out as I do not have a remote repository that I can push SNAPSHOTs to.
--
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