After a little more testing, one thing I did notice was an
apparent stricter treatment of property expansion.
With 1.8.1, having an arg to a forked java task like this:
was happily ignored if skipFetch wasn't defined.
With 1.8.2, we now get a failed build with reason:
Property skipFetch was c
On 2010-12-15, Paul King wrote:
> After a little more testing, one thing I did notice was an
> apparent stricter treatment of property expansion.
> With 1.8.1, having an arg to a forked java task like this:
>
> was happily ignored if skipFetch wasn't defined.
> With 1.8.2, we now get a failed b
This is probably enough to reproduce it:
Cheers, Paul.
On 15/12/2010 7:55 PM, Stefan Bodewig wrote:
On 2010-12-15, Paul King wrote:
After a little more testing, one thing I did notice was an
apparent stricter treatment of property expansion.
With 1.8.1, havin
On 2010-12-15, Paul King wrote:
> This is probably enough to reproduce it:
Yes, it is, thank you Paul.
>
>
>
>
>
>
>
>
The error message is created by the forked Ant process, not the one
executing the build file. You would see the same if you used
ant -Dbar=${b
Hi,
Antoine
On 12/14/2010 12:30 PM, Michael Sunde wrote:
Hi,
I recently tested upgrading my build from ant 1.7.1 to ant 1.8.2alpha (1.8.1
broke build) and the build times doubled (2hrs vs 1hr). Has anyone else noticed
this?
https://issues.apache.org/bugzilla/show_bug.cgi?id=50229
Since Str
Moving this discussion to ant-dev.
My guess is that in ant 1.8.x it is only legal to use references which
have already been defined at execution time.
So the eclipse integration would need to execute the build to find which
references are legally usable in a given target.
Maybe the eclipse
Antoine Levy-Lambert wrote on 2010/12/15 10:59:35 AM:
>
> My guess is that in ant 1.8.x it is only legal to use references which
> have already been defined at execution time.
>
> So the eclipse integration would need to execute the build to find which
> references are legally usable in a given
On 12/15/2010 12:15 PM, Antoine Levy-Lambert wrote:
On 12/14/2010 12:30 PM, Michael Sunde wrote:
Hi,
I recently tested upgrading my build from ant 1.7.1 to ant 1.8.2alpha
(1.8.1 broke build) and the build times doubled (2hrs vs 1hr). Has
anyone else noticed this?
https://issues.apache.org/bu
On 15/12/2010 10:55 PM, Stefan Bodewig wrote:
On 2010-12-15, Paul King wrote:
This is probably enough to reproduce it:
Yes, it is, thank you Paul.
The error message is created by the forked Ant process, not the one
executing the build file. You would
Hi Antoine,
I'm bootstrapping on Windows XP SP3 behind a proxy that requires
authentication with oracle jdk6 (1.6.22)
compile-tests:
test-jar:
BUILD FAILED
C:\Temp\apache-ant-1.8.2-src\apache-ant-1.8.2\build.xml:986: The following error
occurred while executing this line:
C:\Temp\apache-ant-1.
Hi,
http://ant.apache.org/manual/tasklist.html
This is giving me: 404 not found
Kev
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
11 matches
Mail list logo
