[
https://jira.codehaus.org/browse/MASSEMBLY-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282734#comment-282734
]
Hellmut Adolphs commented on MASSEMBLY-211:
-------------------------------------------
We are seeing this problem as well using 2.2.1 We have both the jar and
assembly plugin working together to produce a zip file that contains an
executable jar (produced with the jar plugin including a manifest that has all
dependencies) and all the jar library dependencies as well.
The problem we are seeing is probably the same or similar to what you were
having, I see some jars with timestamps (we are using SNAPSHOTS for
development) but there is one of them that has not time stamp... and in the
manifest its being looked for with a timestamp. So this "disagreement" between
the assembly and jar plugin create class not found exceptions on run time.
> assembly plugin and jar plugin disagree about whether to use uniqueVersion
> snapshot names
> -----------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-211
> URL: https://jira.codehaus.org/browse/MASSEMBLY-211
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Max Bowsher
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.2-beta-3
>
> Attachments: CSMDirectoryListingOfJars.txt, CSMJarManifest.txt
>
>
> Background: Consider the following setup:
> jar-plugin configured with addClasspath=true, writing list of dependency jar
> file names into manifest of project jar.
> assembly-plugin configured with a dependencySet pulling all dependencies into
> a single directory.
> Result: application is runnable with with "java -jar mainartifact.jar"
> There has long been a problem (i.e. with assembly-plugin 2.1) that when
> deployed snapshot jars were in use, the jar and assembly plugins would
> disagree in whether the uniqueVersion name was used, and this is MNG-2456.
> However, assembly-plugin 2.2-beta-1 has introduced further complications to
> the situation by not using the lifecycle's default set of resolved artifacts,
> but by running a manual resolution of its own. This has made the two plugins
> disagree in more scenarios than before, and broke the workaround patch that I
> posted in MNG-2456.
> At the root of these problems is some very peculiar handling of the 'file',
> 'baseVersion' and 'version' fields of Artifact objects, two notable instances
> of which are the DefaultArtifact.isSnapshot method, which despite being an
> accessor, actually changes the state of the object, and the
> DefaultArtifactResolver.resolve method, which contains some rather bizarre
> manipulation of the 'file' field (more detail may comments in MNG-2456).
> An interim fix to this issue might involve workarounds in both the jar and
> assembly plugins to get them to agree. A true fix probably also involves
> fixing Maven core classes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
