[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_68549 ]
Baerrach bonDierne commented on MASSEMBLY-67:
---------------------------------------------
Ok,
I think the problem is that we are not using the archiver to assemble a jar.
We are using the archiver to assemble a binary distribution of the jar, with
all dependencies.
Therefore we need the version values in the manifest to match the versions in
the binary distribution as well.
I'm not clear if the Class-Path entry should be -SNAPSHOT or the resolved
version identifiers.
The only reason for a -SNAPSHOT would be for development purposes and so it
would be easier to just use -SNAPSHOT rather than the timestamped snapshot
versions.
> assembling dependent jars or snapshots uses timestamp formatted version
> instead of ${version}
> ---------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-67
> URL: http://jira.codehaus.org/browse/MASSEMBLY-67
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Reporter: Mark J. Titorenko
>
>
> I'm using the jar plugin to add my dependencies to the manifest. I'm also
> using the assembly plugin to package all dependencies into one archive. The
> problem is that the jar manifest adds my dependencies as "foo-SNAPHOT" and
> the archiver adds them as "foo-20041113.jar".
> This causes my snapshot classes to not be found at runtime.
--
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
