Hi Paul, Sorry, yea, I've been a little frustrated dealing with manifest entries and transitive dependencies (last post). I've solved my problems for the most part.
For the below issue what was happening is Maven2 (Plexutils I think) is generating the manifest file and not copying the EXACT string between my tags. It is formatting it which I found very odd, I would get: Class-Path: lib/mylib1.jar ...... lib/mylib 1.jar lib/mylib2.jar... lib/mylib3. jar etc. it actually works during runtime, its looks ugly as sin. I'm using addClassPath now so I don't have the generated manifest to post (again sorry) which led me to my other post about transitive dependencies and best practices (I now have a duplicate dependency entries in the parent and transitive dependencies explicilty listed in order to give them a scope of provided so they don't appear in my EAR). FYI, I really think the transitive dependencies should be completely optional. In my case I had like 4-5 that crept in which would royally screw up a JBoss deploy (like log4j, commons-logging, xerces, etc.). Thanks! -aps On 10/25/06, pjungwir <[EMAIL PROTECTED]> wrote:
Hello, Could you please post your MANIFEST.MF file so we can see what "royally screwed up" means? Thanks, Paul Alexander Sack-3 wrote: > > Hi Everybody, > > I did check the email archives on this one and I'm not sure what's what... > > If I specify a manifest entry such as: > > <archive> > <manifestEntries> > <Class-Path>lib/some1.jar lib/some2.jar lib/some3.jar lib/some4.jar > lib/some5.jar</Class-Path> > </manifestEntries> > </archive> --> > > The actual manifest entry is royally screwed up in terms of formatting. > I'm > porting projects so I realize I need to play around with dependencies so I > can just use the addClassPath entry, but shouldn't this work regardless? > > Also, can someone tell me the difference between compile, runtime, and > provided with respect to the <addClassPath> tag? Its not very obvious from > the doc (or I'm looking at the wrong doc). > > Thanks! > > -aps > > -- > "What lies behind us and what lies in front of us is of little concern to > what lies within us." -Ralph Waldo Emerson > > -- View this message in context: http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7001669 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "What lies behind us and what lies in front of us is of little concern to what lies within us." -Ralph Waldo Emerson
