Hi Marc, that is exactly what I need! Thank you very much!! @Antonio, Martin: Because of classpath manipulation (switching 3rdParty libraries) while runtime! The library should not be loaded from the webapp classloader.
Fredy -----Ursprüngliche Nachricht----- Von: Marc Rohlfs [mailto:pomar...@googlemail.com] Gesendet: Mittwoch, 2. Februar 2011 17:44 An: Maven Users List Betreff: Re: adding a jar as resource to a webapp I'd suggest it could be a JAR containing an Applet. The maven-dependency-plugin might help You out. Use on of the following approaches: http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-project-dependencies.html On 02/02/11 17:06, Antonio Petrelli wrote: >> The jar should not be added to the classpath at build, runtime! And it >> should not be included in WEB-INF/lib. > Not at build, not at runtime and not in WEB-INF/lib? What do you need it for? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
