Greetings all,
We're in the process of migrating our enterprise between Java versions. We're
at 6 presently and are moving to either 7 or 8, depending on time frame,
Oracle's release schedule, etc.
We have a number of in-house libraries which we compile and publish to our
private Ivy
Hi Zac,
if you don't want to change the library names nor the revision number, how
about
putting the libs into distinct repositories? Then use different resolver
chains depending
on which jre version you want to have.
Cheers
Carsten
Von:Zachary Bedell zbed...@nycourts.gov
An:
It seems to me this is a classic use case for Ivy confs. So your ivy.xml
might specify:
configurations
conf name=package /
conf name=java6 extends=package /
conf name=java7 extends=package /
conf name=java8 extends=package /
conf name=default extends=java6 /
configurations
Thanks for the suggestion, but there are two problems that break this for us I
think.
First, we already use several configurations in many of the libraries in order
to separate distinct dependency groups (which ideally should be refactored to
separate libraries, but...). For example, we have
I think I like the sound of that.
I should be able to setup a resolver chain both with without the JRE-7 stuff,
list the 7 repository first, and allow the chain to fall down to the default
JRE-6 tree for anything which hasn't been built under 7 yet, right? So
essentially anything built out
Since you hadn't mentioned confs, I was making the assumption that you
weren't using confs. Good to see you are.
I think your criticisms of using confs for this in your situation are
valid.
And I think Carsten's suggestion of multiple repos is workable and
preferable to confs. As long as clients
