ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: Strange behaviour of <manifestclasspath>
Date Wed, 15 Oct 2008 04:06:12 GMT
On Tue, 14 Oct 2008, andbin <abin73@cheapnet.it> wrote:

> [echo] initial.path =
> C:\Test\MyProject\file1.jar;C:\Test\MyProject\lib\file2.jar;C:\Test\MyProject
> [echo] manifest.classpath = file1.jar lib/file2.jar ../MyProject/

as someone familiar with the code I can see why this happens, but it
won't help you (if C:\Test\MyProject in initial.path ended with a \ it
would most likely work as expected).

I agree the result is not desirable.

> But there is another thing more strange. Instead to put MyProject in
> C:\Test, try to put it in C:\ (move MyProject in C:\).
> 
> - - - - - - - - - - - - - - - - - - -
> C:\MyProject>ant
> Buildfile: build.xml
>      [echo] initial.path =
> C:\MyProject\file1.jar;C:\MyProject\lib\file2.jar;C:\MyProject
> 
> BUILD FAILED java.lang.NullPointerException at
> java.lang.String.startsWith(String.java:1422) at
> java.lang.String.startsWith(String.java:1451) at
> org.apache.tools.ant.taskdefs.ManifestClassPath.execute(ManifestClassPath.java:100)

This clearly is a bug, could you please file a bugzilla issue so we
don't loose track of it?

Thanks

        Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message