On Thu, May 22, 2008 at 5:42 PM, Toomey, Kevin H (ATS, IT) <[EMAIL PROTECTED]> wrote: > "What about a application which needs multiple jar files on its > classpath, does all these files (dependencies) needs to be specified > using the -classpath attribute on command line" > > Yes. > Not quite. The Class-path attribute in a jar manifest is used to specific relative or absolute files that are to be added to the classpath when one uses java -jar. The filenames are relative to the jar file.
so having Class-path: App1.jar in the manifest of X.jar, and placing App1.jar and X.jar in /opt/testing/X one can do java -jar /opt/testing/X/X.jar, and App1.jar will be picked up. Peter > Do a search on "executable jar file dependencies" and you'll come across > many articles 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 from MANIFEST.MF > > 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 -classpath attribute on > command line .. There is no other way ? > > Dominique : App1.jar is included in root of Application.jar so it is > physical file itself in the Application.jar ? > Regards, > Ravi > > On Thu, May 22, 2008 at 9:20 PM, Toomey, Kevin H (ATS, IT) > <[EMAIL PROTECTED]> wrote: >> 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 -jar Application.jar >> >> Thanks, >> Kevin >> >> -----Original Message----- >> From: Ravi Roy [mailto:[EMAIL PROTECTED] >> Sent: Thursday, May 22, 2008 11:29 AM >> To: Ant Users List >> Subject: Class-Path not recognised from MANIFEST.MF >> >> Hi All, >> >> My apologies if I am missing something obivious, I have the following >> test build.xml, in which I am trying to create a executable JAR, I am >> specifying the Class-Path which is needed by the application at >> runtime but application reports NoClassDefFound error... >> >> Class-Path and Main-Class attribute are fine the Manifest.MF.. But >> looked very strange that is come with NoClassDefFoundError.. >> >> Does soembody knows the clue what is wrong ? >> >> Thanks in advance. >> >> Regards, >> Ravi. >> >> >> <project name="Test Executable application" default="main"> >> >> <target name="main" depends="manifest.creation"> <jar >> destfile="Application.jar" manifest="manifest.mf" update="false"> >> <fileset dir="${basedir}"> >> <include name="*com/**" /> >> <include name="App1.jar" /> >> </fileset> >> </jar> >> </target> >> >> <target name="manifest.creation"> >> <manifest file="MANIFEST.MF"> >> <attribute name="Main-Class" value="com.maycompany.test.HelloMain" >> /> >> <attribute name="Class-Path" value="App1.jar" /> </manifest> >> </target> >> >> </project> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional > >> commands, e-mail: [EMAIL PROTECTED] >> >> >> >> ********************************************************************** >> *** This communication, including attachments, is for the exclusive >> use of addressee and may contain proprietary, confidential and/or >> privileged information. If you are not the intended recipient, any >> use, copying, disclosure, dissemination or distribution is strictly >> prohibited. If you are not the intended recipient, please notify the >> sender immediately by return e-mail, delete this communication and >> destroy all copies. >> ********************************************************************** >> *** >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional > >> commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] For additional > commands, e-mail: [EMAIL PROTECTED] > > > > ************************************************************************* > This communication, including attachments, is > for the exclusive use of addressee and may contain proprietary, > confidential and/or privileged information. If you are not the intended > recipient, any use, copying, disclosure, dissemination or distribution is > strictly prohibited. If you are not the intended recipient, please notify > the sender immediately by return e-mail, delete this communication and > destroy all copies. > ************************************************************************* > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
