. Removing the "implements Constants" as it is a bad pattern. Interfaces

should represent types. It also makes the UML diagrams very hard
  to follow. We're just going to use the fully qualified GraphConstants.{x}
  idiom.

. Added the Graphable interface to allow any arbitrary object to be
  manipulated like a vertex in a graph.

. Added a util package that has a dependency resolver that uses a depth first
  search to sort the dependencies for a set of objects that implement
  the Graphable interface. The resolver also works with Strings and
  lists and deps stated as lists of strings so I can resuse the test
  I wrote for the DependencyEngine in jjar.

PR:
Obtained from:
Submitted by:
Reviewed by:


git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/sandbox/graph/trunk@144586 13f79535-47bb-0310-9956-ffa450edef68

src/java/org/apache/commons/graph/TraversalOrder.java

@@ -63,13 +63,14 @@ import org.apache.commons.graph.visitor.Visitor;
  *
  * This relates to the "Strategy" design pattern.
  *
- * @version $Id: TraversalOrder.java,v 1.2 2001/11/29 14:17:33 jvanzyl Exp $
+ * @version $Id: TraversalOrder.java,v 1.3 2001/12/02 18:07:18 jvanzyl Exp $
  * @author  <A HREF="http://www.inf.fu-berlin.de/~dahm">M. Dahm</A>
  * @see DFS
  * @see BFS
  * @see Sequential 
 */
-public abstract class TraversalOrder implements Constants {
+public abstract class TraversalOrder 
+{
   protected Visitor visitor;
   protected Graph   graph;
   protected boolean stopped;