Todd- Ahh, but I've tried that and it does not work as expected.
The line continuation does work, but if the line exceeds 72 bytes, the Manifest class will automatically embed a line-break when it constructs the Manifest object. This in fact can occur in the middle of a reference (as it was occurring for me). This has unexpected results and could in fact construct an unintelligible classpath for the classloader. Of course, YMMV on this. You can always "count" characters and split the lines in the right place in lieu of the Manifest constructor automatically splitting at the 72'nd byte. -----Original Message----- From: Todd Chambery [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 11:47 AM To: Ant Users List Subject: Re: Adding/extending a manifest using <ejbjar> ----- Original Message ----- From: "Eddie Bernard" <[EMAIL PROTECTED]> To: "'Ant Users List'" <[EMAIL PROTECTED]> Sent: Tuesday, January 15, 2002 1:48 PM Subject: RE: Adding/extending a manifest using <ejbjar> > After many hours of research and scouring over the java specs, here's what I > found out ... just thought I'd post this so others don't lose sleep over > this ;). > > If you specify your own manifest file, you *must* provide the > "Manifest-Version" name/value pair, otherwise it will generate an "empty" > (actually <cr><lf><cr><lf>) manifest. > > This is a restriction noted in the java specification for creating a > manifest. > > Moreover (and on a separate note), a manifest line *cannot* exceed 72 bytes > per specification. > > This means that if you're adding a "Class-Path: " attribute (which consumes > 12 of the 72 bytes allocated leaving you with only 60), you can only add 60 > characters or bytes worth of additional classpath information such as jars, > zips, classes, etc. In my case, I have over 120 bytes of information I > wanted to add to this attribute but now I'm unable to do so due to this > restriction. > You can have a classpath longer than 72 characters, but you have to wrap the classpath, comme ca: Manifest-Version: 1.0 Class-Path: library/this_is_a_jar__.jar library/another_jar_____.jar y et_another_jar.jar blahblahblahblah_________________blahblahbalhbal.j ar note the space at the beginning of the wrapped lines (this should look right if you have a monospaced font). > I don't understand why this is a restriction considering the need for J2EE > components to define its own classpath requirements. Nonetheless, it's > something to consider. > > What I'm going to have to do is add my additional third party components to > the system classpath of the J2EE server (in this case WebLogic) and limit > the manifest classpath construct to only the components that I'm > building/generating (i.e. only one jar file). > > Thanks to everyone for their help on this. If anyone has something else to > lend to this, please do so -- it will be of great value to everyone > concerned :). > > > > Cheers! > Eddie > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
