[
http://jira.codehaus.org/browse/MSHARED-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148737#action_148737
]
jdcasey edited comment on MSHARED-36 at 9/22/08 3:09 PM:
------------------------------------------------------------
I've changed the manifest creation logic to use the timestamp/buildnumber
version by default (when the classpathLayoutType is simple - the default value
- or repository, which makes it act like a maven repo dir structure). The repo
output looks like:
{noformat}
org/codehaus/plexus/plexus-archiver/1.0-alpha-11-SNAPSHOT/plexus-archiver-1.0-alpha-11-20081022.112233-1.jar
{noformat}
You could always specify a custom classpathLayoutType and customClasspathLayout
configuration to modify this.
See MSHARED-32 for more info on the custom layout stuff.
was (Author: jdcasey):
I've changed the manifest creation logic to use the timestamp/buildnumber
version by default (when the classpathLayoutType is simple - the default value
- or repository, which makes it act like a maven repo dir structure). The repo
output looks like:
{noformat}
org/codehaus/plexus/plexus-archiver/1.0-alpha-11-SNAPSHOT/plexus-archiver-1.0-alpha-11-20081022.112233-1.jar
{noformat}
You could always specify a custom classpathLayoutType and customClasspathLayout
configuration to modify this.
> Maven Archiver creates incorrect Class-Path entry in Manifest for deployed
> snapshots
> ------------------------------------------------------------------------------------
>
> Key: MSHARED-36
> URL: http://jira.codehaus.org/browse/MSHARED-36
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Reporter: Barrie Treloar
> Assignee: John Casey
> Fix For: maven-archiver-2.4
>
> 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
