garima.bat...@gmail.com
To: ivy-user@ant.apache.org
Sent: Friday, June 26, 2009 5:21:51 AM
Subject: Ivy confs masquerading as dependencies' revisions
Let's say I have an Ivy module that depends on JUnit. But when I go to
publish version 1.0 of my module, I don't want to commit to a particular
/2.1.0-rc1/use/publish.html
Maarten
- Original Message
From: Garima Bathla garima.bat...@gmail.com
To: ivy-user@ant.apache.org
Sent: Friday, June 26, 2009 5:21:51 AM
Subject: Ivy confs masquerading as dependencies' revisions
Let's say I have an Ivy module
Chiming in...
On Fri 2009-06-26 at 12:42h, Garima Bathla wrote on ivy-user:
:
And let's follow your suggestion and put the dependency on JUnit directly in
Foo's ivy.xml:
dependency org=org.junit name=junit rev=3.8.2 conf=...
/
Now, the question arises, what to do about Bar's dependency
On Fri 2009-06-26 at 15:42h, Archie Cobbs wrote on ivy-user:
On Fri, Jun 26, 2009 at 2:42 PM, Garima Bathla garima.bat...@gmail.comwrote:
:
And let's follow your suggestion and put the dependency on JUnit directly
in
Foo's ivy.xml:
dependency org=org.junit name=junit rev=3.8.2 conf=...
Let's say I have an Ivy module that depends on JUnit. But when I go to
publish version 1.0 of my module, I don't want to commit to a particular
version of JUnit. I want to leave open the option to depend on either JUnit
3.8.2 or JUnit 4.6.
The best way I've come up with to accomplish this is to
