Home » Language IDEs » AspectJ » Constant "plugin activation failed" errors
| Constant "plugin activation failed" errors [message #13528] |
Mon, 09 December 2002 18:40  |
Eclipse User |
|
|
|
Originally posted by: chad_woolleyNOSPAM.choicehotels.com
Hello,
I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
org.aspectj.ajde_1.1b1), and I am still getting the following error almost
every time I restart eclipse:
Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
\"org.eclipse.ajdt.internal.builder.Builder\"
The only way I can get rid of this is to shutdown eclipse, delete (not
overwrite) the plugin directories and recopy them from the original
distribution files (and sometimes even this does not work).
Does anyone else have this error, and is there any way I can stop it? I
think saw a bug report that this was supposedly fixed, but it isn\'t fixed
for me.
Thanks,
Chad
|
|
| |
| Re: Constant "plugin activation failed" errors [message #13569 is a reply to message #13550] |
Wed, 11 December 2002 22:32  |
| Eclipse User |
|
|
|
Originally posted by: chad_woolleyNOSPAM.choicehotels.com
I am using Eclipse 2.0.1. Is this considered 2.0?
Markus Weyerhaeuser wrote:
> chad,
> what version of eclipse are u using? the current AJ plugin for
> eclipse works only for eclipse 2.0 release.
> -- markus
> Chad Woolley wrote:
> > Hello,
> >
> > I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> > org.aspectj.ajde_1.1b1), and I am still getting the following error almost
> > every time I restart eclipse:
> >
> > Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> > \"org.eclipse.ajdt.internal.builder.Builder\"
> >
> > The only way I can get rid of this is to shutdown eclipse, delete (not
> > overwrite) the plugin directories and recopy them from the original
> > distribution files (and sometimes even this does not work).
> >
> > Does anyone else have this error, and is there any way I can stop it? I
> > think saw a bug report that this was supposedly fixed, but it isn\'t fixed
> > for me.
> >
> > Thanks,
> > Chad
> >
> >
> >
> >
|
|
| |
| Re: Constant "plugin activation failed" errors [message #13611 is a reply to message #13590] |
Thu, 12 December 2002 22:42 |
| Eclipse User |
|
|
|
Originally posted by: chad_woolleyNOSPAM.choicehotels.com
Here is the exception from ...\eclipse\workspace\.metadata\.log .
This just happened 2 times in a row, even though I shut down eclipse,
deleted the plugin dirs, recopied them, and restarted eclipse. The third
try I didn't get the error. It actually seems to be getting worse, it
usually used to be fixed the first time by deleting and recopying the
plugins.
Let me know if I can provide any other information...
!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.resources".
!STACK 0
org.eclipse.core.internal.boot.DelegatingLoaderException:
org.eclipse.core.runtime.CoreException[2]:
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
at java.lang.reflect.Constructor.newInstance(Native Method)
at
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
at
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
at
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
at
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
at
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
at
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
at
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
at
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
at org.eclipse.core.runtime.Platform.run(Platform.java:416)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
at
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
at
org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
Markus Weyerhaeuser wrote:
> yes, by all means - 2.0.1 should be 2.0 API compatible.
> did you check your .log file? this is the best chance you have to
> figure out what was going wrong. do you see anything strange
> in there?
> -- markus
> Chad Woolley wrote:
> > I am using Eclipse 2.0.1. Is this considered 2.0?
> >
> > Markus Weyerhaeuser wrote:
> >
> >
> >>chad,
> >
> >
> >>what version of eclipse are u using? the current AJ plugin for
> >>eclipse works only for eclipse 2.0 release.
> >
> >
> >>-- markus
> >
> >
> >
> >>Chad Woolley wrote:
> >>
> >>>Hello,
> >>>
> >>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> >>>org.aspectj.ajde_1.1b1), and I am still getting the following error almost
> >>>every time I restart eclipse:
> >>>
> >>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> >>>\"org.eclipse.ajdt.internal.builder.Builder\"
> >>>
> >>>The only way I can get rid of this is to shutdown eclipse, delete (not
> >>>overwrite) the plugin directories and recopy them from the original
> >>>distribution files (and sometimes even this does not work).
> >>>
> >>>Does anyone else have this error, and is there any way I can stop it? I
> >>>think saw a bug report that this was supposedly fixed, but it isn\'t fixed
> >>>for me.
> >>>
> >>>Thanks,
> >>>Chad
|
|
|
| Re: Constant "plugin activation failed" errors [message #13632 is a reply to message #13611] |
Fri, 13 December 2002 18:36 |
| Eclipse User |
|
|
|
Originally posted by: chad_woolleyNOSPAM.choicehotels.com
FYI, I also have my workspace in another location outside of the eclipse
directory tree. This may be related to the problem, as mentioned in the
thread " ADJT and workspace build errors"...
Thanks,
Chad
Chad Woolley wrote:
> Here is the exception from ...\eclipse\workspace\.metadata\.log .
> This just happened 2 times in a row, even though I shut down eclipse,
> deleted the plugin dirs, recopied them, and restarted eclipse. The third
> try I didn't get the error. It actually seems to be getting worse, it
> usually used to be fixed the first time by deleting and recopying the
> plugins.
> Let me know if I can provide any other information...
> !ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> !MESSAGE Problems occurred when invoking code from plug-in:
> "org.eclipse.core.resources".
> !STACK 0
> org.eclipse.core.internal.boot.DelegatingLoaderException:
> org.eclipse.core.runtime.CoreException[2]:
> java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> at java.lang.reflect.Constructor.newInstance(Native Method)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> at
>
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> at
>
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> at
>
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> at
>
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> at
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> at
>
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> at
> org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> at
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> Markus Weyerhaeuser wrote:
> > yes, by all means - 2.0.1 should be 2.0 API compatible.
> > did you check your .log file? this is the best chance you have to
> > figure out what was going wrong. do you see anything strange
> > in there?
> > -- markus
> > Chad Woolley wrote:
> > > I am using Eclipse 2.0.1. Is this considered 2.0?
> > >
> > > Markus Weyerhaeuser wrote:
> > >
> > >
> > >>chad,
> > >
> > >
> > >>what version of eclipse are u using? the current AJ plugin for
> > >>eclipse works only for eclipse 2.0 release.
> > >
> > >
> > >>-- markus
> > >
> > >
> > >
> > >>Chad Woolley wrote:
> > >>
> > >>>Hello,
> > >>>
> > >>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> > >>>org.aspectj.ajde_1.1b1), and I am still getting the following error
almost
> > >>>every time I restart eclipse:
> > >>>
> > >>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> > >>>\"org.eclipse.ajdt.internal.builder.Builder\"
> > >>>
> > >>>The only way I can get rid of this is to shutdown eclipse, delete (not
> > >>>overwrite) the plugin directories and recopy them from the original
> > >>>distribution files (and sometimes even this does not work).
> > >>>
> > >>>Does anyone else have this error, and is there any way I can stop it? I
> > >>>think saw a bug report that this was supposedly fixed, but it isn\'t
fixed
> > >>>for me.
> > >>>
> > >>>Thanks,
> > >>>Chad
|
|
|
| Re: Constant "plugin activation failed" errors [message #13653 is a reply to message #13632] |
Fri, 13 December 2002 18:40 |
| Eclipse User |
|
|
|
Originally posted by: chad_woolleyNOSPAM.choicehotels.com
Also, I am using the increased memory -vmargs settings on startup, and it
doesn't help. Here is my command line:
D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
-DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
Thanks,
Chad
Chad Woolley wrote:
> FYI, I also have my workspace in another location outside of the eclipse
> directory tree. This may be related to the problem, as mentioned in the
> thread " ADJT and workspace build errors"...
> Thanks,
> Chad
> Chad Woolley wrote:
> > Here is the exception from ...\eclipse\workspace\.metadata\.log .
> > This just happened 2 times in a row, even though I shut down eclipse,
> > deleted the plugin dirs, recopied them, and restarted eclipse. The third
> > try I didn't get the error. It actually seems to be getting worse, it
> > usually used to be fixed the first time by deleting and recopying the
> > plugins.
> > Let me know if I can provide any other information...
> > !ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> > !MESSAGE Problems occurred when invoking code from plug-in:
> > "org.eclipse.core.resources".
> > !STACK 0
> > org.eclipse.core.internal.boot.DelegatingLoaderException:
> > org.eclipse.core.runtime.CoreException[2]:
> > java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
> > at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> > at java.lang.reflect.Constructor.newInstance(Native Method)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> > at
> >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> > at
> >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> > at
> >
>
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> > at
> > org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> > at
> >
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> > at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> > at
> > org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> > at
> >
>
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> > at
> >
org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> > at
> >
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> > Markus Weyerhaeuser wrote:
> > > yes, by all means - 2.0.1 should be 2.0 API compatible.
> > > did you check your .log file? this is the best chance you have to
> > > figure out what was going wrong. do you see anything strange
> > > in there?
> > > -- markus
> > > Chad Woolley wrote:
> > > > I am using Eclipse 2.0.1. Is this considered 2.0?
> > > >
> > > > Markus Weyerhaeuser wrote:
> > > >
> > > >
> > > >>chad,
> > > >
> > > >
> > > >>what version of eclipse are u using? the current AJ plugin for
> > > >>eclipse works only for eclipse 2.0 release.
> > > >
> > > >
> > > >>-- markus
> > > >
> > > >
> > > >
> > > >>Chad Woolley wrote:
> > > >>
> > > >>>Hello,
> > > >>>
> > > >>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> > > >>>org.aspectj.ajde_1.1b1), and I am still getting the following error
> almost
> > > >>>every time I restart eclipse:
> > > >>>
> > > >>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> > > >>>\"org.eclipse.ajdt.internal.builder.Builder\"
> > > >>>
> > > >>>The only way I can get rid of this is to shutdown eclipse, delete (not
> > > >>>overwrite) the plugin directories and recopy them from the original
> > > >>>distribution files (and sometimes even this does not work).
> > > >>>
> > > >>>Does anyone else have this error, and is there any way I can stop it?
I
> > > >>>think saw a bug report that this was supposedly fixed, but it isn\'t
> fixed
> > > >>>for me.
> > > >>>
> > > >>>Thanks,
> > > >>>Chad
|
|
|
| Re: Constant "plugin activation failed" errors [message #13674 is a reply to message #13653] |
Sun, 15 December 2002 14:38 |
 Markus Weyerhaeuser
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
chad,
i have installed a 2.0.1 release (on sun jdk 1.4.1), installed the two
aspectj 1.1 beta plugins, startet eclipse with the same runtime options
you use, created an aspectj project outside of the workspace, created a
couple of java files and corresponding aspects, compiled and started
everything. worked without getting any errors.
if you follow the procedure above, do you still get the same error?
-- markus
Chad Woolley wrote:
> Also, I am using the increased memory -vmargs settings on startup, and it
> doesn't help. Here is my command line:
>
> D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
> -DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
>
> Thanks,
> Chad
>
> Chad Woolley wrote:
>
>
>>FYI, I also have my workspace in another location outside of the eclipse
>>directory tree. This may be related to the problem, as mentioned in the
>>thread " ADJT and workspace build errors"...
>
>
>>Thanks,
>>Chad
>
>
>>Chad Woolley wrote:
>
>
>>>Here is the exception from ...\eclipse\workspace\.metadata\.log .
>
>
>>>This just happened 2 times in a row, even though I shut down eclipse,
>>>deleted the plugin dirs, recopied them, and restarted eclipse. The third
>>>try I didn't get the error. It actually seems to be getting worse, it
>>>usually used to be fixed the first time by deleting and recopying the
>>>plugins.
>
>
>>>Let me know if I can provide any other information...
>
>
>
>>>!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
>>>!MESSAGE Problems occurred when invoking code from plug-in:
>>>"org.eclipse.core.resources".
>>>!STACK 0
>>>org.eclipse.core.internal.boot.DelegatingLoaderException:
>>>org.eclipse.core.runtime.CoreException[2]:
>>>java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
>>> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
>>> at java.lang.reflect.Constructor.newInstance(Native Method)
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
>
>>> at
>>>
>>
> org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
>
>>> at
>>>
>>
> org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
>
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
>
>>> at
>>> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
>>> at
>>>
>>
> org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
>
>>> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
>
>>> at
>>> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
>>> at
>>>
>>
> org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
>
>>> at
>>>
>
> org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
>
>>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
>>> at
>>>
>>
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
>
>
>
>
>>>Markus Weyerhaeuser wrote:
>
>
>
>>>>yes, by all means - 2.0.1 should be 2.0 API compatible.
>
>
>>>>did you check your .log file? this is the best chance you have to
>>>>figure out what was going wrong. do you see anything strange
>>>>in there?
>
>
>>>>-- markus
>
>
>>>>Chad Woolley wrote:
>>>>
>>>>>I am using Eclipse 2.0.1. Is this considered 2.0?
>>>>>
>>>>>Markus Weyerhaeuser wrote:
>>>>>
>>>>>
>>>>>
>>>>>>chad,
>>>>>
>>>>>
>>>>>>what version of eclipse are u using? the current AJ plugin for
>>>>>>eclipse works only for eclipse 2.0 release.
>>>>>
>>>>>
>>>>>>-- markus
>>>>>
>>>>>
>>>>>
>>>>>>Chad Woolley wrote:
>>>>>>
>>>>>>
>>>>>>>Hello,
>>>>>>>
>>>>>>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
>>>>>>>org.aspectj.ajde_1.1b1), and I am still getting the following error
>>
>>almost
>>
>>>>>>>every time I restart eclipse:
>>>>>>>
>>>>>>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
>>>>>>>\"org.eclipse.ajdt.internal.builder.Builder\"
>>>>>>>
>>>>>>>The only way I can get rid of this is to shutdown eclipse, delete (not
>>>>>>>overwrite) the plugin directories and recopy them from the original
>>>>>>>distribution files (and sometimes even this does not work).
>>>>>>>
>>>>>>>Does anyone else have this error, and is there any way I can stop it?
>
> I
>
>>>>>>>think saw a bug report that this was supposedly fixed, but it isn\'t
>>
>>fixed
>>
>>>>>>>for me.
>>>>>>>
>>>>>>>Thanks,
>>>>>>>Chad
>
>
>
>
>
>
>
>
>
>
>
|
|
|
| Re: Constant "plugin activation failed" errors [message #15339 is a reply to message #13674] |
Thu, 16 January 2003 02:17 |
| Eclipse User |
|
|
|
Originally posted by: chad_woolleyNOSPAM.choicehotels.com
Yes. First I tried a reinstall but keeping my old workspace, and still
had the errors.
Then, I tried a reinstall completely from scratch, reconfiguring
everything from scratch. I thought this was going to fix it, didn't have
errors for several days. Then it started happening again. Same story,
reinstalling the plugins doesn't seem to really make a difference. What I
have resorted to is continually restarting eclipse until I don't get the
error. It usually takes 5-6 times. Once I get a "good" start, then I
never get the error until I restart eclipse again.
You don't have to keep pursuing this, it seems like this is specific to my
environment and nobody else is reporting these errors. I will just live
with it and try to never shutdown eclipse except when I have to reboot my
computer. Thanks for your help.
Chad
Markus Weyerhaeuser wrote:
> chad,
> i have installed a 2.0.1 release (on sun jdk 1.4.1), installed the two
> aspectj 1.1 beta plugins, startet eclipse with the same runtime options
> you use, created an aspectj project outside of the workspace, created a
> couple of java files and corresponding aspects, compiled and started
> everything. worked without getting any errors.
> if you follow the procedure above, do you still get the same error?
> -- markus
> Chad Woolley wrote:
> > Also, I am using the increased memory -vmargs settings on startup, and it
> > doesn't help. Here is my command line:
> >
> > D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
> > -DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
> >
> > Thanks,
> > Chad
> >
> > Chad Woolley wrote:
> >
> >
> >>FYI, I also have my workspace in another location outside of the eclipse
> >>directory tree. This may be related to the problem, as mentioned in the
> >>thread " ADJT and workspace build errors"...
> >
> >
> >>Thanks,
> >>Chad
> >
> >
> >>Chad Woolley wrote:
> >
> >
> >>>Here is the exception from ...\eclipse\workspace\.metadata\.log .
> >
> >
> >>>This just happened 2 times in a row, even though I shut down eclipse,
> >>>deleted the plugin dirs, recopied them, and restarted eclipse. The third
> >>>try I didn't get the error. It actually seems to be getting worse, it
> >>>usually used to be fixed the first time by deleting and recopying the
> >>>plugins.
> >
> >
> >>>Let me know if I can provide any other information...
> >
> >
> >
> >>>!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> >>>!MESSAGE Problems occurred when invoking code from plug-in:
> >>>"org.eclipse.core.resources".
> >>>!STACK 0
> >>>org.eclipse.core.internal.boot.DelegatingLoaderException:
> >>>org.eclipse.core.runtime.CoreException[2]:
> >>>java.lang.reflect.InvocationTargetException:
java.lang.NullPointerException
> >>> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> >>> at java.lang.reflect.Constructor.newInstance(Native Method)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> >
> >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> >
> >>> at
> >>> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> >
> >>> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> >
> >>> at
> >>> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> >
> >>> at
> >>>
> >
> >
org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> >
> >>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> >>> at
> >>>
> >>
> >
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> >
> >
> >
> >
> >>>Markus Weyerhaeuser wrote:
> >
> >
> >
> >>>>yes, by all means - 2.0.1 should be 2.0 API compatible.
> >
> >
> >>>>did you check your .log file? this is the best chance you have to
> >>>>figure out what was going wrong. do you see anything strange
> >>>>in there?
> >
> >
> >>>>-- markus
> >
> >
> >>>>Chad Woolley wrote:
> >>>>
> >>>>>I am using Eclipse 2.0.1. Is this considered 2.0?
> >>>>>
> >>>>>Markus Weyerhaeuser wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>chad,
> >>>>>
> >>>>>
> >>>>>>what version of eclipse are u using? the current AJ plugin for
> >>>>>>eclipse works only for eclipse 2.0 release.
> >>>>>
> >>>>>
> >>>>>>-- markus
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Chad Woolley wrote:
> >>>>>>
> >>>>>>
> >>>>>>>Hello,
> >>>>>>>
> >>>>>>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> >>>>>>>org.aspectj.ajde_1.1b1), and I am still getting the following error
> >>
> >>almost
> >>
> >>>>>>>every time I restart eclipse:
> >>>>>>>
> >>>>>>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> >>>>>>>\"org.eclipse.ajdt.internal.builder.Builder\"
> >>>>>>>
> >>>>>>>The only way I can get rid of this is to shutdown eclipse, delete (not
> >>>>>>>overwrite) the plugin directories and recopy them from the original
> >>>>>>>distribution files (and sometimes even this does not work).
> >>>>>>>
> >>>>>>>Does anyone else have this error, and is there any way I can stop it?
> >
> > I
> >
> >>>>>>>think saw a bug report that this was supposedly fixed, but it isn\'t
> >>
> >>fixed
> >>
> >>>>>>>for me.
> >>>>>>>
> >>>>>>>Thanks,
> >>>>>>>Chad
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
|
|
|
| Re: Constant "plugin activation failed" errors [message #15632 is a reply to message #15339] |
Fri, 14 February 2003 17:49 |
| Eclipse User |
|
|
|
Originally posted by: chad_woolley.NOSPAMchoicehotels.com
I think I have found the trick to get around this. If, when I start
eclipse, I go directly to Window -> Preferences -> AspectJ and click Apply
(don't have to change anything), then I don't get this error. Do not do a
refresh first, do not do a build, do not pass Go. Hopefully this will
help anyone else with this problem.
FYI, I have recreated this error on 3 differnet Win2K machines with 3
different Eclipse fresh installs. The only other custom plugin I had was
Jalopy.
Good Luck,
Chad
Chad Woolley wrote:
> Yes. First I tried a reinstall but keeping my old workspace, and still
> had the errors.
> Then, I tried a reinstall completely from scratch, reconfiguring
> everything from scratch. I thought this was going to fix it, didn't have
> errors for several days. Then it started happening again. Same story,
> reinstalling the plugins doesn't seem to really make a difference. What I
> have resorted to is continually restarting eclipse until I don't get the
> error. It usually takes 5-6 times. Once I get a "good" start, then I
> never get the error until I restart eclipse again.
> You don't have to keep pursuing this, it seems like this is specific to my
> environment and nobody else is reporting these errors. I will just live
> with it and try to never shutdown eclipse except when I have to reboot my
> computer. Thanks for your help.
> Chad
> Markus Weyerhaeuser wrote:
> > chad,
> > i have installed a 2.0.1 release (on sun jdk 1.4.1), installed the two
> > aspectj 1.1 beta plugins, startet eclipse with the same runtime options
> > you use, created an aspectj project outside of the workspace, created a
> > couple of java files and corresponding aspects, compiled and started
> > everything. worked without getting any errors.
> > if you follow the procedure above, do you still get the same error?
> > -- markus
> > Chad Woolley wrote:
> > > Also, I am using the increased memory -vmargs settings on startup, and it
> > > doesn't help. Here is my command line:
> > >
> > > D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
> > > -DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
> > >
> > > Thanks,
> > > Chad
> > >
> > > Chad Woolley wrote:
> > >
> > >
> > >>FYI, I also have my workspace in another location outside of the eclipse
> > >>directory tree. This may be related to the problem, as mentioned in the
> > >>thread " ADJT and workspace build errors"...
> > >
> > >
> > >>Thanks,
> > >>Chad
> > >
> > >
> > >>Chad Woolley wrote:
> > >
> > >
> > >>>Here is the exception from ...\eclipse\workspace\.metadata\.log .
> > >
> > >
> > >>>This just happened 2 times in a row, even though I shut down eclipse,
> > >>>deleted the plugin dirs, recopied them, and restarted eclipse. The
third
> > >>>try I didn't get the error. It actually seems to be getting worse, it
> > >>>usually used to be fixed the first time by deleting and recopying the
> > >>>plugins.
> > >
> > >
> > >>>Let me know if I can provide any other information...
> > >
> > >
> > >
> > >>>!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> > >>>!MESSAGE Problems occurred when invoking code from plug-in:
> > >>>"org.eclipse.core.resources".
> > >>>!STACK 0
> > >>>org.eclipse.core.internal.boot.DelegatingLoaderException:
> > >>>org.eclipse.core.runtime.CoreException[2]:
> > >>>java.lang.reflect.InvocationTargetException:
> java.lang.NullPointerException
> > >>> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> > >>> at java.lang.reflect.Constructor.newInstance(Native Method)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> > >
> > >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> > >
> > >>> at
> >
>>> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> > >
> > >>> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> > >
> > >>> at
> >
>>> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> > >
> > >>> at
> > >>>
> > >
> > >
> org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> > >
> > >>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> > >
> > >
> > >
> > >
> > >>>Markus Weyerhaeuser wrote:
> > >
> > >
> > >
> > >>>>yes, by all means - 2.0.1 should be 2.0 API compatible.
> > >
> > >
> > >>>>did you check your .log file? this is the best chance you have to
> > >>>>figure out what was going wrong. do you see anything strange
> > >>>>in there?
> > >
> > >
> > >>>>-- markus
> > >
> > >
> > >>>>Chad Woolley wrote:
> > >>>>
> > >>>>>I am using Eclipse 2.0.1. Is this considered 2.0?
> > >>>>>
> > >>>>>Markus Weyerhaeuser wrote:
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>chad,
> > >>>>>
> > >>>>>
> > >>>>>>what version of eclipse are u using? the current AJ plugin for
> > >>>>>>eclipse works only for eclipse 2.0 release.
> > >>>>>
> > >>>>>
> > >>>>>>-- markus
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>Chad Woolley wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>>>Hello,
> > >>>>>>>
> > >>>>>>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta
and
> > >>>>>>>org.aspectj.ajde_1.1b1), and I am still getting the following error
> > >>
> > >>almost
> > >>
> > >>>>>>>every time I restart eclipse:
> > >>>>>>>
> > >>>>>>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading
class
> > >>>>>>>\"org.eclipse.ajdt.internal.builder.Builder\"
> > >>>>>>>
> > >>>>>>>The only way I can get rid of this is to shutdown eclipse, delete
(not
> > >>>>>>>overwrite) the plugin directories and recopy them from the original
> > >>>>>>>distribution files (and sometimes even this does not work).
> > >>>>>>>
> > >>>>>>>Does anyone else have this error, and is there any way I can stop
it?
> > >
> > > I
> > >
> > >>>>>>>think saw a bug report that this was supposedly fixed, but it isn\'t
> > >>
> > >>fixed
> > >>
> > >>>>>>>for me.
> > >>>>>>>
> > >>>>>>>Thanks,
> > >>>>>>>Chad
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
|
|
| | | |
| Re: Constant "plugin activation failed" errors [message #563586 is a reply to message #13590] |
Thu, 12 December 2002 22:42 |
Chad Woolley
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
Here is the exception from ...\eclipse\workspace\.metadata\.log .
This just happened 2 times in a row, even though I shut down eclipse,
deleted the plugin dirs, recopied them, and restarted eclipse. The third
try I didn't get the error. It actually seems to be getting worse, it
usually used to be fixed the first time by deleting and recopying the
plugins.
Let me know if I can provide any other information...
!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
!MESSAGE Problems occurred when invoking code from plug-in:
"org.eclipse.core.resources".
!STACK 0
org.eclipse.core.internal.boot.DelegatingLoaderException:
org.eclipse.core.runtime.CoreException[2]:
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
at java.lang.reflect.Constructor.newInstance(Native Method)
at
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
at
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
at
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
at
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
at
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
at
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
at
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
at
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
at org.eclipse.core.runtime.Platform.run(Platform.java:416)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
at
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
at
org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
Markus Weyerhaeuser wrote:
> yes, by all means - 2.0.1 should be 2.0 API compatible.
> did you check your .log file? this is the best chance you have to
> figure out what was going wrong. do you see anything strange
> in there?
> -- markus
> Chad Woolley wrote:
> > I am using Eclipse 2.0.1. Is this considered 2.0?
> >
> > Markus Weyerhaeuser wrote:
> >
> >
> >>chad,
> >
> >
> >>what version of eclipse are u using? the current AJ plugin for
> >>eclipse works only for eclipse 2.0 release.
> >
> >
> >>-- markus
> >
> >
> >
> >>Chad Woolley wrote:
> >>
> >>>Hello,
> >>>
> >>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> >>>org.aspectj.ajde_1.1b1), and I am still getting the following error almost
> >>>every time I restart eclipse:
> >>>
> >>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> >>>\"org.eclipse.ajdt.internal.builder.Builder\"
> >>>
> >>>The only way I can get rid of this is to shutdown eclipse, delete (not
> >>>overwrite) the plugin directories and recopy them from the original
> >>>distribution files (and sometimes even this does not work).
> >>>
> >>>Does anyone else have this error, and is there any way I can stop it? I
> >>>think saw a bug report that this was supposedly fixed, but it isn\'t fixed
> >>>for me.
> >>>
> >>>Thanks,
> >>>Chad
|
|
|
| Re: Constant "plugin activation failed" errors [message #563616 is a reply to message #13611] |
Fri, 13 December 2002 18:36 |
Chad Woolley
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
FYI, I also have my workspace in another location outside of the eclipse
directory tree. This may be related to the problem, as mentioned in the
thread " ADJT and workspace build errors"...
Thanks,
Chad
Chad Woolley wrote:
> Here is the exception from ...\eclipse\workspace\.metadata\.log .
> This just happened 2 times in a row, even though I shut down eclipse,
> deleted the plugin dirs, recopied them, and restarted eclipse. The third
> try I didn't get the error. It actually seems to be getting worse, it
> usually used to be fixed the first time by deleting and recopying the
> plugins.
> Let me know if I can provide any other information...
> !ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> !MESSAGE Problems occurred when invoking code from plug-in:
> "org.eclipse.core.resources".
> !STACK 0
> org.eclipse.core.internal.boot.DelegatingLoaderException:
> org.eclipse.core.runtime.CoreException[2]:
> java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> at java.lang.reflect.Constructor.newInstance(Native Method)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> at
>
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> at
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> at
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> at
>
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> at
>
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> at
>
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> at
>
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> at
> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> at
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> at
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> at
> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> at
>
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> at
> org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> at
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> Markus Weyerhaeuser wrote:
> > yes, by all means - 2.0.1 should be 2.0 API compatible.
> > did you check your .log file? this is the best chance you have to
> > figure out what was going wrong. do you see anything strange
> > in there?
> > -- markus
> > Chad Woolley wrote:
> > > I am using Eclipse 2.0.1. Is this considered 2.0?
> > >
> > > Markus Weyerhaeuser wrote:
> > >
> > >
> > >>chad,
> > >
> > >
> > >>what version of eclipse are u using? the current AJ plugin for
> > >>eclipse works only for eclipse 2.0 release.
> > >
> > >
> > >>-- markus
> > >
> > >
> > >
> > >>Chad Woolley wrote:
> > >>
> > >>>Hello,
> > >>>
> > >>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> > >>>org.aspectj.ajde_1.1b1), and I am still getting the following error
almost
> > >>>every time I restart eclipse:
> > >>>
> > >>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> > >>>\"org.eclipse.ajdt.internal.builder.Builder\"
> > >>>
> > >>>The only way I can get rid of this is to shutdown eclipse, delete (not
> > >>>overwrite) the plugin directories and recopy them from the original
> > >>>distribution files (and sometimes even this does not work).
> > >>>
> > >>>Does anyone else have this error, and is there any way I can stop it? I
> > >>>think saw a bug report that this was supposedly fixed, but it isn\'t
fixed
> > >>>for me.
> > >>>
> > >>>Thanks,
> > >>>Chad
|
|
|
| Re: Constant "plugin activation failed" errors [message #563637 is a reply to message #13632] |
Fri, 13 December 2002 18:40 |
Chad Woolley
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
Also, I am using the increased memory -vmargs settings on startup, and it
doesn't help. Here is my command line:
D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
-DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
Thanks,
Chad
Chad Woolley wrote:
> FYI, I also have my workspace in another location outside of the eclipse
> directory tree. This may be related to the problem, as mentioned in the
> thread " ADJT and workspace build errors"...
> Thanks,
> Chad
> Chad Woolley wrote:
> > Here is the exception from ...\eclipse\workspace\.metadata\.log .
> > This just happened 2 times in a row, even though I shut down eclipse,
> > deleted the plugin dirs, recopied them, and restarted eclipse. The third
> > try I didn't get the error. It actually seems to be getting worse, it
> > usually used to be fixed the first time by deleting and recopying the
> > plugins.
> > Let me know if I can provide any other information...
> > !ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> > !MESSAGE Problems occurred when invoking code from plug-in:
> > "org.eclipse.core.resources".
> > !STACK 0
> > org.eclipse.core.internal.boot.DelegatingLoaderException:
> > org.eclipse.core.runtime.CoreException[2]:
> > java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
> > at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> > at java.lang.reflect.Constructor.newInstance(Native Method)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> > at
> >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> > at
> >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> > at
> >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> > at
> >
>
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> > at
> > org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> > at
> >
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> > at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> > at
> >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> > at
> > org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> > at
> >
>
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> > at
> >
org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> > at
> >
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> > Markus Weyerhaeuser wrote:
> > > yes, by all means - 2.0.1 should be 2.0 API compatible.
> > > did you check your .log file? this is the best chance you have to
> > > figure out what was going wrong. do you see anything strange
> > > in there?
> > > -- markus
> > > Chad Woolley wrote:
> > > > I am using Eclipse 2.0.1. Is this considered 2.0?
> > > >
> > > > Markus Weyerhaeuser wrote:
> > > >
> > > >
> > > >>chad,
> > > >
> > > >
> > > >>what version of eclipse are u using? the current AJ plugin for
> > > >>eclipse works only for eclipse 2.0 release.
> > > >
> > > >
> > > >>-- markus
> > > >
> > > >
> > > >
> > > >>Chad Woolley wrote:
> > > >>
> > > >>>Hello,
> > > >>>
> > > >>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> > > >>>org.aspectj.ajde_1.1b1), and I am still getting the following error
> almost
> > > >>>every time I restart eclipse:
> > > >>>
> > > >>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> > > >>>\"org.eclipse.ajdt.internal.builder.Builder\"
> > > >>>
> > > >>>The only way I can get rid of this is to shutdown eclipse, delete (not
> > > >>>overwrite) the plugin directories and recopy them from the original
> > > >>>distribution files (and sometimes even this does not work).
> > > >>>
> > > >>>Does anyone else have this error, and is there any way I can stop it?
I
> > > >>>think saw a bug report that this was supposedly fixed, but it isn\'t
> fixed
> > > >>>for me.
> > > >>>
> > > >>>Thanks,
> > > >>>Chad
|
|
|
| Re: Constant "plugin activation failed" errors [message #563661 is a reply to message #13653] |
Sun, 15 December 2002 14:38 |
Markus Weyerhaeuser
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
chad,
i have installed a 2.0.1 release (on sun jdk 1.4.1), installed the two
aspectj 1.1 beta plugins, startet eclipse with the same runtime options
you use, created an aspectj project outside of the workspace, created a
couple of java files and corresponding aspects, compiled and started
everything. worked without getting any errors.
if you follow the procedure above, do you still get the same error?
-- markus
Chad Woolley wrote:
> Also, I am using the increased memory -vmargs settings on startup, and it
> doesn't help. Here is my command line:
>
> D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
> -DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
>
> Thanks,
> Chad
>
> Chad Woolley wrote:
>
>
>>FYI, I also have my workspace in another location outside of the eclipse
>>directory tree. This may be related to the problem, as mentioned in the
>>thread " ADJT and workspace build errors"...
>
>
>>Thanks,
>>Chad
>
>
>>Chad Woolley wrote:
>
>
>>>Here is the exception from ...\eclipse\workspace\.metadata\.log .
>
>
>>>This just happened 2 times in a row, even though I shut down eclipse,
>>>deleted the plugin dirs, recopied them, and restarted eclipse. The third
>>>try I didn't get the error. It actually seems to be getting worse, it
>>>usually used to be fixed the first time by deleting and recopying the
>>>plugins.
>
>
>>>Let me know if I can provide any other information...
>
>
>
>>>!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
>>>!MESSAGE Problems occurred when invoking code from plug-in:
>>>"org.eclipse.core.resources".
>>>!STACK 0
>>>org.eclipse.core.internal.boot.DelegatingLoaderException:
>>>org.eclipse.core.runtime.CoreException[2]:
>>>java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
>>> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
>>> at java.lang.reflect.Constructor.newInstance(Native Method)
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
>
>>> at
>>>
>>
> org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
>
>>> at
>>>
>>
> org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
>
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
>
>>> at
>>>
>>
> org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
>
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
>
>>> at
>>> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
>>> at
>>>
>>
> org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
>
>>> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
>>> at
>>>
>>
> org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
>
>>> at
>>> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
>>> at
>>>
>>
> org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
>
>>> at
>>>
>
> org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
>
>>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
>>> at
>>>
>>
> org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
>
>
>
>
>>>Markus Weyerhaeuser wrote:
>
>
>
>>>>yes, by all means - 2.0.1 should be 2.0 API compatible.
>
>
>>>>did you check your .log file? this is the best chance you have to
>>>>figure out what was going wrong. do you see anything strange
>>>>in there?
>
>
>>>>-- markus
>
>
>>>>Chad Woolley wrote:
>>>>
>>>>>I am using Eclipse 2.0.1. Is this considered 2.0?
>>>>>
>>>>>Markus Weyerhaeuser wrote:
>>>>>
>>>>>
>>>>>
>>>>>>chad,
>>>>>
>>>>>
>>>>>>what version of eclipse are u using? the current AJ plugin for
>>>>>>eclipse works only for eclipse 2.0 release.
>>>>>
>>>>>
>>>>>>-- markus
>>>>>
>>>>>
>>>>>
>>>>>>Chad Woolley wrote:
>>>>>>
>>>>>>
>>>>>>>Hello,
>>>>>>>
>>>>>>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
>>>>>>>org.aspectj.ajde_1.1b1), and I am still getting the following error
>>
>>almost
>>
>>>>>>>every time I restart eclipse:
>>>>>>>
>>>>>>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
>>>>>>>\"org.eclipse.ajdt.internal.builder.Builder\"
>>>>>>>
>>>>>>>The only way I can get rid of this is to shutdown eclipse, delete (not
>>>>>>>overwrite) the plugin directories and recopy them from the original
>>>>>>>distribution files (and sometimes even this does not work).
>>>>>>>
>>>>>>>Does anyone else have this error, and is there any way I can stop it?
>
> I
>
>>>>>>>think saw a bug report that this was supposedly fixed, but it isn\'t
>>
>>fixed
>>
>>>>>>>for me.
>>>>>>>
>>>>>>>Thanks,
>>>>>>>Chad
>
>
>
>
>
>
>
>
>
>
>
|
|
|
| Re: Constant "plugin activation failed" errors [message #564017 is a reply to message #13674] |
Thu, 16 January 2003 02:17 |
Chad Woolley
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
Yes. First I tried a reinstall but keeping my old workspace, and still
had the errors.
Then, I tried a reinstall completely from scratch, reconfiguring
everything from scratch. I thought this was going to fix it, didn't have
errors for several days. Then it started happening again. Same story,
reinstalling the plugins doesn't seem to really make a difference. What I
have resorted to is continually restarting eclipse until I don't get the
error. It usually takes 5-6 times. Once I get a "good" start, then I
never get the error until I restart eclipse again.
You don't have to keep pursuing this, it seems like this is specific to my
environment and nobody else is reporting these errors. I will just live
with it and try to never shutdown eclipse except when I have to reboot my
computer. Thanks for your help.
Chad
Markus Weyerhaeuser wrote:
> chad,
> i have installed a 2.0.1 release (on sun jdk 1.4.1), installed the two
> aspectj 1.1 beta plugins, startet eclipse with the same runtime options
> you use, created an aspectj project outside of the workspace, created a
> couple of java files and corresponding aspects, compiled and started
> everything. worked without getting any errors.
> if you follow the procedure above, do you still get the same error?
> -- markus
> Chad Woolley wrote:
> > Also, I am using the increased memory -vmargs settings on startup, and it
> > doesn't help. Here is my command line:
> >
> > D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
> > -DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
> >
> > Thanks,
> > Chad
> >
> > Chad Woolley wrote:
> >
> >
> >>FYI, I also have my workspace in another location outside of the eclipse
> >>directory tree. This may be related to the problem, as mentioned in the
> >>thread " ADJT and workspace build errors"...
> >
> >
> >>Thanks,
> >>Chad
> >
> >
> >>Chad Woolley wrote:
> >
> >
> >>>Here is the exception from ...\eclipse\workspace\.metadata\.log .
> >
> >
> >>>This just happened 2 times in a row, even though I shut down eclipse,
> >>>deleted the plugin dirs, recopied them, and restarted eclipse. The third
> >>>try I didn't get the error. It actually seems to be getting worse, it
> >>>usually used to be fixed the first time by deleting and recopying the
> >>>plugins.
> >
> >
> >>>Let me know if I can provide any other information...
> >
> >
> >
> >>>!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> >>>!MESSAGE Problems occurred when invoking code from plug-in:
> >>>"org.eclipse.core.resources".
> >>>!STACK 0
> >>>org.eclipse.core.internal.boot.DelegatingLoaderException:
> >>>org.eclipse.core.runtime.CoreException[2]:
> >>>java.lang.reflect.InvocationTargetException:
java.lang.NullPointerException
> >>> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> >>> at java.lang.reflect.Constructor.newInstance(Native Method)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> >
> >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> >
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> >
> >>> at
> >>> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> >
> >>> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> >
> >>> at
> >>> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> >>> at
> >>>
> >>
> >
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> >
> >>> at
> >>>
> >
> >
org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> >
> >>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> >>> at
> >>>
> >>
> >
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> >
> >
> >
> >
> >>>Markus Weyerhaeuser wrote:
> >
> >
> >
> >>>>yes, by all means - 2.0.1 should be 2.0 API compatible.
> >
> >
> >>>>did you check your .log file? this is the best chance you have to
> >>>>figure out what was going wrong. do you see anything strange
> >>>>in there?
> >
> >
> >>>>-- markus
> >
> >
> >>>>Chad Woolley wrote:
> >>>>
> >>>>>I am using Eclipse 2.0.1. Is this considered 2.0?
> >>>>>
> >>>>>Markus Weyerhaeuser wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>>chad,
> >>>>>
> >>>>>
> >>>>>>what version of eclipse are u using? the current AJ plugin for
> >>>>>>eclipse works only for eclipse 2.0 release.
> >>>>>
> >>>>>
> >>>>>>-- markus
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Chad Woolley wrote:
> >>>>>>
> >>>>>>
> >>>>>>>Hello,
> >>>>>>>
> >>>>>>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta and
> >>>>>>>org.aspectj.ajde_1.1b1), and I am still getting the following error
> >>
> >>almost
> >>
> >>>>>>>every time I restart eclipse:
> >>>>>>>
> >>>>>>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading class
> >>>>>>>\"org.eclipse.ajdt.internal.builder.Builder\"
> >>>>>>>
> >>>>>>>The only way I can get rid of this is to shutdown eclipse, delete (not
> >>>>>>>overwrite) the plugin directories and recopy them from the original
> >>>>>>>distribution files (and sometimes even this does not work).
> >>>>>>>
> >>>>>>>Does anyone else have this error, and is there any way I can stop it?
> >
> > I
> >
> >>>>>>>think saw a bug report that this was supposedly fixed, but it isn\'t
> >>
> >>fixed
> >>
> >>>>>>>for me.
> >>>>>>>
> >>>>>>>Thanks,
> >>>>>>>Chad
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
|
|
|
| Re: Constant "plugin activation failed" errors [message #564271 is a reply to message #15339] |
Fri, 14 February 2003 17:49 |
Chad Woolley
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
I think I have found the trick to get around this. If, when I start
eclipse, I go directly to Window -> Preferences -> AspectJ and click Apply
(don't have to change anything), then I don't get this error. Do not do a
refresh first, do not do a build, do not pass Go. Hopefully this will
help anyone else with this problem.
FYI, I have recreated this error on 3 differnet Win2K machines with 3
different Eclipse fresh installs. The only other custom plugin I had was
Jalopy.
Good Luck,
Chad
Chad Woolley wrote:
> Yes. First I tried a reinstall but keeping my old workspace, and still
> had the errors.
> Then, I tried a reinstall completely from scratch, reconfiguring
> everything from scratch. I thought this was going to fix it, didn't have
> errors for several days. Then it started happening again. Same story,
> reinstalling the plugins doesn't seem to really make a difference. What I
> have resorted to is continually restarting eclipse until I don't get the
> error. It usually takes 5-6 times. Once I get a "good" start, then I
> never get the error until I restart eclipse again.
> You don't have to keep pursuing this, it seems like this is specific to my
> environment and nobody else is reporting these errors. I will just live
> with it and try to never shutdown eclipse except when I have to reboot my
> computer. Thanks for your help.
> Chad
> Markus Weyerhaeuser wrote:
> > chad,
> > i have installed a 2.0.1 release (on sun jdk 1.4.1), installed the two
> > aspectj 1.1 beta plugins, startet eclipse with the same runtime options
> > you use, created an aspectj project outside of the workspace, created a
> > couple of java files and corresponding aspects, compiled and started
> > everything. worked without getting any errors.
> > if you follow the procedure above, do you still get the same error?
> > -- markus
> > Chad Woolley wrote:
> > > Also, I am using the increased memory -vmargs settings on startup, and it
> > > doesn't help. Here is my command line:
> > >
> > > D:\eclipse\eclipse.exe -vmargs -Xmx256M -DproxySet=true
> > > -DproxyHost=xxx.xxx.xxx.xxx -DproxyPort=8080
> > >
> > > Thanks,
> > > Chad
> > >
> > > Chad Woolley wrote:
> > >
> > >
> > >>FYI, I also have my workspace in another location outside of the eclipse
> > >>directory tree. This may be related to the problem, as mentioned in the
> > >>thread " ADJT and workspace build errors"...
> > >
> > >
> > >>Thanks,
> > >>Chad
> > >
> > >
> > >>Chad Woolley wrote:
> > >
> > >
> > >>>Here is the exception from ...\eclipse\workspace\.metadata\.log .
> > >
> > >
> > >>>This just happened 2 times in a row, even though I shut down eclipse,
> > >>>deleted the plugin dirs, recopied them, and restarted eclipse. The
third
> > >>>try I didn't get the error. It actually seems to be getting worse, it
> > >>>usually used to be fixed the first time by deleting and recopying the
> > >>>plugins.
> > >
> > >
> > >>>Let me know if I can provide any other information...
> > >
> > >
> > >
> > >>>!ENTRY org.eclipse.core.resources 4 2 Dec 12, 2002 15:40:44.115
> > >>>!MESSAGE Problems occurred when invoking code from plug-in:
> > >>>"org.eclipse.core.resources".
> > >>>!STACK 0
> > >>>org.eclipse.core.internal.boot.DelegatingLoaderException:
> > >>>org.eclipse.core.runtime.CoreException[2]:
> > >>>java.lang.reflect.InvocationTargetException:
> java.lang.NullPointerException
> > >>> at org.eclipse.ajdt.ui.AspectJPlugin.<init>(AspectJPlugin.java:383)
> > >>> at java.lang.reflect.Constructor.newInstance(Native Method)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.internalD oPluginActivation(PluginDescriptor.java:677)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.doPluginA ctivation(PluginDescriptor.java:183)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginClassLoader.activate Plugin(PluginClassLoader.java:58)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(PluginClassLoader.java:136)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:750)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(DelegatingURLClassLoader.java:730)
> > >
> > >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:127)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.PluginDescriptor.createExe cutableExtension(PluginDescriptor.java:164)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.plugins.ConfigurationElement.creat eExecutableExtension(ConfigurationElement.java:102)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManager.java:486)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.initializeBuil der(BuildManager.java:441)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.getBuilder(Bui ldManager.java:327)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:165)
> > >
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:186)
> > >
> > >>> at
> >
>>> org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:146)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:839)
> > >
> > >>> at org.eclipse.core.runtime.Platform.run(Platform.java:416)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:160)
> > >
> > >>> at
> >
>>> org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:745)
> > >
> > >>> at
> > >>>
> > >
> > >
> org.eclipse.core.internal.resources.Resource.refreshLocal(Re source.java:974)
> > >
> > >>> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:607)
> > >>> at
> > >>>
> > >>
> > >
>
org.eclipse.jface.operation.ModalContext$ModalContextThread. run(ModalContext.java:98)
> > >
> > >
> > >
> > >
> > >>>Markus Weyerhaeuser wrote:
> > >
> > >
> > >
> > >>>>yes, by all means - 2.0.1 should be 2.0 API compatible.
> > >
> > >
> > >>>>did you check your .log file? this is the best chance you have to
> > >>>>figure out what was going wrong. do you see anything strange
> > >>>>in there?
> > >
> > >
> > >>>>-- markus
> > >
> > >
> > >>>>Chad Woolley wrote:
> > >>>>
> > >>>>>I am using Eclipse 2.0.1. Is this considered 2.0?
> > >>>>>
> > >>>>>Markus Weyerhaeuser wrote:
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>chad,
> > >>>>>
> > >>>>>
> > >>>>>>what version of eclipse are u using? the current AJ plugin for
> > >>>>>>eclipse works only for eclipse 2.0 release.
> > >>>>>
> > >>>>>
> > >>>>>>-- markus
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>>Chad Woolley wrote:
> > >>>>>>
> > >>>>>>
> > >>>>>>>Hello,
> > >>>>>>>
> > >>>>>>>I just upgraded to the latest plugins (org.eclipse.ajdt_0.6.0beta
and
> > >>>>>>>org.aspectj.ajde_1.1b1), and I am still getting the following error
> > >>
> > >>almost
> > >>
> > >>>>>>>every time I restart eclipse:
> > >>>>>>>
> > >>>>>>>Plug-in \"org.eclipse.ajdt.ui\" activation failed while loading
class
> > >>>>>>>\"org.eclipse.ajdt.internal.builder.Builder\"
> > >>>>>>>
> > >>>>>>>The only way I can get rid of this is to shutdown eclipse, delete
(not
> > >>>>>>>overwrite) the plugin directories and recopy them from the original
> > >>>>>>>distribution files (and sometimes even this does not work).
> > >>>>>>>
> > >>>>>>>Does anyone else have this error, and is there any way I can stop
it?
> > >
> > > I
> > >
> > >>>>>>>think saw a bug report that this was supposedly fixed, but it isn\'t
> > >>
> > >>fixed
> > >>
> > >>>>>>>for me.
> > >>>>>>>
> > >>>>>>>Thanks,
> > >>>>>>>Chad
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
|
|
|
Goto Forum:
Current Time: Thu Apr 18 01:38:42 GMT 2024
Powered by FUDForum. Page generated in 0.03756 seconds |
] 
Search
Help
Register
Login
Home
