Bug#547969: ivy jar not added to ant lib
konqueror at gmx.de
Sat Sep 26 06:49:05 UTC 2009
On Fri, Sep 25, 2009 at 09:10:10AM +0200, Marcus Better wrote:
> Michael Koch wrote:
> > On Thu, Sep 24, 2009 at 04:31:54AM -0400, Patrick McFarland wrote:
> >> I would also like to see Ivy added to ant/lib. Ivy is a special case
> >> in that it is a sister project to Ant
> I would prefer this decision to be based on technical reasons.
> >> people expect Ivy to work by default when installing it.
> Nothing like that happens when you download the Ivy package from
> upstream (and for good reasons!), so I doubt this.
> In fact projects I've seen using Ivy have different ways of ensuring Ivy
> is on the classpath. (For instance, Grails projects have an Ant target
> that downloads Ivy if necessary.)
This is a valid point.
> > After looking into the issue more closely I think we can make an exception
> > for Ivy in this case. I'm with Patrick for the symlink.
> Can any of the proponents of this suggestions actually show the
> requirement (real-life use case)? "I am too lazy to plug into ~/.ant/lib
> or set the classpath" does not count.
> Can you prove that it won't cause breakage similar to #506018 when
> someone tries to load a different Ivy version in their build?
I have just worked on ant-contrib and for it to build its enough to
put 'ivy' into DEB_JARS which puts it on the classpath when calling ant.
Ok, as long as we have no really good reason we dont put it into ant/lib/.
More information about the pkg-java-maintainers