On Sat, Oct 13, 2012 at 6:29 AM, Chris Conroy <ccon...@gmail.com> wrote: > Is there any way to specify that a dependency should not be on the build > classpath? > > I am using the maven-javadoc-plugin to generate an aggregate javadoc jar > for my top level project. In a sub-project, I have a dependency on the > javadoc jar so that I can serve the javadoc from a jetty server. This > results in some strange behavior with m2e (full context here: > http://www.mail-archive.com/m2e-users@eclipse.org/msg02900.html) that > revealed that the javadoc jar is actually ending up on the build classpath. > > However, it doesn't really make sense for the javadoc jar to be on the > build classpath. Is there any way that I can tell maven that something is a > *non-Java *dependency that should get run at the right phase but should > not be part of the build classpath?
If you are just serving it from jetty you could use http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html to copy the aggregate jar into the web directory? Trying to wedge dependencies into this round hole may not be your best option. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
