Thanks Steve, your mail forced me to step back and trace all the
possibilities that could have been the culprit for the
ClassNotFoundException and I am glad I finally figured it out.
In the META-INF directory the auto generated file INDEX.LIST that lists all
the packages for the jar that is being
Garima Bathla wrote:
David :
Thanks, I have tried setting the class-path via manifestclasspath task as
well within a build.xml ant script and it is the same result, with long
class-path's the jar names are split over differnt lines with \n and space
character.
This is by design
http://java.sun
On 2009-06-29, Garima Bathla wrote:
> the problem with that logic though is that java -jar command ignores
> class-path which contains more than one space character
> so e.g.
> Class-Path: aaa.jar ss ..(till 71 characters)
> bbb.jar
> where s - space character till 71 characters
Maybe you are right, Garima.
I'll run a sample on my machine shortly to validate your use case and the
corresponding output.
Cheers
Avlesh
On Mon, Jun 29, 2009 at 9:53 PM, Garima Bathla wrote:
> Avlesh,
>
> Thanks, your reply does makes a lot of sense - and honestly what you
> suggested I have a
Avlesh,
Thanks, your reply does makes a lot of sense - and honestly what you
suggested I have already tried , the problem with that logic though is that
java -jar command ignores class-path which contains more than one space
character
so e.g.
Class-Path: aaa.jar ss ..(till 71 charact
David :
Thanks, I have tried setting the class-path via manifestclasspath task as
well within a build.xml ant script and it is the same result, with long
class-path's the jar names are split over differnt lines with \n and space
character.
On Mon, Jun 29, 2009 at 7:39 AM, David Weintraub wrote:
Just curious: Why don't you use the task and the
task?
On Mon, Jun 29, 2009 at 3:02 AM, Garima Bathla wrote:
> 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
Here is what the jar specification has to say on manifest's class-path
attribute -
The value of this attribute specifies the relative URLs of the extensions or
> libraries that this application or extension needs. URLs are separated by
> one or more spaces. The application or extension class loade
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 learn it very
hard way that if Class-Path in a jar is not se
