Community
Participate
Working Groups
I20050308 To be consistent with the runtime behavior where you can have strict and loose access control to classes in required plugin, PDE needs to control the severity of access rules. Some access rules would always be flagged as errors, some would be flagged as warnings.
Added the following APIs to control access rules severity: - IAccessRule int K_ACCESSIBLE; int K_NON_ACCESSIBLE; int K_DISCOURAGED; IPath getPattern(); int getKind(); - JavaCore String COMPILER_PB_DISCOURAGED_REFERENCE; IAccessRule newAccessRule(IPath pattern, int kind); IClasspathEntry newContainerEntry( IPath containerPath, IAccessRule[] accessRules, IClasspathAttribute[] extraAttributes, boolean isExported); IClasspathEntry newLibraryEntry( IPath path, IPath sourceAttachmentPath, IPath sourceAttachmentRootPath, IAccessRule[] accessRules, IClasspathAttribute[] extraAttributes, boolean isExported); IClasspathEntry newProjectEntry( IPath path, IAccessRule[] accessRules, boolean combineAccessRules, IClasspathAttribute[] extraAttributes, boolean isExported); IClasspathEntry newVariableEntry( IPath variablePath, IPath variableSourceAttachmentPath, IPath variableSourceAttachmentRootPath, IAccessRule[] accessRules, IClasspathAttribute[] extraAttributes, boolean isExported); - IClasspathEntry boolean combineAccessRules(); IAccessRule[] getAccessRules();
Jerome, any chance the discouraged types are not in the code assist proposals? or is that a separate issue?
by discouraged, I also meant inaccessible ;-)
That's a separate issue. David is adding flags to control this.
Verified in I20050330-0500