Bug#547969: ivy jar not added to ant lib

[Patrick McFarland]

On Fri, Sep 25, 2009 at 3:10 AM, Marcus Better <marcus at better.se> 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.)
>
>> 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?

Basically, either allow Ivy to work by default with no additional
changes, or don't bother packaging Ivy at all. People are going to get
really confused when they apt-get install ivy and it doesn't work and
there are no instructions
included with the .deb to make it work.

People would not apt-get Ivy if they didn't want to use it.

Your same argument applies to ant itself, "But but but some projects
include ant right inside of them, why have ant on the path install, it
might conflict with theirs!"

Programs that include ant and/or ant rules to download Ivy do not
effect Debian's packaging of Ant or Ivy in any realistic way.

My suggestion of a dpkg-configure option to install a symlink or not
pleases both crowds and makes your argument entirely moot.

> Cheers,
>
> Marcus