As far as I've found, currently it is not possible to specify a
dependency scope which will cause a dependency normally packaged
along with its compile scope dependencies in a final product like
EAR, but will not resolve its compile scope dependencies when
compiling the project which includes it as dependency. That's it, I
would like to use the APIs provided by a given dependency, but I
don't want to allow compiling against APIs provided by its
implementation dependencies (unless given as dependencies
explicitly), and then I want those implementation dependencies
packaged automatically in a final product.
I hope I've explained it good enough. Is what I'm after currently
possible? If not, has this been thought about before?
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
