Yeah, that's what I'm doing. But if there isn't an easier way, there
needs to be. I have a dependency hierarchy 3 levels deep for this
project, and it is a real pain to crawl the dependency tree to configure
a pom. You should just be able to designate a depedency jar as being
excluded, and all of its ancestral dependencies will be excluded as
well. It makes sense for optimizing ear, sar, and wsr archiving.
Brad
Wayne Fay wrote:
Perhaps add all of B's dependencies in your pom as excluded?
Wayne
On 3/6/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
