we had this discussion already and the agreement was that we use compile-/runtime-scope for our own modules. -> you are welcome to change it.
regards, gerhard 2014-06-29 1:27 GMT+02:00 John D. Ament <[email protected]>: > Hi all > > This week, since we now have a 1.0.0, and my team was in need of > bringing up a scheduler, I told one of my guys that they must use > DeltaSpike Scheduler module. > > After a lot of investigating, we found that certain beans weren't > getting registered in AS7 due to missing dependencies on CDI SE. We > did end up hacking together a solution, but I found it odd that there > was a required dependency on CDI SE on something that should just run > fine on an app server. Looking at other modules, it seems like the > root cause is that certain modules declare provided dependencies on > each other, which is causing some dependency purgatory (not quite > hell...) between the modules and what they use. > > So I'm wondering, anytime we have cross module dependencies can we > mark them as compile (api) and runtime (impl)? Or perhaps list > something on the docs page indicating that you need this module (there > is a brief blurb on the scheduler that I found, but considering that > the other module is marked as SE only it seemed odd). > > WDYT? > > John >
