Re: [aspectj-users] Build configuration error

[Luzius Meisser <luzius.meisser@xxxxxxxxxx>]

Hi Cyrill,

I have not seen this kind of exception
before in AJDT, seems to be an interesting one. :)
Has anyone else experienced something
similar to the error Cyrill discovered?

I did not succeed in reproducing it.
What I've tried:
I've installed Spring IDE 1.0.3 (including
GEF) and MyEclipse IDE 3.8 Beta2 on a plain eclipse 3.0. I created some
projects of different type and added Spring Bean project nature. Then,
I installed AJDT 1.1.11 and added AspectJ nature to each of the projects.
Except for getting ugly project icons (the "aj" and the "s"
decoration overlap), I did not see anything odd or any errors.

However, I did my test without the Suclipse
plugin because I wasn't able to find it. If you provide a url where I can
download it from, I'll try that as well.
The "de.bb.bje.eclipse"
bundle error in your log indicates that you have also installed the beiy
eclipse plugin. Are there any other installed plugins in your eclipse IDE?

Regards,
 Luzius


--
Luzius Meisser
IBM Centre for Java Technology, Hursley, UK
+44 19 6281 5201 (external) 243482 (internal)

luzius.meisser@xxxxxxxxxx

Cyrill Rüttimann <ruettimac@xxxxxxx> Sent by: aspectj-users-admin@xxxxxxxxxxx 04/08/2004 22:08 Please respond to aspectj-users

To:        aspectj-users@xxxxxxxxxxx         cc:                 Subject:        [aspectj-users] Build configuration error

Hi,

I have a project running on Eclipse 3.0 with the following plug-ins  
loaded:

AJDT 1.1.11
Spring IDE 1.0.3
MyEclipse IDE 3.8 Beta2
Suclipse 0.9.12

Today I introduced my first Aspect to this project:
1) Convert to AspectJ Project (Context menu from the project)

After that, the following error occures:

An internal error occured during: "Build configuration update

java.lang.IllegalArgumentException: Attempted to beginRule: R/, does  
not match outer scope rule: P/MyUsers
at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:58)
at  
org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java: 
106)
at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:200)
at  
org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:80)
at  
org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java: 
170)
at  
org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java
:95)
at  
org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace
.java:1628)
at org.eclipse.core.internal.resources.File.setContents(File.java:330)
at org.eclipse.core.internal.resources.File.setContents(File.java:423)
at  
org.eclipse.ajdt.buildconfigurator.editor.BuildProperties.writeFile(Buil
dProperties.java:319)
at  
org.eclipse.ajdt.buildconfigurator.editor.BuildProperties.updateSourceFo
lders(BuildProperties.java:553)
at  
org.eclipse.ajdt.buildconfigurator.BuildConfiguration.updateSourceFolder
s(BuildConfiguration.java:584)
at  
org.eclipse.ajdt.buildconfigurator.UpdateJob.classpathChanged(UpdateJob.
java:113)
at org.eclipse.ajdt.buildconfigurator.UpdateJob.run(UpdateJob.java:67)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)

After that, Eclipse goes wild!

- complaining about using a resource twice - two builders?
- error accessing marker type - no stack trace
- Marker id: 15656 not found - no stack trace

After killing the crashed instance, at startup the following error  
occures:

While loading class "de.bb.bje.eclipse.support.Config", thread
 
"Thread-1" timed out waiting (5000ms) for thread "Worker-7"
to finish  
starting bundle "de.bb.bje.eclipse". To avoid deadlock, thread
 
"Thread-1" is proceeding but "de.bb.bje.eclipse.support.Config"
may not  
be fully initialized.

java.lang.Exception: Generated exception.
at  
org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(Eclip
seClassLoader.java:102)
at  
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(Bun
dleLoader.java:371)
at  
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLo
ader.java:402)
at  
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(Ab
stractClassLoader.java:93)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at de.bb.bje.eclipse.BejyPlugin.startup(Unknown Source)
at de.bb.bje.eclipse.BejyPlugin.earlyStartup(Unknown Source)
at  
org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartu
pRunnable.java:81)
at  
org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.ja
va:68)
at  
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.
java:615)
at org.eclipse.core.runtime.Platform.run(Platform.java:747)
at org.eclipse.ui.internal.Workbench$15.run(Workbench.java:1283)
at java.lang.Thread.run(Thread.java:552)


Working with the project is not any longer possible ...

Anyone has a clue or works with a similar setup?


Regards,

Cyrill

_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users