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
On Fri, Sep 25, 2009 at 3:10 AM, Marcus Better mar...@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
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
-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
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
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
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
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
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
9 matches
Mail list logo
