Hi Curtis,
yes, that's right. I want do declare a set of dependencies, which always must
be used all or none. That why I encapsulate those dependencies in a
separate pom and reference it with a type=pom dependency.
I didn't know about this scope import before and found your link very
I would approach this as an acceptable use of a profile. Make a profile with
these dependencies defined. If you activate the profile, they will all be
added. If you don’t activate the profile, none will be added.
This should fix your issues.
Thanks,
Roy Lyons
Senior Configuration Engineer
Not that I'm an expert, but I thought the rule of thumb was this:
Never use profiles in such a way that different profiles build different
versions of artifacts with the same id.
I always restricted my use of profiles to activities such as deployment or
testing that didn't affect the artifacts
Hi,
I'm pleased to announce the release of the gwt-maven-plugin version 2.5.0-rc2.
http://mojo.codehaus.org/gwt-maven-plugin/
To get this update, simply specify the version in your project's
plugin configuration:
plugin
groupIdorg.codehaus.mojo/groupId
John,
That is a pretty good observation.
My assumption (even though assuming anything can be fatal) is that the
resulting project was a top tier application -- one which would not be
subjected to being consumed by another application as a library.
I am in full agreement that this is not a valid
Hah. I spoke too soon. I just thought about it and using shade would be
very dangerous because of possible class collisions. Let me modify my
statement to never do this for anything that will ever be consumed by
another build.
Thanks,
Roy Lyons
Senior Configuration Engineer
On
Early in my exposure to Maven, I imbibed some advice to never try to
use moduleSets in the assembly plugin. I don't recall where or how.
If I were you, I'd be coding out the use of the dependency plugin with
'copy', not 'copy-dependencies' to grab all these thing and arrange
them artfully in a
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
