Debian Bug report logs - #547969
ivy jar not added to ant lib

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: przemek tomczyk <cafebabe@interia.pl>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ivy jar not added to ant lib

Date: Wed, 23 Sep 2009 00:02:34 +0200

Package: ivy
Version: 2.1.0~rc2-2
Severity: important

when ant installed, ivy should be added to system's /usr/share/ant/lib , to enable using ivy ant tasks. now user has to link ivy.jar to local ant lib directory.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ivy depends on:
ii  sun-java6-jre [java2-runtime- 6-16-1     Sun Java(TM) Runtime Environment (

ivy recommends no packages.

Versions of packages ivy suggests:
pn  ivy-doc                       <none>     (no description available)
ii  libjsch-java                  0.1.41-2   pure Java implementation of the SS
ii  sun-java6-jre [java2-runtime] 6-16-1     Sun Java(TM) Runtime Environment (

-- no debconf information

Message #10 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Onkar Shinde <onkarshinde@ubuntu.com>

To: przemek tomczyk <cafebabe@interia.pl>, 547969@bugs.debian.org

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Wed, 23 Sep 2009 09:29:55 +0530

Ant upstream authors recommend using classpath attribute for optional
ant tasks when defining the task in build.xml.[1] Hence the symlink
should not be present in ant's library. Also the symlink modifies the
default classpath of ant which will cause problem if user wants to use
another version of ivy outside the system installation.

[1] http://ant.apache.org/manual/install.html#optionalTasks

Message #15 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Michael Koch <konqueror@gmx.de>

To: Onkar Shinde <onkarshinde@ubuntu.com>, 547969@bugs.debian.org

Cc: przemek tomczyk <cafebabe@interia.pl>

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Wed, 23 Sep 2009 07:07:38 +0200

On Wed, Sep 23, 2009 at 09:29:55AM +0530, Onkar Shinde wrote:
> Ant upstream authors recommend using classpath attribute for optional
> ant tasks when defining the task in build.xml.[1] Hence the symlink
> should not be present in ant's library. Also the symlink modifies the
> default classpath of ant which will cause problem if user wants to use
> another version of ivy outside the system installation.

I agree with Onkar. There are several ways to make additional classes
for tasks know to ant. Polluting Ant's lib-directory is one of the
worst ones.

I tend to tag this bug as wontfix but I will wait some more days for
more opinions.


Cheers,
Michael

Message #20 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Patrick McFarland <pmcfarland@adterrasperaspera.com>

To: 547969@bugs.debian.org

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Thu, 24 Sep 2009 04:31:54 -0400

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 and people expect Ivy to work by default when installing it.

I find a dpkg configure option an acceptable alternative to blindly
symlinking ivy.jar to
the ant/lib director, as in, ask the user if he wants to do it
(defaulting to yes).

Message #25 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Michael Koch <konqueror@gmx.de>

To: Patrick McFarland <pmcfarland@adterrasperaspera.com>, 547969@bugs.debian.org

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Thu, 24 Sep 2009 21:31:54 +0200

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 and people expect Ivy to work by default when installing it.
> 
> I find a dpkg configure option an acceptable alternative to blindly
> symlinking ivy.jar to
> the ant/lib director, as in, ask the user if he wants to do it
> (defaulting to yes).

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.


Cheers,
Michael

Message #30 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Marcus Better <marcus@better.se>

To: Michael Koch <konqueror@gmx.de>, 547969@bugs.debian.org

Cc: Patrick McFarland <pmcfarland@adterrasperaspera.com>

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Fri, 25 Sep 2009 09:10:10 +0200

-----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-----

Message #35 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Michael Koch <konqueror@gmx.de>

To: Marcus Better <marcus@better.se>, 547969@bugs.debian.org

Cc: Patrick McFarland <pmcfarland@adterrasperaspera.com>

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Sat, 26 Sep 2009 08:49:05 +0200

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/.


Cheers,
Michael

Message #40 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Patrick McFarland <pmcfarland@adterrasperaspera.com>

To: Marcus Better <marcus@better.se>

Cc: Michael Koch <konqueror@gmx.de>, 547969@bugs.debian.org

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Sat, 26 Sep 2009 09:25:21 -0400

On Fri, Sep 25, 2009 at 3:10 AM, Marcus Better <marcus@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

Message #45 received at 547969@bugs.debian.org (full text, mbox, reply):

From: Michael Koch <konqueror@gmx.de>

To: Patrick McFarland <pmcfarland@adterrasperaspera.com>, 547969@bugs.debian.org

Cc: Marcus Better <marcus@better.se>

Subject: Re: Bug#547969: ivy jar not added to ant lib

Date: Tue, 29 Sep 2009 14:02:59 +0200

On Sat, Sep 26, 2009 at 09:25:21AM -0400, Patrick McFarland wrote:
> 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.

I'm a bit reluctant to just implement this debconf question for this.

I see no place in Debian where we recommend to just 'apt-get install'
java libraries and they will automatically get used. Even contents
of /usr/share/java ist not put on the CLASSPATH by default. There
are too many possible problems with this. Too many things can break
when wrong jars are on the CLASSPATH or jars are in the wrong order
on the CLASSPATH.

Do you have any really world example where Ivy is used inside Ant with
this setup? Having a good real world example where this is needed and
the example also works out-of-the-box with upstream ant releases would
be good hint to put Ivy into the Ant installation by default.

What would be possible would be an entry in README.Debian. Then the
local admin can do it if he wants to. And we can also clearly speak
about the possible implications of it.


Cheers,
Michael

Message #50 received at 547969-close@bugs.debian.org (full text, mbox, reply):

From: Varun Hiremath <varun@debian.org>

To: 547969-close@bugs.debian.org

Subject: Bug#547969: fixed in ivy 2.1.0~rc2-3

Date: Fri, 02 Oct 2009 00:02:31 +0000

Source: ivy
Source-Version: 2.1.0~rc2-3

We believe that the bug you reported is fixed in the latest version of
ivy, which is due to be installed in the Debian FTP archive:

ivy-doc_2.1.0~rc2-3_all.deb
  to pool/main/i/ivy/ivy-doc_2.1.0~rc2-3_all.deb
ivy_2.1.0~rc2-3.diff.gz
  to pool/main/i/ivy/ivy_2.1.0~rc2-3.diff.gz
ivy_2.1.0~rc2-3.dsc
  to pool/main/i/ivy/ivy_2.1.0~rc2-3.dsc
ivy_2.1.0~rc2-3_all.deb
  to pool/main/i/ivy/ivy_2.1.0~rc2-3_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 547969@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Varun Hiremath <varun@debian.org> (supplier of updated ivy package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 01 Oct 2009 19:47:35 -0400
Source: ivy
Binary: ivy ivy-doc
Architecture: source all
Version: 2.1.0~rc2-3
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Changed-By: Varun Hiremath <varun@debian.org>
Description: 
 ivy        - The agile dependency manager
 ivy-doc    - The agile dependency manager (documentation)
Closes: 547969 548310 548311
Changes: 
 ivy (2.1.0~rc2-3) unstable; urgency=low
 .
   * Update pom.xml file to latest 2.1.0~rc2 version (Closes: #548310)
   * Include the MANIFEST.MF file in the jar (Closes: #548311)
   * Add debian/README.Debian listing reasons for not creating symlink to
     ivy.jar in ant's lib directory and solutions (Closes: #547969)
   * Switch to default-jdk
   * Bump Standards-Version to 3.8.3 (no changes)
Checksums-Sha1: 
 a812698ba1b10f301e27aea5b41d13d6022fe973 1484 ivy_2.1.0~rc2-3.dsc
 0ff92cdc5cae4b0dd999405400c5c7b66be4c3b0 4312 ivy_2.1.0~rc2-3.diff.gz
 5490d7823558c0b1ae9d48f700e8b0aa9163082a 865436 ivy_2.1.0~rc2-3_all.deb
 c611615eef4a5af4f1f0d9c6e56fdf792d104636 712634 ivy-doc_2.1.0~rc2-3_all.deb
Checksums-Sha256: 
 66b797f7adedf4ca03bfc501737ff2b90c2bc1ab488057e84687ea6e929e037a 1484 ivy_2.1.0~rc2-3.dsc
 4aab0f5ad6613ae974081c4a6abae91855bd5aeb1779b2b036e30adf257412df 4312 ivy_2.1.0~rc2-3.diff.gz
 0023dd99ced136e121fa3e8357f70060c7d6f21616d364f5725043936b788d94 865436 ivy_2.1.0~rc2-3_all.deb
 54a77fe1b5d466a4c5c2de204eeeefc16adeda1c55039522b18beacc5f1b5ba8 712634 ivy-doc_2.1.0~rc2-3_all.deb
Files: 
 0782c67d3e9890e1d284b44be591b18a 1484 java optional ivy_2.1.0~rc2-3.dsc
 65841ee0969ef26abb034915940b70c2 4312 java optional ivy_2.1.0~rc2-3.diff.gz
 fd8b795685b2dd8441ecb8bd8b4b9e08 865436 java optional ivy_2.1.0~rc2-3_all.deb
 83289d555b1aceafabbe38fa788797f3 712634 doc optional ivy-doc_2.1.0~rc2-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFKxUAoPEFSUMxFMZcRAmzEAJ4/KjCgyCExfLAWJIzs26zEJI57xwCbBBaA
Ruo+Bh4oyT6uDtwNXPq5+qQ=
=OhKL
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.