743096
btw, did you already find the problem?
Maarten
----- Original Message
From: "Buck, Robert"
To: ivy-u...@ant.apache.org
Sent: Tuesday, February 10, 2009 10:23:25 PM
Subject: RE: Unresolved dependency error message makes no sense.
Nope, didn't work -- what threw me
Is this what is desired? The error message here is not a proper sentence
and makes no sense; it does not help me diagnose the issue. Could
someone update the resource bundle text so that it has a proper english
sentence?
>>> "'default' doesn't exist in module module" <<<
Thanks
[ivy:resolve]
Hi,
Is there something I need to do differently in rc1?
Here is what I get (below). Note that beta2 works fine.
Warning: Reference ivy.instance has not been set at runtime, but was
found during
build file parsing, attempting to resolve. Future versions of Ant may
support
referencing ids define
C:\TEMP>ant
Buildfile: build.xml
[echo] Apache Ant version 1.7.1beta compiled on March 18 2008
init:
[echo] test
BUILD SUCCESSFUL
JDK 1.6.0_02-b05 @ WinXP SP2
Jan
> -Ursprüngliche Nachricht-
> Von: Buck, Robert [mailto:[EMAIL PROTECTED]
> Gesendet: Donn
.
Peter
On Thu, Mar 27, 2008 at 1:52 PM, Buck, Robert <[EMAIL PROTECTED]>
wrote:
> Has this bug been reported yet?
>
> Run "ant init clean" and you get an NPE. Basically, Ant will not run
> multiple targets, which is a pretty huge limitation.
>
>
>
>
Has this bug been reported yet?
Run "ant init clean" and you get an NPE. Basically, Ant will not run
multiple targets, which is a pretty huge limitation.
test
Apache Ant version 1.7.1beta compiled on March 18 2008
D:\dev\thirdparty\shared\apache-ant-1.7.1beta>ant -f antfails.
The mailto:[EMAIL PROTECTED]
Sent: Thursday, January 17, 2008 10:49 AM
To: Ant Users List
Subject: Re: using to check for tool availability
On Jan 17, 2008 9:20 AM, Buck, Robert <[EMAIL PROTECTED]> wrote:
> Does anyone have any better suggestions for how to check for tool
> exis
Hello,
I have a problem I am trying to solve that I need some help with. What
I'd like to do is check for the availability of an executable tool on
the system path. If the tool is available, then allow extra (secret
sauce) features to be enabled. Otherwise the extra (non-essential) build
features
