-
Notifications
You must be signed in to change notification settings - Fork 101
Workaround for JDK8/Maven bug? #151
Comments
Are you using Maven, as in the bug description? On Wed, 4 May 2016, 19:05 Dmitry Minkovsky, notifications@github.com
|
I am. Version 3.3.3. A gist with my pom.xml https://gist.github.com/dminkovsky/edd89c757d7c1f1d9c2ccfaf4e9ed34e |
Is that the full stack trace you're seeing? |
Here is the full trace:
|
Thanks. Unfortunately there doesn't seem to be any FreeBuilder in that trace, so there's no obvious way we could change the processor to avoid triggering the error in the first place, which we normally do for this kind of bug. |
That's what I feared. I posted thinking maybe someone else might know or find an answer? Others must surely be using JDK8? |
It seems to be a Maven bug, though. We've used JDK8 for a while with no problems using Gradle, Eclipse and IntelliJ. |
I configured an IntelliJ build and, yeah, this does not occur. So, Maven related. |
My best suggestion is to switch to Gradle. As a bonus, with gradle-processors you can correctly configure IntelliJ and Eclipse to use annotation processors with a single command-line call ( |
@ChrisAlice Thank you. Yeah, that's what I'm probably going to do eventually when I have a minute. But I've got it working in IntelliJ. I was enjoying building and running from the command line, but since IntelliJ was already configured to import my Maven model, when I ran into this problem I just started building from the IDE and everything has been fine. I'd rather not do everything from the IDE because it's not the best feeling for me but it's working now, so... :D |
Hey I am glad to report user error in this issue. For some reason I had needlessly configured Thank you. |
Thanks for the update, Dmitry! |
I am affected by this JDK8 bug with annotation processing. When I attempt to build my project without cleaning first, I get:
This is forcing me to clean my build every time I want to compile. I'd like to be able to build without cleaning. Does anyone know a workaround for this issue?
The text was updated successfully, but these errors were encountered: