| Access restriction: The type ResourcesPlugin is not accessible due to restriction on required librar [message #285719] | 
Tue, 24 May 2005 10:16   | 
 
Eclipse User  | 
 | 
 | 
   | 
 
Originally posted by: mark_melvin.amis.com 
 
Can anyone give me a hint here?  I just upgraded to 3.1M7 and my plugins  
now have > 100 errors due to classes not being resolved, my MANIFEST.MF  
files not declaring "singleton:=true" (in various formats...I have fixed  
all of these by searching the newsgroup...) as well as Access  
Restrictions like the following: 
 
Access restriction: The type ResourcesPlugin is not accessible due to  
restriction on required library  
 C:\path\to\eclipse3.1M7\eclipse\plugins\org.eclipse.core.res ources_3.1.0.jar 
 
I'm assuming the ResourcesPlugin is not actually restricted...at least I  
hope it isn't - or that means I have a lot of re-coding to do... 
 
What is triggering these errors?  A full clean of my workspace has not  
fixed anything. 
 
Thanks, 
Mark.
 |  
 |  
  | 
 | 
 | 
 | 
| Re: Access restriction: The type ResourcesPlugin is not accessible due   to restriction on required  [message #285742 is a reply to message #285731] | 
Tue, 24 May 2005 17:20    | 
 
Eclipse User  | 
 | 
 | 
   | 
 
Originally posted by: mark_melvin.amis.com 
 
I found the source of my pain.  One of my plug-ins was re-exporting its  
dependencies, and this was causing weirdness.  Actually, it was  
re-exporting them both in the MANIFEST.MF (which appears to work fine),  
but also in the Java Build Path > Order and Export project properties  
tab (Plug-in Dependencies was checked off as well as its source folder).  
   Unchecking this caused all of my errors to magically disappear. 
 
I'm thinking this is a bug - so I will enter this into Bugzilla. 
 
Mark. 
 
Mark Melvin wrote: 
> Thanks for the bug links.  I removed all imported plugins from my  
> workspace (only had one - pde.ui), restarted my IDE from the command  
> line with the "-clean" option, and did a full clean, and re-build on my  
> workspace and the errors are still all there. 
> <sigh> 
> I know what I'll be doing this afternoon, I guess... 
.. 
.. 
>  
> Mark. 
>  
> Ron Capelli wrote: 
>  
>> I ran into similar problems, but with core JRE classes!  e.g., 
>> 
>> Access restriction: The type String is not accessible due to  
>> restriction on required library C:\Program  
>> Files\IBM\Java142\jre\lib\core.jar 
>> 
>> This has to be a bug.  Any of the following may be related: 
>> 
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95277 
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95853 
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95167 
>> 
>> ...Ron Capelli  (Austin)
 |  
 |  
  | 
 | 
| Re: Access restriction: The type ResourcesPlugin is not accessible due   to restriction on required  [message #285748 is a reply to message #285742] | 
Tue, 24 May 2005 20:34    | 
 
Eclipse User  | 
 | 
 | 
   | 
 
Originally posted by: wassimm.ibm.canada 
 
Please NEVER tweak the Plugin Dependencies container in any way in the  
Java Build Path properties page, as you would be asking for trouble and  
you would be on your own. 
 
Wassim. 
 
Mark Melvin wrote: 
 
> I found the source of my pain.  One of my plug-ins was re-exporting its  
> dependencies, and this was causing weirdness.  Actually, it was  
> re-exporting them both in the MANIFEST.MF (which appears to work fine),  
> but also in the Java Build Path > Order and Export project properties  
> tab (Plug-in Dependencies was checked off as well as its source folder).  
>    Unchecking this caused all of my errors to magically disappear. 
 
> I'm thinking this is a bug - so I will enter this into Bugzilla. 
 
> Mark. 
 
> Mark Melvin wrote: 
>> Thanks for the bug links.  I removed all imported plugins from my  
>> workspace (only had one - pde.ui), restarted my IDE from the command  
>> line with the "-clean" option, and did a full clean, and re-build on my  
>> workspace and the errors are still all there. 
>> <sigh> 
>> I know what I'll be doing this afternoon, I guess... 
> .. 
> .. 
>>  
>> Mark. 
>>  
>> Ron Capelli wrote: 
>>  
>>> I ran into similar problems, but with core JRE classes!  e.g., 
>>> 
>>> Access restriction: The type String is not accessible due to  
>>> restriction on required library C:Program  
>>> FilesIBMJava142jrelibcore.jar 
>>> 
>>> This has to be a bug.  Any of the following may be related: 
>>> 
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95277 
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95853 
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95167 
>>> 
>>> ...Ron Capelli  (Austin) 
You should express your plugin's dependencies through the manifest.mf  
exclusively.  PDE will take care of the rest.
 |  
 |  
  | 
 | 
| Re: Access restriction: The type ResourcesPlugin is not accessible due   to restriction on required  [message #285764 is a reply to message #285748] | 
Wed, 25 May 2005 09:18   | 
 
Eclipse User  | 
 | 
 | 
   | 
 
Originally posted by: mark_melvin.amis.com 
 
Good to know.  ;o) 
 
I must have checked this off - waaay back when I was first starting with  
Eclipse many moons ago.  I'm sure I'll never mess with it again.  ;O) 
 
Mark. 
 
Wassim Melhem wrote: 
> Please NEVER tweak the Plugin Dependencies container in any way in the  
> Java Build Path properties page, as you would be asking for trouble and  
> you would be on your own. 
>  
> Wassim. 
>  
> Mark Melvin wrote: 
>  
>> I found the source of my pain.  One of my plug-ins was re-exporting  
>> its dependencies, and this was causing weirdness.  Actually, it was  
>> re-exporting them both in the MANIFEST.MF (which appears to work  
>> fine), but also in the Java Build Path > Order and Export project  
>> properties tab (Plug-in Dependencies was checked off as well as its  
>> source folder).    Unchecking this caused all of my errors to  
>> magically disappear. 
>  
>  
>> I'm thinking this is a bug - so I will enter this into Bugzilla. 
>  
>  
>> Mark. 
>  
>  
>> Mark Melvin wrote: 
>> 
>>> Thanks for the bug links.  I removed all imported plugins from my  
>>> workspace (only had one - pde.ui), restarted my IDE from the command  
>>> line with the "-clean" option, and did a full clean, and re-build on  
>>> my workspace and the errors are still all there. 
>>> <sigh> 
>>> I know what I'll be doing this afternoon, I guess... 
>> 
>> .. 
>> .. 
>> 
>>> 
>>> Mark. 
>>> 
>>> Ron Capelli wrote: 
>>> 
>>>> I ran into similar problems, but with core JRE classes!  e.g., 
>>>> 
>>>> Access restriction: The type String is not accessible due to  
>>>> restriction on required library C:Program FilesIBMJava142jrelibcore.jar 
>>>> 
>>>> This has to be a bug.  Any of the following may be related: 
>>>> 
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95277 
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95853 
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=95167 
>>>> 
>>>> ...Ron Capelli  (Austin) 
>  
> You should express your plugin's dependencies through the manifest.mf  
> exclusively.  PDE will take care of the rest. 
>  
>  
>
 |  
 |  
  | 
Powered by 
FUDForum. Page generated in 0.06108 seconds