Good day to you, Chris, Open an issue in [1], probably under the Dependencies component.
Thanks, Franz [1] http://jira.codehaus.org/browse/MNG Chris Eldredge wrote: > > I've noticed the following problem: > > module a depends on commons-lang (scope compile) > module b depends on commons-lang (scope provided) > module c depends on module a (scope test) > module c depends on module b (scope provided) > > If I run mvn on the top level pom (with a module set) the compile of > module c fails because the test scope wins (meaning that source code in > src/main/java does not have commons-lang in the classpath). > > If I run mvn on module c only, the provided scope wins, and everything > works fine. > > Changing module a to depend on commons-lang (scope provided) resolved > this issue, but the inconsistency is there nonetheless. > > The inconsistency seems to be that in a reactor build, module > dependencies are provided by MavenProject instances, whereas when the > individual module is built, the module dependency is processed like any > other from the pom in the repository. So I think the bug is in how > module dependencies are processed. > > Should I open an issue in JIRA? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-m2--Scoping-inconsistency-with-multi-module-build-tf2966519s177.html#a8312862 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
