We regularly have tests run on 10+ machines on 4 different platforms and
have never had a problem with using the Ant java task with jar and a nested
classpath.
The classpath is constructed from a filelist *.jar from the ${dir.axisJARs}
property which points to the directory $AXISJAVA_LIB by default. Is the
AXISJAVA_LIB directory clean in you case? i.e. does it only have the 1
correct version of the axis jar files in the directory? Could the order the
files are loaded by ant cause a problem. We could specifically order and
list the jar files to load if that would make a difference.
I'd like some more feedback before committing to make a change as there
seems to be some differences of opinion.
Regards,
Andrew Perry
IBM C/C++ Web Services Client
[EMAIL PROTECTED]
Mail Point 127
IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
Tel. Internal 249828 External + 44 (0)1962 819828
Fax. + 44(0)1962 818080
Adrian Dick/UK/[EMAIL PROTECTED] wrote on 11/01/2005 10:23:58:
>
>
>
>
> I accept people have been having difficulties using the JAR option and
> using classname is the easy option, but I feel we should still persevere,
> otherwise we will no longer be testing the correct creation of the
manifest
> file.
>
> Regards,
> Adrian
>
> _______________________________________
> Adrian Dick ([EMAIL PROTECTED])
>
>
> Andrew Perry2/UK/[EMAIL PROTECTED] wrote on 11/01/2005 09:45:42:
>
> >
> >
> >
> >
> > I have never had a problem with specifying a classpath with the jar
> option
> > in ant, but as the general concensus seems to be to use the classname
> > invocation method, I'll update the buildTest.xml to use this method.
> >
> > Regards,
> >
> > Andrew Perry
>
