I have built a new release candidate for Ivy 2.0.0.
The only difference with the previous attempt is that the Ivy bundle version is
now "2.0.0.final".
You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.0.0/
A maven 2 staging repo with this release is available he
ok, I'll update the bundle version to "2.0.0.final"
Maarten
- Original Message
From: Nicolas Lalevée
To: Ant Developers List
Sent: Thursday, January 8, 2009 7:51:06 PM
Subject: Re: [VOTE] Ivy 2.0.0 Release
It seems there is an issue with the bundle version of Ivy:
In the generated M
It seems there is an issue with the bundle version of Ivy:
In the generated MANIFEST.MF there is '2.0.0_20090107223116' which is
an invalid OSGi version.
And to make that final version be considered upper than the RC2, that
final version cannot be tagged as 2.0.0, because '2.0.0' is considered
These log messages are confusing, beacause they are not resolve time
conflicts, but retrieve time conflicts: when Ivy retrieves a set of
artifact, if it has to retrieve two artifacts to the same location, it
complains about a conflict. For instance if you have a dependency on
acme#foo;1.0 in conf A
Thanks!
One question... I noticed that nobody seems to be committing to ivy's trunk
lately... why is that? When will this and other recent changes get merged
upward?
I guess I'm used to changes always going into trunk first, and then being
merged into more stable branches (e.g. using svnmerge), s
