-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, December 10, 2013 6:57 PM
To: Maven Users List
Subject: Re: How to resolve right dependency which enabled and
built/install with profile?
Using profiles to manipulate dependencies is a route to madness.
An modules depende
-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Wednesday, December 11, 2013 6:47 PM
To: Maven Users List
Subject: Re: How to resolve right dependency which enabled and built/install
with profile?
You are looking for the impossible.
You want A to work with any version
t; -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Tuesday, December 10, 2013 6:57 PM
> To: Maven Users List
> Subject: Re: How to resolve right dependency which enabled and
> built/install with profile?
>
> Using profiles
ng libjar is ok.
Best Regards,
Raymond Liu
-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
Sent: Wednesday, December 11, 2013 12:24 PM
To: users@maven.apache.org
Subject: Re: How to resolve right dependency which enabled and built/install
with profile?
B
ilto:rwhee...@artifact-software.com]
Sent: Wednesday, December 11, 2013 12:24 PM
To: users@maven.apache.org
Subject: Re: How to resolve right dependency which enabled and built/install
with profile?
B depends on A
A depends on C
C depends on libjar x.0 "provided"
C has no code and is
as a feature
missing?
Best Regards,
Raymond Liu
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, December 10, 2013 6:57 PM
To: Maven Users List
Subject: Re: How to resolve right dependency which enabled and built/install
with profile?
Using
inal Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, December 10, 2013 6:57 PM
To: Maven Users List
Subject: Re: How to resolve right dependency which enabled and built/install
with profile?
Using profiles to manipulate dependencies is a route to madness.
An m
Using profiles to manipulate dependencies is a route to madness.
An modules dependencies should be a constant... It was a mistake to allow
within .
The correct solution is to create additional modules that aggregate in the
corresponding lib versions (this is also a bad plan, but less worse than
