2009/5/8 Jörg Schaible <[email protected]>: >> E.g. if project P has test scoped dependency to a LIB1, and compile scoped >> dependency to LIB2, while LIB2 has compile scope dependency to LIB1, >> currently project P's war will wrongly end up without LIB1 included. > > This is the whole point: This is not wrong, Maven did it right! Actually we > use scope narrowing to trim down dependencies that are not needed/only > needed for test or provided by the container.
I don't follow that logic, adding a test dependency shouldn't affect the compile classpath. What's a use case for scope-narrowing? I've had scopes being narrowed before due to bugs (such as MNG-2686) and they're pretty hard to track down in large dependency trees. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
