one war would have application dependencies packaged inside its
WEB-INF/lib because it is the application. For a skinny war it is part of a
larger application and therefore the application dependencies are transitive.
"application" dependencies can be declared in anywhere normal compile
depend
I'm surprised no one has commented.
Since it's an important issue in my work or anyone that packages ears I
would think.
I'll comment below.
> 1. add a new scope called "application" that is exposed
> as application dependencies
Having a scope for these seems to be a better approach in my
Hi,
I am new to maven development and have been tackling the "skinny" war problem
(http://docs.codehaus.org/display/MAVENUSER/Solving+the+Skinny+Wars+problem).
After a few attempts and considering pros and cons of various solutions and
their implementations I am resigned to the fac
