I've configured the JAR plugin to generate a Manifest with a classpath per
the online documentation:
<configuration>
<archive>
<manifest>
<mainClass>fully.qualified.MainClass</mainClass>
<addClasspath>true</addClasspath>
</manifest>
</archive>
</configuration>
What's strange (and causing me problems) is that the generated classpath
contains the JAR plugin's dependencies!
Is there a trick to avoiding this? The problems I'm having are caused older
versions of JARs I use being listed on the classpath because Maven uses
them.
Thanks,
Mike
--
View this message in context:
http://www.nabble.com/Generated-Jar-Manifest-Contains-Maven-Jars-tf3416904s177.html#a9522718
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
