t; who expected to be able to do what you are trying to do.
>
> Thanks,
> Kevin
>
> -Original Message-
> From: Ravi Roy [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 22, 2008 12:04 PM
> To: Ant Users List
> Subject: Re: Class-Path not recognised from MANIFEST.MF
>
&
rticles and forum entries relating to this. You are not the first
who expected to be able to do what you are trying to do.
Thanks,
Kevin
-Original Message-
From: Ravi Roy [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 22, 2008 12:04 PM
To: Ant Users List
Subject: Re: Class-Path not recognised
Thanks Kevin and Dominique for your quick replies,
Yes. Exception is for a class in the App1.jar which is needed by
Application.jar (main application file). What about a application
which needs multiple jar files on its classpath, does all these files
(dependencies) needs to be specified using the
Hi Ravi,
I'm assuming the exception is for a class in the App1.jar file. That's
because (unfortunately) jar files can't read jar files contained within
them. You need to place App1.jar on the file system and include it in
your command to your executable jar file.
Ex. java -classpath App1.jar -j
On Thu, May 22, 2008 at 10:29 AM, Ravi Roy <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
You are including App1.jar *inside* Application.jar. The default class
loader does not support such nesting. The Class-Path attribute refers
*files* (or URLs to those files), but App1.jar is not a
