Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312988 - com.google.collect does not specify its complete classpath
Summary: com.google.collect does not specify its complete classpath
Status: RESOLVED FIXED
Alias: None
Product: Orbit
Classification: Tools
Component: bundles (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Chris Aniszczyk CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-14 17:58 EDT by Mikaël Barbero CLA
Modified: 2010-05-16 01:22 EDT (History)
1 user (show)

See Also:

Attachments
It adds the root of the bundle as a classpath entry and set it as exported (along with setting a link to the source folder) (759 bytes, patch)
2010-05-14 17:58 EDT, Mikaël Barbero 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 Mikaël Barbero CLA 2010-05-14 17:58:45 EDT 
Created attachment 168619 [details]
It adds the root of the bundle as a classpath entry and set it as exported (along with setting a link to the source folder)

Hi, 

When using the com.google.collect bundle from CVS, you have to set the bundle classpath manually by adding "." in the set of classpath entries (and set it as exported).

It has no impact on the orbit build as it is JDT's specific configuration, but it is very useful when developing with the bundle in the workspace.

Best regards,
Mikael
Comment 1 Chris Aniszczyk CLA 2010-05-16 01:21:54 EDT 
Thanks, fixed.
Comment 2 Chris Aniszczyk CLA 2010-05-16 01:22:07 EDT 
Done.