maven build aborted with the following message: Diagnosis: The projects in the reactor contain a cyclic reference ... and yes, there is a cycle in the specified dependencies, like:
A -> B -> A but A needs B only for the compilation (because a class from A extends a class from B) and B needs A only for the runtime (because B calls an object of the extended class per reflection). i specified the dependency in B as <scope>runtime</scope> and in A, B is referenced per default with the option <scope>compile</scope>. so, there is no cycle conflict. any ideas? thanks, simim -- View this message in context: http://www.nabble.com/detected-reference-cycle%2C-but-there-is-no-cycle-conflict-tp15825973s177p15825973.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
