Project

General

Profile

Bug #2316

Conflicting jars and classpath reduction

Added by Kevin Ruland almost 14 years ago. Updated almost 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
core
Target version:
Start date:
12/12/2005
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2316

Description

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).

History

#1 Updated by Dan Higgins almost 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
http://www.kepler-project.org/Wiki.jsp?page=AddingJarsToKarFiles

We still need to treat all 'legacy' actor jars - i.e. figure out which jars go with which actors and are any shared.

#2 Updated by Dan Higgins almost 12 years ago

Closed and new bug (#3027) added for remaining issues

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 2316

Also available in: Atom PDF