On 9/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi All,
I have a problem but I don't know if the cause is the assembly plugin, the
jar plugin that creates the MANIFEST or the mechanism that manage snapshot
versions.
I explain :
1)
I have 2 projects : prjA dependding on prjB
=> in the pom.xml of prjA I have a dependency to prjB
<dependency>
<groupId>myGroupId</groupId>
<artifactId>prjB</artifactId>
<version>1.0.0-SNAPSHOT</version>
<scope>compile</scope>
</dependency>
Very important : the dependency is a SNAPSHOT version (build by continuum
on a snapshot repository)
2)
In prjA, I configure the jar plugin to create a MANIFEST file that contains
attributes "Main-Class" and "Class-Path".
The value of the "Class-Path" attribute is set by Maven to
"prjB-1.0.0-SNAPSHOT.jar" ... I think it's correct ...
3)
When I execute the "mvn assembly:assembly" task, the zip contains
prjA-1.0.0-SNAPSHOT.jar (which is correct)
prjB-1.0.0-20060902.020557-2.jar (which is not correct) => does not
correspond to the classpath put in the manifest by Maven
How can I resolve this problem ?
It's a known issue.
See JIRA.
http://jira.codehaus.org/browse/MJAR-28
http://jira.codehaus.org/browse/MASSEMBLY-67
http://jira.codehaus.org/browse/MNG-2456
The solution is as per http://jira.codehaus.org/browse/MASSEMBLY-67#action_72144
Since assembly has not yet been release with this fix in it you need
to roll your own version as per
http://jira.codehaus.org/browse/MASSEMBLY-67#action_72435
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
