Community
Participate
Working Groups
When adding a JRE System Library to the build path the library should be set up with access rules that discourage access to non-API packages; this would be of great help to application developers by identifying areas of code that are not portable across Java implementations. I'll attach a suggested set of rules for a 1.4 JRE, the list would be slightly different for 1.5 etc.
Created attachment 30066 [details] Suggested 1.4.2 access rules for a JRE container
Moving to JDT Debug
Martin, I'm not sure this should be up to debug to do this. It seems more like a "development" issue that JUI might want to handle? However, this will be specific to the JRE being installed as well, which might be a nightmare to maintain.
I don't really see where JDT.UI could help here. I would rather prefer to avoid JRE specific features in JDT.UI. We could add a import/export functionality to the access rule configuration page, if that helps. In the example, the access rules are applied to the JRE container. Maybe it would be better to apply the rules internally to each of the entries and so make the feature JRE instance specific. UI-wise that would mean to offer a button on the JRE-Install Dialog that offers to initialize the access rules with the suggested rules.
*** Bug 121091 has been marked as a duplicate of this bug. ***
Not planned for 3.2
Re-opening to mark as dup.
Rather than associate rules with JREs, we plan to associate access rules with execution environments. *** This bug has been marked as a duplicate of 163444 ***
