Wed, 22 Jun 2011 15:07:02 -0700, /Manfred Moser/:
Use a dependency to the api with provided scope on jar or whatever code
projects you have.
And then use the implementation of the api as dependency on the ear.
Yeah, that's exactly what I'm currently doing, but it easily becomes
a nightmare with a larger project with large amount of modules, with
even larger amount of dependencies - tracking and declaring
explicitly the dependencies of these dependencies for packaging. I
want to avoid specifying implementation detail dependencies for
packaging (which may change in a next version of the main
dependency). As far as I'm aware Maven encourages the practice of
"don't repeat yourself" and the given solution obviously involves a
lot of repetitions (in terms of dependency declarations).
Say I have an EJB module which depends on the X dependency which
itself depends on DOM4J for certain parts of its implementation. I
don't want to allow my EJB module using DOM4J APIs, but I want this
dependency automatically packaged in an EAR which packages my EJB
module. I think this is quite important part of the dependency
transitivity for it to be useful.
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
