Community
Participate
Working Groups
When running with -dev bin (development mode, classes loaded from <myplugin>/bin/) it would appear that class visibility filters (<export> specified/defaulted for each <library> in plugin.xml) are ignored. This changes the runtime behavior when self-hosting vs. running from jars. NOTES:
Not a committed item on the 2.0 plan. Changing resolution to LATER.
I assume this is related to what just bit me. I was happily testing along in my RuntimeWorkbench and got very confused with all the ClassNotFounds I got after building the plugins and running them as "real plugins". I eventually discovered my export was not set so the dependent plugin did not work properly. It seems somewhat important to me that the RuntimeWorkbench stick as close to possible to what would happen in the real world, I had several minutes of head-scratching confusion and concerns that I could not reproduce the problem. -Andrew
Reopen for investigation.
This was fixed but this bug report was unintentionally left open. When we create the manifest.mf the export filters from the plugin.xml are taken into account. Closing.
New Gerrit change created: https://git.eclipse.org/r/139905
Gerrit change https://git.eclipse.org/r/139905 was merged to [master]. Commit: http://git.eclipse.org/c/www.eclipse.org/eclipse.org-common.git/commit/?id=6753b96847a146d550efd7ef1c84351f706e9945