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
Assembly, when using a type:pom dependency
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
@maven.apache.org
Subject: Antw: Re: Re: Corrupted Assembly, when using a type:pom
dependency
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
@maven. org'
users@maven.apache.orgmailto:users@maven.apache.org
Subject: Antw: Re: Re: Corrupted Assembly, when using a type:pom
dependency
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
@maven.apache.org
Date: Friday, October 12, 2012 6:52 AM
To: 'users@maven. org'
users@maven.apache.orgmailto:users@maven.apache.org
Subject: Antw: Re: Re: Corrupted Assembly, when using a type:pom
dependency
Hi Curtis,
yes, that's right. I want do declare a set of dependencies, which always
must be used all
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
