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]