Hi Jarek;
Thanks for the help..
I fixed it using *"Manifestclasspath task"*, which is used to avoid long
classpath issue...
I have written a small blog[1] entry with the sample for others reference..
http://vvratha.blogspot.com/2012/04/avoiding-long-classpath-issue-in-ant.html
Thanks
-Ratha
On 2
W dniu 2012-04-02 12:21, vijayaratha vijayasingam pisze:
Actually i want to know how can i correct my build.xml or what is the issue
with it?
Use unjar task to unpack the jars.
pathing.jar contains the manifest file where the classpaths are defined
..But ANT couldn't load it with the pathid "
Actually i want to know how can i correct my build.xml or what is the issue
with it?
pathing.jar contains the manifest file where the classpaths are defined
..But ANT couldn't load it with the pathid "javac.classpath"..
Any issue with the script?
Thanks
-Ratha
On 2 April 2012 15:47, Jarek Czekals
You could unpack part of the jars and use the directory containing
classes as a classpath. Later you may put them into a single jar. For
compilation it's safe. For distribution there may be licensing issues,
depending on the libraries involved.
Jarek
W dniu 2012-04-02 11:47, vijayaratha vijay
I corrected my build.xml as follows according the following doc
http://ant.apache.org/manual/Tasks/jar.html
Where I just introduced a new jar(pathing.jar) which mainly contains a
manifest file where i define all classpaths..But still i get CNF issue..
Any idea how can i overcome this issue?
