these types of cycles are common in applications. they are only a problem *iff* you want to separate your base page into a different jar than the subclass pages. if you are planning on doing that there are well known patterns for how to do that, but they will make your code more complex.
so you have to weigh whether or not the complexity is a reasonable tradeoff. -igor On Wed, Apr 25, 2012 at 3:22 AM, romanasu <[email protected]> wrote: > Copy&paste from Sonar: > > Package tangle index > 11.7% >> 46 cycles > > Dependencies to cut > 13 between packages > 16 between files > > Sonar say (probably true) that there are 'Suspect dependency (cycle)' > between packages and also between files, and then i receive a low grade on > Architecture. > > For example, one suspect cycling dependency is: > com.myPackage.TemplatePage USES com.myPackage.login.LoginPage > > If i move LoginPage to com.myPackage, sonar will be very happy, but, I don't > like this stupid solution. > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Sonar-Architecture-and-Wicket-tp4573798p4586175.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
