On Thu, Oct 21, 2010 at 12:35 PM, Phillip Hellewell wrote:
> On Thu, Oct 21, 2010 at 12:32 PM, Wayne Fay wrote:
> >> And to make it more manageable capture the version in a property and
> >> use that in the different places.
> >
> > Or compose all 3 artifacts into a single "all" dependency and de
On Thu, Oct 21, 2010 at 12:32 PM, Wayne Fay wrote:
>> And to make it more manageable capture the version in a property and
>> use that in the different places.
>
> Or compose all 3 artifacts into a single "all" dependency and depend on it.
Thanks. Given the issues surrounding classifiers, I'm th
On Thu, Oct 21, 2010 at 11:57 AM, Yanko, Curtis wrote:
>
> Perhaps the enforcer plugin could help
>
> http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html
Thanks. It seems like a lot of work to prevent something that IMO
should be treated as an error by the dependency resolut
> And to make it more manageable capture the version in a property and
> use that in the different places.
Or compose all 3 artifacts into a single "all" dependency and depend on it.
Wayne
-
To unsubscribe, e-mail: users-unsubsc
inal Message-
> From: Phillip Hellewell [mailto:ssh...@gmail.com]
> Sent: Thursday, October 21, 2010 1:53 PM
> To: Maven Users List
> Subject: Same dependency different classifier
>
> Can I make it an error if someone tries to use two different versions of
> the same dependency w
: Phillip Hellewell [mailto:ssh...@gmail.com]
Sent: Thursday, October 21, 2010 1:53 PM
To: Maven Users List
Subject: Same dependency different classifier
Can I make it an error if someone tries to use two different versions of
the same dependency with different classifiers?
For example, this works, but I
Can I make it an error if someone tries to use two different versions
of the same dependency with different classifiers?
For example, this works, but I want it to cause an error:
ad.3rdparty
zlib
[1.2.5]
zip
dlls
ad.3rdparty
zlib
[1.2
