tricky cyclic dependency issue ...

hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon at test scope) ProjectX-Core: main implementations (depends on API and also on TestCommon at test scope) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to clients

tricky cyclic dependency issue ...

hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon) ProjectX-Core: main implementations (depends on API and transitively on TestCommon) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to clients of ProjectX and it

Re: tricky cyclic dependency issue ...

Move the concrete impls of your API interfaces into a seperate module. The only solution to cyclical dependencies is not to have them. Justin On Mar 25, 2009, at 8:21 AM, "Giovanni Azua" wrote: hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon at

tricky cyclic dependency issue ...

hi, I have the following setup: ProjectX-API: pure abstract layer (depends on TestCommon at test scope) ProjectX-Core: main implementations (depends on API and also on TestCommon at test scope) ProjectX-TestCommon: offers common testing facilities to all ProjectX sub-modules, but also to cl

tricky cyclic dependency issue

provided, etc. Any other ideas how to resolve this? TIA, Best regards, Giovanni -- View this message in context: http://www.nabble.com/tricky-cyclic-dependency-issue-tp22700195p22700195.html Sent from the Maven - Users mailing list archive at Nabble.com