Conflicting jars and classpath reduction
The current collection of jars in the lib/ directory includes many jars which
may not be used, many duplicated jars, and probably some conflicting jars. We
need to perform analysis to determine the dependencies among the jars and
determine which jars are required by which kepler sources (actors and base code).
#1 Updated by Dan Higgins over 12 years ago
The jars have been divided into 2 parts, with those used by the kepler base code in the $KEPLER$/lib/jar/base-jars/ directory. [All other jars in $KEPLER/lib/jar/ are used by various actors. Dependencies of each has yet to be determined.
Furthermore, a method for dynamically loading ALL jars that are in $KEPLER/lib/jar/ has been implemented. These jars are placed in the classpath on Kepler startup. This eliminates the incredible long static classpath that was previously required. (see http://www.kepler-project.org/Wiki.jsp?page=DynamicClassPathInKepler
Also, a method for adding jars inside the kar file has been implemented. see
We still need to treat all 'legacy' actor jars - i.e. figure out which jars go with which actors and are any shared.