-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? Cheers, Marcus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkq8bM4ACgkQXjXn6TzcAQn7HwCeNColNkkWX/soXGPGluR5M2uE YhsAniHtMexOTTPT6/zCB+EQgf97S5cN =qGYm -----END PGP SIGNATURE----- _______________________________________________ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
