i tried different things and my guess is that the problems occur because the problematic module is a webapplication running in the lightweight jetty container. it seems that the jetty-classloader cannot cope with some classpath entries. all other non-webapp components i am using with the generated MANIFEST.MF are working fine.
i heard already some issues about webcontainers and referencing classpaths, so i suspect the same problem with my app. ----- manuel aldana aldana((at))gmx.de software-engineering blog: http://www.aldana-online.de -- View this message in context: http://www.nabble.com/classpath-entries-in-maven-archiver-generated-MANIFEST.MF-cannot-be-referenced-tp17229567p17232146.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
