On Fri, Oct 12, 2012 at 11:22 PM, Barrie Treloar baerr...@gmail.com wrote:
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
On Mon, Oct 15, 2012 at 12:19 PM, Chris Conroy ccon...@gmail.com wrote:
On Fri, Oct 12, 2012 at 11:22 PM, Barrie Treloar baerr...@gmail.comwrote:
If you are just serving it from jetty you could use
http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html
to
There's a real maven design problem here, if you ask me. Maven
overloads the 'type' of an artifact. A 'war' dependency is legitimate
and a different thing from a 'jar' dependency. Sadly, though, all jar
files are equally treated as the output of the standard java
lifecycle, suitable for classpath.
On Fri, Oct 12, 2012 at 3:59 PM, 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 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
