We've been down this road before, only to find out you had one valid argument. And that was implemented as part of domino ordering. Wrt P1), we've already discussed that, and my decision still stands. Doing across stages checks is nothing more to me than supporting someone else's laziness by not taking the time to do proper check or testing before. As for P2) why would you even need to compare two deployers? CompareTo code really comes in use when you as a user actually get a hold of two instances and try to compare them. Users/devs should never have to compare two deployers. Wtr "suggestions". You came up with a clear case of cycle dependency, proposed some fuzzy logic solution, put "bugs" label on existing code and you now expect us to drop everything to support your claims? The reality is that apart from you we haven't had any deployers ordering issues. I do give you credit for previous example and suggestion for a fix, but in this case, not only you're repeating yourself, I think you're just plain wrong. If something is a clear example of a cycle, perhaps you can somehow "avoid" it per example use case, but I doubt there is any nice non-complex aka human readable algorithm to solve it. And that's what it matters at the end - users should be able to order deployers with simple paper drawing. In my mind this definitely excludes your fuzzy/custom logic, otherwise we would have to have a RichardO book of custum rules to follow. ;-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262386#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...