Hi,
on behalf of the Ant development team, I have the pleasure to announce
the release of Apache Ant 1.8.1.
Key features of the 1.8.1 release are
* new task augment allows to add attributes or nested elements to
previously defined references
* numerous bug fixes and improvements as docum
Hello,
thanks for the response.
No, I do not know a simple way to reproduce this.
It happens in self defined task that parses xml.
So it has to do with classpath issues and taskdef.
The stacktrace shows that the classptahs are mixed up:
com.sun.org.apache.xerces: This is the cp if the Java sdk
i downloaded xalan 2.7.1 and discovered these specifications displayed in
/META-INF/manifest.mf
Manifest-Version: 1.0
Created-By: 1.3.1 (IBM Corporation)
Main-Class: org.apache.xalan.xslt.Process
Class-Path: xercesImpl.jar xml-apis.jar serializer.jar
Name: org/apache/xalan/
Comment: Main Xalan
We don't use the Xalan shipped with Java -- we substitute our preferred version
via the java endorsed directories mechanism. When Xalan was first included
with Java several years ago, there was a bug in the Xalan version shipped, but
fixed in the latest version of Xalan. So we started using
"
Hello,
I found out that the xalanimpl shipped with Ant1.7.1 is probably
incompatible to Java1.6.0_17, because
Java1.6 is shipped with a different xalan version
When I run Ant together with Java 1,6.0_17 I get a certain error
When I remove xalanimpl in the ANT lib dir I don't get this erro
> -Original Message-
> From: Stefan Bodewig [mailto:bode...@apache.org]
> Sent: 06 May 2010 04:39
> To: user@ant.apache.org
> Subject: Re: Better alternative than using foreach, for and
> if/then/else?
>
> On 2010-05-05, Bailey, Darragh wrote:
>
> > 1) Is for/foreach the only real op
>From the manual:
Jan
>-Ursprüngliche Nachricht-
>Von: Frank Wilson [mailto:fajwil...@gmail.com]
>Gesendet: Donnerstag, 6. Mai 2010 17:59
>An: user@ant.apache.org
>Betreff: importing ant targets from the classpath
>
>I would like to import ant build targets fro
