Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354118 - Some build.properties embedded library entries are not on compile classpath
Summary: Some build.properties embedded library entries are not on compile classpath
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Fedorenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 345254 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-08 05:59 EDT by Igor Fedorenko CLA
Modified: 2021-04-28 16:54 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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. ***