>> I have several modules that have a dependency on a PERSISTENCE module. Said Persistence module has a bunch of dependencies on jars of scope "provided" because they will actually be available directly in the app server's out-of-the-box libraries. My modules that depend on Persistence need to see the libraries that Persistence declares in its Pom, both for compilation and for tests (UTs are run outside of the app server), BUT since those jars are declared with scope "provided" in the Persistence module's Pom, the command line build fails <<
I can see how "provided" is of limited usefulness in this situation, being non-transitive. So why not use "compile" scope and filter those jars out when you build your deployable war/ear? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
