Yeah, I did a lot of mail-archive.com searching and its a common issue. Transitive dependency tracking can be fantastic (especially for Java applications building), but for EARs its VERY dangerous since you are left with runtime exceptions to debug (treaded cast class exceptions etc.) instead of a compile time errors which defeats the whole purpose of Maven2! :D
-aps On 10/25/06, pjungwir <[EMAIL PROTECTED]> wrote:
Yeah, I wish maven wouldn't wrap the Class-Path entry, too. I'm pretty new to maven myself, so I haven't tried out multi-module builds or J2EE builds. But I think you have the right idea. Marking things provided is the surest way I know to keep transitive dependencies out of your artifacts. There is also the <exclusions> tag, but then you have to catch every path from which the dependency is coming. A lot of people seem to get bit by your problem, so perhaps a flag to exclude transitive dependencies would be a good idea. You could override it on a per-dependency basis. Paul -- View this message in context: http://www.nabble.com/Malformed-manifest-classpath-entry-tf2497595.html#a7002290 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
