On 2018-03-01, Gintautas Grigelionis wrote:
> Build File: .../src/tests/antunit/taskdefs/copy-test.xml
> Tests run: 26, Failures: 0, Errors: 2, Time elapsed: 8,59 sec
Passes for me locally as well as on Jenkins
https://builds.apache.org/view/A-D/view/Ant/job/Ant-Build-Matrix-master-Linux/OS=xeni
I just tried locally both with Java 8 and 9:
java version "9.0.1"
Java(TM) SE Runtime Environment (build 9.0.1+11)
Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode)
They pass for me:
[au:antunit] Tests run: 26, Failures: 0, Errors: 0, Time elapsed: 9.175 sec
[au:antunit] Target: t
On 3/1/2011 3:49 AM, Stefan Bodewig wrote:
On 2011-03-01, Antoine Levy-Lambert wrote:
OK I have done "something".
Thank you. I have tweaked a few things and am just running the full
testsuite on my windows box where problems with undeleteable jars tend
to show up.
Thanks too.
I have seen t
On 2011-03-01, Antoine Levy-Lambert wrote:
> OK I have done "something".
Thank you. I have tweaked a few things and am just running the full
testsuite on my windows box where problems with undeleteable jars tend
to show up.
> I have seen that the java resources like ${java:foo!foo.properties} i
OK I have done "something".
for taskdef-test.xml I have added 5 properties test1.jar to test5.jar
which correspond to work entries in gump.
I have seen that the java resources like ${java:foo!foo.properties} in
replacetokens-test.xml do not lend themselves to standardisation.
I wanted to replace
On 2/28/11 11:02 AM, Stefan Bodewig wrote:
> On 2011-02-28, Antoine Levy-Lambert wrote:
>
>> I see now that in fact there are still 21 antunit tests failing in gump
>> (see [1] and [2] below) :
>> Do we want to add a work entry in gump metadata for each of the
>> directories where these tests creat
On 2011-02-28, Antoine Levy-Lambert wrote:
> I see now that in fact there are still 21 antunit tests failing in gump
> (see [1] and [2] below) :
> Do we want to add a work entry in gump metadata for each of the
> directories where these tests create classes or resources ?
> Or do we want to someh
On 12/7/2010 3:18 PM, Rod MacKenzie wrote:
ys 1.6).
Are you using Mac OS X 10.6? If so it only supports Java 1.6 by
default but has links/aliases for versions 1.3 to 1.5 that will run
Java 1.6. That may explain the Java version confusion.
Yes, I am using Mac OS X 10.6.
Rod
Thanks,
Antoine
On 7 December 2010 18:34, Antoine Levy-Lambert wrote:
> Hi,
>
> I just built trunk and ran the tests on Mac OS.
>
> I am not 100% sure whether I have been using Java 1.5 or 1.6 as my
> JAVA_HOME setting and java -version seem to be telling different stories
> ( my JAVA_HOME has a 1.5.0 in the path
