Ticket #9 (closed enhancement: fixed)

Opened 4 months ago

Last modified 4 months ago

Extended configurability for application runner

Reported by: jwloka Assigned to: jwloka
Priority: major Milestone: M3
Component: dila.data Version: 0.0.2
Keywords: Cc: msridhar

Description

The current configuration of Dila requires a list of package name (patterns) that cover all target packages to be instrumented. In addition, specific packages that cannot/shouldn't be loaded with the custom class loader and classes that cannot be instrumented have to be specified by an exclusion list.

The following configuration options could allow a developer to deal with this complex configuration in a more intuitive way:

DEFAULT: nothing specified

  • classes in "java.class.path" are considered to be target classes
  • classes in "sun.boot.class.path" are library classes

EXCLUSIONS, but no inclusions specified

  • classes in "java.class.path", except EXCLUSIONS are considered to be target classes
  • classes in "sun.boot.class.path" and in EXCLUSIONS are library classes

INCLUSIONS, but no exclusions specified

  • classes in INCLUSIONS are considered to be target classes
  • all other classes are library classes

INCLUSIONS and EXCLUSIONS specified

  • classes in INCLUSIONS are considered to be target classes, except those specified in EXCLUSIONS
  • classes NOT in INCLUSIONS or in EXCLUSIONS are library classes

Change History

05/11/08 13:06:02 changed by jwloka

  • cc set to msridhar.

05/12/08 13:23:55 changed by jwloka

  • status changed from new to assigned.

05/12/08 13:24:08 changed by jwloka

  • milestone changed from M4 to M3.

05/13/08 19:22:17 changed by jwloka

  • status changed from assigned to closed.
  • resolution set to fixed.