thanks, saved my day!
one little correction and suggestion (and a last question for maven-jar
plugin):
<assembly>
...
<fileSets>
<fileSet>
<includes>
<include>${artifactId}-*.jar</include>
</includes>
<directory>${basedir}/target</directory>
<!-- output directory empty, so does get copied to root (you wrote
lib/)-->
<outputDirectory></outputDirectory>
</fileSet>
</fileSets>
<dependencySet>
<!-- there could be conflicts (hence there are often libs called
commons-xxx.jar, prepend groupId to ensure that nothing gets overwritten
-->
<outputFileNameMapping>${groupId}-${artifactId}-${version}-${classifier}.${extension}</outputFileNameMapping>
<outputDirectory>lib</outputDirectory>
</dependencySet>
</dependencySets>
...
</assembly>
for
<outputFileNameMapping>${groupId}-${artifactId}-${version}-${classifier}.${extension}</outputFileNameMapping>
i need to adjust the classpath string in MANIFEST.MF. unfortunately making
<classpathPrefix>lib/${groupId}-${artifactId}-${version}-${classifier}.${extension}.</classpathPrefix>
does not work, because it is interpreted as a directory.
how is it possible to set the classpath equal to the library names in lib/
folder configured in assembly plugin?
--
View this message in context:
http://www.nabble.com/maven-plugin-alternative-to-assembly-plugin-tf4262116s177.html#a12311490
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]