Project

General

Profile

Bug #981

Eclipsoid classpath container does not expose included for in-workspace references

Added by Henning Blohm about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
z2-base-tools-eclipsoid
Target version:
Start date:
28.02.2013
Due date:
% Done:

100%

Estimated time:
origin:

Description

When referencing a Z project from a Z project in an eclipse workspace, Eclipsoid creates an Eclipse project references between the two projects.

If the dependent project however included libs from the dependency project, say via

java.publicInclude=project2/something

then those are are not exposed via the eclipse project reference.Point is: The Eclipse class path container of the dependency project does not contain all libs from all include components of its module (looking for component type java would be sufficient).

Workaround: Expose them manually by fixing the eclipse project definition of the dependency project.

Also available in: Atom PDF