| Change in Neon - packages taken from target platform instead of the workspace [message #1766234] |
Mon, 19 June 2017 01:28  |
Eclipse User |
|
|
|
I have an OSGi project XYZ and a target platform. The target platform exports a package "com.foo".
Situation before Neon :
if there was a workspace project ABC representing one of the bundles in the platform and exporting "com.foo", then XYZ implicitly used this workspace project as classpath.
That way when I change/add/delete a class in package "com.foo" the it became automatically available in XYZ. Also when I ctrl+click on a class from "com.foo" then the Eclipse used to navigate to the class in project ABC.
Since Neon however this is no longer the case. The target platform has absolute priority. E.g. navigating brings me the .class file from the bundle in the target platform. Changes in projects are not reflected to others. Instead I have to rebuild the whole target platform in order to get them.
Was this an intended change? Is there an option to switch to the old behaviour?
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04089 seconds
Home