Hi all.
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 (the build actually works in Eclipse because the M2Eclipse
plugin apparently ignores the scope
for compilation, because I see all the jars in the maven dependancies in
Eclipse, but I'm straying from the point here).
Ok a basic solution would be to copy-paste all those provided-scoped
library dependencies into the Poms
of all projects that have a dependency on Persistence, but that is
cumbersome and error prone.
If anyone has a better idea, I'm a taker.
Fabien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
