[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [sapphire-dev] FW: Need some help with Sapphire...
|
If you look in your project's configuration under APT, do you see anything related to Web Services? If you do, maybe try to disable that processor. It sounds like it has some issues.
I tried google for "org.eclipse.jst.ws.internal.annotations.core.processor.AnnotationsCoreProcessorFactory" and all I saw is references to the WebTools Incubator. Could it be that JBoss Tools is pulling in some incubator components? If so, one way to work around this is to use a more pared down install for your dev eclipse as opposed to target platform. Sapphire SDK only requires Platform + JDT + PDE + WTP XML Editor.
- Konstantin
-----Original Message-----
From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Brian Fitzpatrick
Sent: Wednesday, June 22, 2011 10:10 AM
To: Sapphire project
Subject: Re: [sapphire-dev] FW: Need some help with Sapphire...
By the way, I've created a new environment, added a bunch of stuff (SVN, EGit, maven, JBoss Tools), and now I'm getting it again.
The bizarre thing is I'm getting the NPE on a file with no annotations!! Same exception though...
So something is definitely going on with the APT annotation processor. The only project I have open is my sapphire UI project, so it shouldn't be choking. And the only annotations that were there were @Override statements, which I've removed.
And when I comment out all of the annotations, the error goes away. But if I try uncommenting any of them I get the same thing.
Something is definitely still hosed...
--Fitz
"Unexpected failure running APT on the file(s): SwitchyardGraphicalEditor.java"
eclipse.buildId=I20110613-1736
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
Warning
Wed Jun 22 10:55:46 MDT 2011
Unexpected failure running APT on the file(s): SwitchyardGraphicalEditor.java
java.lang.NullPointerException
at org.eclipse.jst.ws.internal.annotations.core.processor.AnnotationsCoreProcessorFactory.getProcessorFor(AnnotationsCoreProcessorFactory.java:49)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.dispatchToFileBasedProcessor(APTDispatchRunnable.java:648)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.runAPTInFileBasedMode(APTDispatchRunnable.java:345)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.build(APTDispatchRunnable.java:683)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.access$1(APTDispatchRunnable.java:675)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable$1.run(APTDispatchRunnable.java:273)
at org.eclipse.jdt.apt.core.internal.env.BuildEnv$CallbackRequestor.acceptBinding(BuildEnv.java:611)
at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:925)
at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:577)
at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:888)
at org.eclipse.jdt.apt.core.internal.env.BaseProcessorEnv.createASTs(BaseProcessorEnv.java:859)
at org.eclipse.jdt.apt.core.internal.env.BuildEnv.createASTs(BuildEnv.java:356)
at org.eclipse.jdt.apt.core.internal.env.AbstractCompilationEnv.newBuildEnv(AbstractCompilationEnv.java:111)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.build(APTDispatchRunnable.java:283)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.run(APTDispatchRunnable.java:225)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.runAPTDuringBuild(APTDispatchRunnable.java:150)
at org.eclipse.jdt.apt.core.internal.AptCompilationParticipant.processAnnotations(AptCompilationParticipant.java:193)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.processAnnotations(AbstractImageBuilder.java:627)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:338)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:60)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
at org.eclipse.core.internal.resources.Project.build(Project.java:114)
at org.eclipse.jdt.internal.ui.util.CoreUtility$BuildJob.run(CoreUtility.java:161)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Brian Fitzpatrick" <bfitzpat@xxxxxxxxxx>
To: "Sapphire project" <sapphire-dev@xxxxxxxxxxx>
Sent: Monday, June 20, 2011 1:09:16 PM
Subject: Re: [sapphire-dev] FW: Need some help with Sapphire...
Creating a fresh Eclipse RC5 (6/13 integration build) installation seemed to have cleared up the APT generation issue.
Not sure what got stuck in its craw, but whatever it is was frustrating!
Now I'm on to see if I can verify https://bugs.eclipse.org/bugs/show_bug.cgi?id=342088
Thanks for all the help guys.
--Fitz
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>
To: "Sapphire project" <sapphire-dev@xxxxxxxxxxx>
Sent: Monday, June 20, 2011 12:28:53 PM
Subject: Re: [sapphire-dev] FW: Need some help with Sapphire...
I think the stack trace made me think of other potential causes, but it is quite likely that you are running into the Eclipse APT bug that we’ve all seen repeatedly.
In certain cases, APT just doesn’t get invoked on some projects. In cases I’ve seen this, I was able to solve the problem by closing a few annotation processing dependent projects in the workspace until the one that I need then started to build. It’s like Eclipse APT gets overwhelmed and starts forgetting about things.
When I tried debugging it a while ago, I convinced myself that Sapphire annotation processor doesn’t even get called on some projects when APT gets into this state. Never was able to come up with a concise description of the problem to open a bug on the JDT team.
- Konstantin
From: sapphire-dev-bounces@xxxxxxxxxxx [mailto:sapphire-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Amerson
Sent: Monday, June 20, 2011 11:18 AM
To: Sapphire project
Subject: Re: [sapphire-dev] FW: Need some help with Sapphire...
I have seen very flaky behavior with the annotations processor in Eclipse. For the record I have never seen it correctly generate classes for the sample project included in sapphire CVS. On my own projects I've seen it fail to generate classes but it turns out there was something I was doing in my model classes that the sapphire processor didn't like. I solved that problem by taking off the @GeneratedImpl annotation one-by-one on my classes until the processor started working. Then I added my model classes back one-by-one until I could find the one that was causing it to act up and I could look for issues. Also I would customize the settings for the annotations processor on a per-project basis, like changing the generated folder name and causing an explicit rebuild, that would sometimes get the processor "unstuck" for me.
I don't know if any of that will help you, just wanted to let you know my experiences.
On Mon, Jun 20, 2011 at 12:57 PM, Konstantin Komissarchik < konstantin.komissarchik@xxxxxxxxxx > wrote:
Forwarding to sapphire-dev in case someone else has encountered this issue and knows the cause.
- Konstantin
-----Original Message-----
From: Brian Fitzpatrick [mailto: bfitzpat@xxxxxxxxxx ]
Sent: Monday, June 20, 2011 10:55 AM
To: Konstantin Komissarchik
Subject: Re: Need some help with Sapphire...
You bet. I just wanted to make sure I wasn't doing something just idiotic...
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Konstantin Komissarchik" < konstantin.komissarchik@xxxxxxxxxx >
To: "Brian Fitzpatrick" < bfitzpat@xxxxxxxxxx >
Sent: Monday, June 20, 2011 11:53:54 AM
Subject: RE: Need some help with Sapphire...
Here is what I tried.
1. Started with a clean RC4 Java EE package install.
2. Installed everything from Sapphire 0.3 RC1 update site, letting it search other sites. This is necessary to pull in Graphiti.
3. Clean workspace. Left target platform as self.
4. Downloaded sapphire samples zip from the Sapphire 0.3 RC1 build. Unzipped it into the workspace and imported the project.
The project builds and the classes are generated. I am not seeing anything weird in the log.
With your permission, I'd like to forward this thread to sapphire-dev as someone else on the list may have encountered this problem or if we figure out the resolution, that may be of benefit to someone else.
- Konstantin
-----Original Message-----
From: Brian Fitzpatrick [mailto: bfitzpat@xxxxxxxxxx ]
Sent: Monday, June 20, 2011 10:39 AM
To: Konstantin Komissarchik
Subject: Re: Need some help with Sapphire...
I used this one:
http://download.eclipse.org/eclipse/downloads/drops/I20110613-1736/index.php
It was the latest RC5-ish Eclipse Indigo build from June 13.
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Konstantin Komissarchik" < konstantin.komissarchik@xxxxxxxxxx >
To: "Brian Fitzpatrick" < bfitzpat@xxxxxxxxxx >
Sent: Monday, June 20, 2011 11:22:29 AM
Subject: RE: Need some help with Sapphire...
Perhaps this unrelated annotation processor blowing up is preventing Sapphire annotation processor from running. What was your base (which version, which package) that you installed Sapphire SDK into?
Let me try now with RC4 Java EE package.
- Konstantin
-----Original Message-----
From: Brian Fitzpatrick [mailto: bfitzpat@xxxxxxxxxx ]
Sent: Monday, June 20, 2011 10:13 AM
To: Konstantin Komissarchik
Subject: Re: Need some help with Sapphire...
If it helps at all I'm seeing it when I try to generate anything in the samples plug-in as well for the MapEditor...
Looks like I have all the plug-ins intact. So I'm not sure why it's failing to generate the classes...
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
----- Original Message -----
From: "Brian Fitzpatrick" < bfitzpat@xxxxxxxxxx >
To: "Konstantin Komissarchik" < konstantin.komissarchik@xxxxxxxxxx >
Sent: Monday, June 20, 2011 10:54:38 AM
Subject: Need some help with Sapphire...
Hey Konstantin,
I hate to put this in the forum because it's just so damn stupid.
I've grabbed the latest RC for Indigo and have Sapphire installed along with my Switchyard editor based in Sapphire...
But I can't get it to build the generated classes. I have the annotation processing turned on in the project. I'm not seeing any errors when I open my sdef in the SDEF editor...
I do see this message in my .log:
java.lang.NullPointerException
at org.eclipse.jst.ws.internal.annotations.core.processor.AnnotationsCoreProcessorFactory.getProcessorFor(AnnotationsCoreProcessorFactory.java:49)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.dispatchToFileBasedProcessor(APTDispatchRunnable.java:648)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.runAPTInFileBasedMode(APTDispatchRunnable.java:345)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.build(APTDispatchRunnable.java:683)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.access$1(APTDispatchRunnable.java:675)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable$1.run(APTDispatchRunnable.java:273)
at org.eclipse.jdt.apt.core.internal.env.BuildEnv$CallbackRequestor.acceptBinding(BuildEnv.java:611)
at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:925)
at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:577)
at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:888)
at org.eclipse.jdt.apt.core.internal.env.BaseProcessorEnv.createASTs(BaseProcessorEnv.java:859)
at org.eclipse.jdt.apt.core.internal.env.BuildEnv.createASTs(BuildEnv.java:356)
at org.eclipse.jdt.apt.core.internal.env.AbstractCompilationEnv.newBuildEnv(AbstractCompilationEnv.java:111)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.build(APTDispatchRunnable.java:283)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.run(APTDispatchRunnable.java:225)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.runAPTDuringBuild(APTDispatchRunnable.java:150)
at org.eclipse.jdt.apt.core.internal.AptCompilationParticipant.processAnnotations(AptCompilationParticipant.java:193)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.processAnnotations(AbstractImageBuilder.java:627)
at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:338)
at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:60)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Any ideas?
--Fitz
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
--
Greg Amerson ( @greg_amerson )
Liferay, Inc. ( #liferay )
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
_______________________________________________
sapphire-dev mailing list
sapphire-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/sapphire-dev
