Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 392471 - trace output for "found classpath entry" is not very helpful
Summary: trace output for "found classpath entry" is not very helpful
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.8.0 Juno   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: Kepler M3   Edit
Assignee: Thomas Watson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-19 12:29 EDT by Brian Vosburgh CLA
Modified: 2012-10-19 14:53 EDT (History)
1 user (show)

See Also:

Attachments
proposed patch (851 bytes, patch)
2012-10-19 12:29 EDT, Brian Vosburgh CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Vosburgh CLA 2012-10-19 12:29:18 EDT 
Created attachment 222589 [details]
proposed patch

While researching a problem, I turned on tracing for
    org.eclipse.osgi/debug/loader

When reviewing the resulting output in the console I noticed the following entry:

  found classpath entry [Ljava.lang.String;@37d7a424

A more helpful trace would print the contents of the string array like this:

  found classpath entry [runtime_registry_compatibility.jar]

See the attached patch.
Comment 1 Thomas Watson CLA 2012-10-19 14:52:57 EDT 
Moving to Equinox