On Wed, 2004-03-03 at 06:51, Andrea Chiumenti wrote: > Yesterday I've tested manifest.mf in war both on jboss and on Web Logic. > It seems that order metter, so inspecting a folder does not seem the > best practice to build a manifest Class-Path. > A solution could be to include CP jar files as xdoclet class comments, > but then what's the 'real' advantage on a plain Manifest.mf ? > > Andrew, i've tryed ant <manifest> task, but then it seems to have some > sort of limit on line lenght so a long cp is printed on several lines > and i actually don't know how to solve this.
You don't need to, that's normal for manifest files. The JAR file specification says "No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE)." See http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files for more details. Andrew. > > Kiuma > > Erik Hatcher wrote: > > > We do it manually in the <manifest> when building the EJB <jar>. I > > have not explored doing it any more elegant way myself. Yeah, it is a > > bit of a pain to do this manually and if you add a new dependency to > > your project and forget to add it to the manifest it blows up. > > > > If I was feeling more pain from it, I would certainly look for a > > solution but at this time things are stable and work so I leave well > > enough alone :) > > > > Erik > > > > On Mar 2, 2004, at 3:04 AM, Andrew Stevens wrote: > > > >> On Tue, 2004-03-02 at 06:34, Craig Berry wrote: > >> > >>> I am facing exactly the same problem, and have been trying to find > >>> solutions using xdoclet or ant tasks. I found a way to do it using > >>> ant, but it's ugly and brittle. I'm very surprised that there isn't > >>> more information available on this topic. How are other people > >>> building ejb jar manifests for EARs which include non-ejb jars which > >>> must appear in the ejb jar's manifest classpath? > >> > >> > >> I just use Ant's <manifest> task, then specify the file which that > >> generated in the appropriate attribute of the jar/war/ear task. > >> Admittedly, I'm not producing the Class-Path: value automatically from > >> the path I've defined for javac to use, but then again I don't use it > >> when I'm copying the jars into my ear either. Perhaps someone (Erik?) > >> knows a way to do it? There's not so many that it's particularly hard > >> to maintain, though. > >> > >> > >> Andrew. > >> > >> > >>> -----Original Message----- > >>> From: [EMAIL PROTECTED] on behalf > >>> of Andrea Chiumenti > >>> Sent: Mon 3/1/2004 10:46 PM > >>> To: [EMAIL PROTECTED] > >>> Cc: > >>> Subject: [Xdoclet-user] Generating Class-Path in Manifest.mf > >>> > >>> > >>> > >>> Hello, i was reading xdoclet in action, nice book! but > >>> currently i need > >>> to compile a Class-Path: element in an ear Manifest.mf. > >>> Since currently i cannot figure out how this would be possible > >>> with > >>> Xdoclet, i was wondering if XD is the right tool to do this > >>> task and if > >>> yes, how could i do. > >>> Thx in advance, > >>> kiuma ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
