Try these two links -
http://maven.apache.org/plugins/maven-war-plugin/examples/skinny-wars.html
http://docs.codehaus.org/display/MAVENUSER/Solving+the+Skinny+Wars+problem
-Kyle
On Tue, Apr 21, 2009 at 11:39 PM, RaviPotnuru ravi_mai...@yahoo.co.inwrote:
I have an EAR project for which the
I have a project which I am converting from ANT to Maven. One of the
artifacts is an EJB project. I am trying to create the ejb-client jar
artifact and it is excluding some of my class files due to the default
exclusion **/*Bean.class set on the maven-ejb-pluign. At the current time I
can not
/clientExcludes
This override the default exclusion **/*Bean.class but keeps the others.
-Kyle
On Thu, Apr 9, 2009 at 1:03 PM, Kyle Bober kyle.bo...@gmail.com wrote:
I have a project which I am converting from ANT to Maven. One of the
artifacts is an EJB project. I am trying to create the ejb
That should work the way you have it configured. Did you run the clean goal
after you changed the dependency scope to provided. This will make sure that
a previous build that may have contained the dependencies is completely
removed.
-Kyle
On Wed, Apr 8, 2009 at 5:22 AM, Robert Einsle
wrote:
Hy,
i think i run it several times, incl restart of my Developementenvironment.
Robert
Kyle Bober schrieb:
That should work the way you have it configured. Did you run the clean
goal after you changed the dependency scope to provided. This will
make sure that a previous build
Just noticed there is a plugin maven-overview-pluing at
http://code.google.com/p/maven-overview-plugin/ Looks like it creates a
graphic report of the dependencies. Not sure if it supports the version
numbers yet. Also, the m2Eclipse plugin has a nice view that shows the
dependency graph of
