On Tue, Jun 23, 2009 at 12:40 PM, Garima Bathla wrote:
> I am trying to set classpath for a standalone application and I am not able
> to figure out what exactly I am doing wrong. Below is the classpath that is
> being generated in the MANIFEST.MF And this isn't valid classpath , when I
> run java
Thanks DD for your prompt reply,
I am trying to set classpath for a standalone application and I am not able
to figure out what exactly I am doing wrong. Below is the classpath that is
being generated in the MANIFEST.MF And this isn't valid classpath , when I
run java -jar mystandaloneapplication.
On Mon, Jun 22, 2009 at 11:58 AM, Garima Bathla wrote:
> That exactly is what I am doing, using Ant's Manifest class. Problem
> happens to be that my classpath is too big and Manifest file has limit of 72
> characters per line, so even though it spits out my configured classpath ,
> it ain't set c
That exactly is what I am doing, using Ant's Manifest class. Problem
happens to be that my classpath is too big and Manifest file has limit of 72
characters per line, so even though it spits out my configured classpath ,
it ain't set correctly (as I have listed in the orginial thread).
Any help i
On Mon, Jun 22, 2009 at 12:33 AM, Garima Bathla wrote:
> I am in the process of generating MANIFEST.MF file programmatically by
> Extending Jar Task; I am almost there, but the class-path that Jar task
> prints in the Manifest file isn't formatted correctly.
Have you looked at Ant's own Manifest a
Dear Fellow memebers,
I really need help , I have been stuck with same problem for few days now.
Problem:
As we all know, manifest file syntax is very sensitive ( sensitive to
spaces, # of characters in a line, \n character). And I have learnt it very
hard way that if Class-Path in a jar is not s
