Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: =?ISO-8859-1?Q?Sven_K=F6hler?= Newsgroups: comp.lang.java.programmer Subject: Re: a question about creating the JAR file Date: Sat, 27 Oct 2012 19:06:08 +0200 Lines: 23 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: news.dfncis.de HZmu7wzHtmeyk5fToITx+gV0bRICr+cZYFXj8FEYMZyitxfGd1bKayPr707jWSKfZFPV3bq50S Cancel-Lock: sha1:qzjHfq1V57UGtlMNikRpt6xbdGs= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121022 Thunderbird/16.0.1 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:19538 Am 27.10.2012 17:24, schrieb Jan Burse: > Jan Burse schrieb: >> >> I guess javac does not understand the Class-Path: manifest >> attribute. Right? So you would need to unpack/pack the two >> .jars into one .jar. I guess you can use something along the >> fileset in the jar ant task for this purpose, no need to >> buy an expensive tool. > > Corr.: > Somebody says javac does, since jdk 1.5: Even if javac would not support that, then I would still recommend to keep JARs seperate. If my library needs some 3rdparty library, then I have to document that, and the user has to put that 3rd party library in the classpath as well, when compiling. This allows the user to update the 3rd party library separate from my own. This also avoid duplicates in the classpath (for example, if two libraries include different versions of the same library in their JAR files). Regards, Sven