Well.. Here a scenario for ya : Project A has 3 modules. A-api A-impl A-jmsserverwrapper
Then it is like this that A-impl is dependent on A-api to compile. All good so far. A-impl is dependent on A-jmsserverwrapper when running integrations tests, so a dependency with a test scope, well. still all is ok, but then... A-jmsserverwrapper also on runtime depend on A-impl to do some stuff, and therefore has a dependency to A-impl with runtime scope. This makes the project to break, it cannot any longer compile. I do understand the problem with cyclic dependencies, and of course if i turn my brain around enough i will probably find another way of organizing this code, but still i think this must be a bug. since A-impl->A-jmsserverwrapper = testscope and A-jmsserverwrapper->A-impl = runtimescope, this in my mind is not a cyclic dep. any thoughts ? /Kaare --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
