I tried using the <provided> approach, and then things wouldn't compile.
I had to configure the ear plugin in the module that creates the ear file to specifically exclude the jars that were required for compilation, but were unneeded in the ear file. On 3/6/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote: > > Thanks Mang! That worked! > > Brad > > Mang Jun Lau wrote: > > >You can try using <scope>provided</scope> for dependency B. > > > > > >_Mang Lau > > > > > > > > > > > >Brad O'Hearne <[EMAIL PROTECTED]> > >03/06/2006 02:37 PM > >Please respond to > >"Maven Users List" <users@maven.apache.org> > > > > > >To > >Maven Users List <users@maven.apache.org> > >cc > > > >Subject > >is there a way to filter dependency jars from being packaged > > > > > > > > > > > > > >I am building a JBoss sar and a JBoss wsr using the sar and wsr plugins. > >I would like to create these archives without including all of the jar > >dependencies. After looking at the documentation, I tried putting this > >into my dependency declaration in my pom: > > > > <optional>true</optional> > > > >This doesn't appear to work the way the documentation states. In my > >project, I have one dependency: call it B. I have declared B to be > >optional in my pom. When I package my project, inside the archive, B has > >been filtered out, but all of B's dependencies are there. Basically what > >I want to have happen, is that I want to filter B and all its > >depedencies up the dependency hierarchy from being inside the archive. > > > >How can this be accomplished? > > > >Thanks. > > > >Brad > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
