Let's break relative order or deployer name ordering backward compatibility --------------------------------------------------------------------------- Key: JBDEPLOY-233 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-233 Project: JBoss Deployers Issue Type: Feature Request Affects Versions: JBDEPLOY-2.0.8.SP1 Reporter: Richard Opalka Fix For: JBDEPLOY-2.0.9.GA, JBDEPLOY-2.1.0.Alpha1 There is a requirement to implement deployers comparison if they are "equivalent". This requirement is because of BC and should be removed ASAP IMHO. Here are the top two reasons why it should be removed: * it breaks topological ordering algorithm linear complexity * deployers should define their order using inputs/outputs only and shouldn't rely on relative order or deployer name ordering I suggest to remove this ordering from our algorithms and then fix particular deployers in AS trunk, that would fail because of wrong ordering. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira