[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_68552 ]
Brett Porter commented on MASSEMBLY-67:
---------------------------------------
ok, so you aren't producing a jar in the assembly plugin.
1) you produce a jar with a manifest and main-class and class-path
2) you produce an assembly (say, zip) that contains the above jar, and the
elements of the class-path
if this is the case, then this can be closed won't fix as there's nothing wrong
with the assembly plugin (the bug is the writing of the incorrect class-path in
the jar plugin).
> 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
