Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354118

Summary: Some build.properties embedded library entries are not on compile classpath
Product: z_Archived Reporter: Igor Fedorenko <igor>
Component: TychoAssignee: Igor Fedorenko <igor>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: sw
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Igor Fedorenko CLA 2011-08-08 05:59:15 EDT 
source.<library>=<folder> build classpath entries should be included to project compile classpath regardless if they have corresponding Build-ClassPath elements or not. When resolving dependencies on other reactor projects, only Bundle-ClassPath entries should be added to compile classpath. So, in other words, OSGi classpath visibility rules only apply to dependencies, all classes are visible inside the same project.

For example, consider the following two projects

A/
  src1/ => source.adhoc.jar=src2/, not on Bundle-ClassPath
  src2/ => source..=src2/

B depends on A
  src/


When compiling bundle A, classes from both A/src1 and A/src2 should be available on compile classpath when compiling src2/.

When compiling bundle B, on the other hand, only classes from A/src2 (and, of course, B/src) should be available on compile classpath.
Comment 1 Tobias Oberlies CLA 2011-08-08 09:58:56 EDT 
Shouldn't this depend on the jars.compile.order?
Comment 2 Igor Fedorenko CLA 2011-08-08 10:42:05 EDT 
Yes, classpath order and compilation order should follow jars.compile.order.
Comment 4 Igor Fedorenko CLA 2011-08-09 14:08:50 EDT 
*** Bug 345254 has been marked as a duplicate of this bug. ***