Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » AspectJ » ADJT and workspace build errors
ADJT and workspace build errors [message #7123] Tue, 15 October 2002 01:35 Go to next message
Eclipse UserFriend
Originally posted by: stephen.Townsend.impactblue.com

Hello,

I have been able to successful use AspectJ as long as the workspace in under
the Eclipse workspace directory (default.) I need to be able to place
workspace directories in other locations. Doing so results in build errors,
even on saving (see below.)

I have not set the project as an AspectJ project so I would not assume this
to be a problem. Any how here's what I get when saving a file. Hope someone
can help.

org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderExce
ption: Attempt to load class "org.eclipse.ajdt.internal.builder.Builder"
from deactivated plug-in "org.eclipse.ajdt.ui".

at
org.eclipse.core.internal.plugins.PluginClassLoader.shouldLo okForClass(Plugi
nClassLoader.java:206)

at
org.eclipse.core.internal.plugins.PluginClassLoader.findClas sParentsSelf(Plu
ginClassLoader.java:125)

at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(Delegating
URLClassLoader.java:750)

at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.load Class(Delegating
URLClassLoader.java:730)

at java.lang.ClassLoader.loadClass(ClassLoader.java:262)

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 eExecutableExten
sion(ConfigurationElement.java:102)

at
org.eclipse.core.internal.events.BuildManager.instantiateBui lder(BuildManage
r.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:3
27)

at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:1
65)

at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:1
86)

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:1
60)

at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:211)

at
org.eclipse.core.internal.resources.Workspace.endOperation(W orkspace.java:74
5)

at org.eclipse.core.internal.resources.Workspace.run(Workspace. java:1383)

at
org.eclipse.ui.actions.WorkspaceModifyOperation.run(Workspac eModifyOperation
..java:78)

at
org.eclipse.ui.texteditor.AbstractTextEditor.performSaveOper ation(AbstractTe
xtEditor.java:2329)

at
org.eclipse.ui.texteditor.AbstractTextEditor.doSave(Abstract TextEditor.java:
2183)

at org.eclipse.ui.internal.EditorManager$11.run(EditorManager.j ava:1004)

at org.eclipse.ui.internal.EditorManager$8.run(EditorManager.ja va:873)

at
org.eclipse.jface.operation.ModalContext.runInCurrentThread( ModalContext.jav
a:299)

at org.eclipse.jface.operation.ModalContext.run(ModalContext.ja va:249)

at
org.eclipse.jface.window.ApplicationWindow$1.run(Application Window.java:394)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:66)

at
org.eclipse.jface.window.ApplicationWindow.run(ApplicationWi ndow.java:391)

at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow. java:1126)

at
org.eclipse.ui.internal.EditorManager.runProgressMonitorOper ation(EditorMana
ger.java:879)

at org.eclipse.ui.internal.EditorManager.saveEditor(EditorManag er.java:1009)

at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPa ge.java:1966)

at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:32)

at org.eclipse.jface.action.Action.runWithEvent(Action.java:749 )

at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(Action
ContributionItem.java:407)

at
org.eclipse.jface.action.ActionContributionItem.handleWidget Event(ActionCont
ributionItem.java:361)

at
org.eclipse.jface.action.ActionContributionItem.access$0(Act ionContributionI
tem.java:352)

at
org.eclipse.jface.action.ActionContributionItem$ActionListen er.handleEvent(A
ctionContributionItem.java:47)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :77)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:1529)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :1291)

at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1256)

at org.eclipse.ui.internal.Workbench.run(Workbench.java:1239)

at
org.eclipse.core.internal.boot.InternalBootLoader.run(Intern alBootLoader.jav
a:775)

at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
)

at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
..java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at org.eclipse.core.launcher.Main.basicRun(Main.java:247)

at org.eclipse.core.launcher.Main.run(Main.java:703)

at org.eclipse.core.launcher.Main.main(Main.java:539)
Re: ADJT and workspace build errors [message #9301 is a reply to message #7123] Sun, 27 October 2002 12:54 Go to previous message
Eclipse UserFriend
Originally posted by: clemas.uk.ibm.com

Stephen Townsend wrote:
> I have been able to successful use AspectJ as long as the workspace in under
> the Eclipse workspace directory (default.) I need to be able to place
> workspace directories in other locations. Doing so results in build errors,
> even on saving (see below.)
> I have not set the project as an AspectJ project so I would not assume this
> to be a problem. Any how here's what I get when saving a file. Hope someone
> can help.
> org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderExce
> ption: Attempt to load class "org.eclipse.ajdt.internal.builder.Builder"
> from deactivated plug-in "org.eclipse.ajdt.ui".
> at
> org.eclipse.core.internal.plugins.PluginClassLoader.shouldLo okForClass(Plugi
> nClassLoader.java:206)

Hi Stephen,

We've had some problems with the plugin when users work outside of the
normal workspace (we did very little testing with that kind of setup).
Can you tell me which directories you want to have outside of the eclipse
workspace? The source for your project? The binaries for your project? Or
both? (We can then include the scenario in our testing)

But I'm a little confused by the fact that you say you have a non AspectJ
project and it is failing to save with an aspectJ error? Looking at the
error, the fact that it says "from deactivated plugin
'org.eclipse.ajdt.ui'" usually means something went wrong previously that
deactivated the plugin - were there other relevant errors in the metadata
log file for your eclipse workspace?

There is some magic to get the plugin re-activated, as you can see
discussed on the other thread "ADJT Plugin Loading/Build Errors".

Andy Clement
AJDT Development
Re: ADJT and workspace build errors [message #562342 is a reply to message #7123] Sun, 27 October 2002 12:54 Go to previous message
Andrew Clement is currently offline Andrew ClementFriend
Messages: 162
Registered: July 2009
Senior Member
Stephen Townsend wrote:
> I have been able to successful use AspectJ as long as the workspace in under
> the Eclipse workspace directory (default.) I need to be able to place
> workspace directories in other locations. Doing so results in build errors,
> even on saving (see below.)
> I have not set the project as an AspectJ project so I would not assume this
> to be a problem. Any how here's what I get when saving a file. Hope someone
> can help.
> org.eclipse.core.internal.boot.DelegatingURLClassLoader$Dele gatingLoaderExce
> ption: Attempt to load class "org.eclipse.ajdt.internal.builder.Builder"
> from deactivated plug-in "org.eclipse.ajdt.ui".
> at
> org.eclipse.core.internal.plugins.PluginClassLoader.shouldLo okForClass(Plugi
> nClassLoader.java:206)

Hi Stephen,

We've had some problems with the plugin when users work outside of the
normal workspace (we did very little testing with that kind of setup).
Can you tell me which directories you want to have outside of the eclipse
workspace? The source for your project? The binaries for your project? Or
both? (We can then include the scenario in our testing)

But I'm a little confused by the fact that you say you have a non AspectJ
project and it is failing to save with an aspectJ error? Looking at the
error, the fact that it says "from deactivated plugin
'org.eclipse.ajdt.ui'" usually means something went wrong previously that
deactivated the plugin - were there other relevant errors in the metadata
log file for your eclipse workspace?

There is some magic to get the plugin re-activated, as you can see
discussed on the other thread "ADJT Plugin Loading/Build Errors".

Andy Clement
AJDT Development
Previous Topic:Novice question on the use of static introductions
Next Topic:Novice question on the use of static introductions
Goto Forum:
  


Current Time: Sun Dec 22 05:22:17 GMT 2024

Powered by FUDForum. Page generated in 0.03051 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top