Igor A. Deruga wrote:
|
| Here's how dependencies are being copied:
|
| //----------------sample----------------
| <j:forEach var="dep" items="${pom.dependencies}">
| <copy file="${pom.getDependencyPath(dep.getId())}"
| todir="${tomcat.dir}/common/lib"/>
| </j:forEach>
| //----------------sample end----------------
|
The above works fine for me :-) Thank you very much Igor.
I am now copying the dependencies to a /lib subfolder in my target
directory. I do not know whether it is good practice or not but it is
what I want at the moment and I can start the application.
Note for people in the same situatio: The maven-jar-plugin-property
"maven.jar.manifest.classpath.add" did not add anything to the manifest
of my client-application, so I could not address any of the copied
jar-Files. - A bug? - I am now using an external manifest including the
classpath-reference to the libs (Class-Path: lib/XXX.jar). It works fine
and the path to the manifest can be definded by the property
"maven.jar.manifest".
Regards
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
