Jan Torben Heuer-3 wrote: > > Try to completely eliminate the "cyclic" reference by using an interface > in > A, so that you don't need to specifiy a dependency from B to A > > > Jan >
thanks, but i think thats not a smooth solution in my case. at compilation time there is definitively not cycle, because B doesn`t need A in any way, at compilation. but maven abort the compilation with the message above. so, i see no problem at the design. i cannot understand why maven detects there an psoudo-cycle. maybe the relevant scope-option are not considered. maybe there is a possibility to set a "cycle-order" in maven? with that i could set reference A -> B before reference B -> A. maybe i can realize an order with a common parent pom-file for A and B? perhaps that the wrong way? other ideas? thanks! -- View this message in context: http://www.nabble.com/detected-reference-cycle%2C-but-there-is-no-cycle-conflict-tp15825973s177p15826737.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]
