Summary: | java.lang.IllegalStateException during build | ||||||
---|---|---|---|---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Jean-Pierre Bergamin <james> | ||||
Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> | ||||
Status: | NEW --- | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | aclement, andrew.eisenberg, f.dasoghe, mlippert | ||||
Version: | unspecified | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Jean-Pierre Bergamin
2011-11-23 07:37:26 EST
looks like an AspectJ issue. Do you have the full stack trace? I just committed some changes - i'll let you know when a dev build is through which you can try. I put in some extra debug (if you could give me the stack trace it produces, that would be great) but it will now try to recover and continue processing. Any ideas where to find the full stacktrace? The .metadata/*.log files did not contain these errors. Hi, please download a dev build of AJDT and see if that makes a difference for you? update site url should be: http://download.eclipse.org/tools/ajdt/37/dev/update I've same exact issue: Eclipse 3.7 SR1 for Linux 64 bit (BIRT package, with AspectJ included in the bundle). I installed the update suggested (from http://download.eclipse.org/tools/ajdt/37/dev/update) and now it works like a charme! After more than one day of work I got no errors. Before the update, I was getting the error after an hour or so. Is it safe to keep the update site configured in my Eclipse? How can I know when this patch will be released in a stable update site? Thank you for your support! Fabio Da Soghe that update site is safe. Builds are only released to any of our update sites if all the tests pass - and effectively a milestone or a release is purely a 'blessed' dev build, there is nothing particularly special about it. So tracking dev builds rather than waiting for releases is a fine way to work. I imagine the next 'milestone' containing this fix will be 1.7.0.M1 which won't be for about a month I think. oh and thanks for confirming it works, I dont suppose you saw the debug exception entry I was putting out? It would be nice to confirm what that contained. (In reply to comment #8) > oh and thanks for confirming it works, I dont suppose you saw the debug > exception entry I was putting out? It would be nice to confirm what that > contained. Excuse me, I'm not sure to understand: you're asking for the stack trace of the exception? If so, now I don't get it anymore... should I revert the installation? I can do that (glad to help) but is it safe for my Eclipse installation? I had some bad experience with p2 before... Alternatively I'll have to do a fresh installation in the next days, I can get the exception from that. You should be still getting it printed out. I basically modified the code so that it recovered when the problem occurred and it continues processing - so you don't think you are getting the same problem, but you are :) With the build you have installed the exception should be in either your .metadata/.log file (under your workspace), or if you start eclipse with -consolelog it should be printed out there. Don't go to too much trouble to try and discover it, I just would have liked to see it. This is what I find in the .log: !ENTRY org.eclipse.ajdt.core 4 0 2011-11-29 16:56:41.509 !MESSAGE java.lang.NullPointerException !STACK 0 java.lang.NullPointerException at org.eclipse.ajdt.core.parserbridge.ITDInserter.addSuperInterfaces(ITDInserter.java:572) at org.eclipse.ajdt.core.parserbridge.ITDInserter.addSuperInterfaces(ITDInserter.java:511) at org.eclipse.ajdt.core.parserbridge.ITDInserter.augmentType(ITDInserter.java:182) at org.eclipse.ajdt.core.parserbridge.ITDInserter.visit(ITDInserter.java:124) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1328) at org.eclipse.jdt.internal.compiler.ast.QualifiedAllocationExpression.traverse(QualifiedAllocationExpression.java:526) at org.eclipse.jdt.internal.compiler.ast.Assignment.traverse(Assignment.java:208) at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.traverse(MethodDeclaration.java:300) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1425) at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.traverse(TypeDeclaration.java:1298) at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.traverse(CompilationUnitDeclaration.java:692) at org.eclipse.ajdt.core.codeconversion.ITDAwareLookupEnvironment.completeTypeBindings(ITDAwareLookupEnvironment.java:42) at org.eclipse.jdt.internal.compiler.Compiler.resolve(Compiler.java:960) at org.eclipse.ajdt.core.parserbridge.AJCompilationUnitProblemFinder.processAJ(AJCompilationUnitProblemFinder.java:235) at org.eclipse.ajdt.ui.AJDTNameEnvironmentProvider.problemFind(AJDTNameEnvironmentProvider.java:79) at org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process_aroundBody1$advice(CompilationUnitProblemFinder.java:234) at org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:1) at org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:284) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.makeConsistent(ReconcileWorkingCopyOperation.java:190) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:89) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1266) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:151) at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.reconcile(CompositeReconcilingStrategy.java:86) at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.reconcile(JavaCompositeReconcilingStrategy.java:104) at org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:77) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:206) But I'm not sure it's related to this problem: I have no clue of when it happens... and now the aspects compilation works, differently from before where the exception blocked the AJDT from finishing its work (I had to do a project clean in order to get my application working again with my aspects in place). That isn't the exception I was expecting, as you correctly guessed :) I raised bug 365106 to cover that (an AJDT issue). I installed the update to my Springsource Tool Suite 2.7.2 (STS) installation. Unfortunately now some of the STS plugins are gone (i.e. the SpringSource Tools Suite DM Server Tools are now not loaded any more). Any ideas how to get those plugins working again as well? The dm server tools are only available for STS 2.7.2 and previous versions. If you have STS 2.7.2 installed, you should be able to get dm server tools as an add-on from the Dashboard. If you wanna use STS 2.8.0 or beyond, I would suggest to wait until the Virgo IDE (the new home of the dm server tooling) is compatible again with newer versions of STS and install them by that time. HTH, Martin (In reply to comment #14) > The dm server tools are only available for STS 2.7.2 and previous versions. If > you have STS 2.7.2 installed, you should be able to get dm server tools as an > add-on from the Dashboard. I'm using 2.7.2 with working dm Server tooling. Installing ajdt from the dev update site as suggested seems to corrupt things in STS, like e.g. the dm Server Tooling that stops working. I have not installed any other updates. (In reply to comment #15) > I'm using 2.7.2 with working dm Server tooling. Installing ajdt from the dev > update site as suggested seems to corrupt things in STS, like e.g. the dm > Server Tooling that stops working. I have not installed any other updates. Can you be more specific about what the problem is? Are there any entries in the error log? Created attachment 208668 [details]
Eclipse Error Log After Installing AJT Update
I installed the before mentioned update as well but the same result as described by Jean-Pierre. The Spring nature is gone. I'm using STS 2.7.1. I attached the error log, hope this will help...
Regards,
Andi Büchler
|