> I have 2 Maven subprojects. The first subporject's pom.xml has a dependency
> with scope set to provided. The second subporject's pom.xml has the same
> dependency with no scope set. What does Maven do in such a situtation.

When you tried building your projects, what happens, and how does that
conflict with what you were expecting?

This list works better when you have specific problems you are trying
to diagnose/resolve rather than simply answering trivia that you can
easily test on your own or read about in various online resources. No
scope = default = compile scope, unless scope is declared in depMgmt
etc.

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to