No error-prone scanner registered in context #188
Comments
|
Original comment posted by tadas.subonis on 2013-09-12 at 10:25 AM I am getting the same. It prints: |
|
Original comment posted by tadas.subonis on 2013-09-12 at 10:27 AM I have another project where it works fine, but this failure in particular was in a project that uses GAE maven setup (https://code.google.com/p/appengine-maven-plugin/) |
|
Original comment posted by alexeagle@google.com on 2013-09-23 at 03:45 AM (No comment entered for this change.) Status: Accepted |
|
Original comment posted by alexeagle@google.com on 2013-09-23 at 03:55 AM Pretty easy to repro. Added an annotation processor to my build with Kohsuke's |
|
Original comment posted by alexeagle@google.com on 2013-09-23 at 03:59 AM This issue was updated by revision 7de7f24eb75b. |
|
Original comment posted by alexeagle@google.com on 2013-09-23 at 05:47 PM Eddie, it's probably better for you to take this one over; you know a lot more about the way annotation processing is wired in javac. Owner: eaftan@google.com |
|
Original comment posted by supertri@google.com on 2013-11-20 at 01:40 AM (No comment entered for this change.) Labels: -Type-NewCheck, Type-Defect |
|
Original comment posted by alexeagle@google.com on 2013-11-22 at 12:23 AM Issue #190 has been merged into this issue. |
|
Original comment posted by alexeagle@google.com on 2013-11-22 at 12:23 AM Issue #175 has been merged into this issue. |
|
Original comment posted by jkuhnert on 2013-11-22 at 12:40 AM You guys might also think about asking cgruber (at your normal internal adddress) for some brief help or ideas on this since I'd be surprised if #175 didn't pique his interest at minimum and have a few easily-at-and likely resources to ask at best to thoroughly stomp on issue..As much as it can be stomped. (See https://github.com/square/dagger/commits/master for reason I suspect cgruber (https://github.com/cgruber) may be easily seduced into some quick help ) |
|
Original comment posted by jkuhnert on 2013-11-22 at 12:44 AM |
|
Original comment posted by husayt on 2013-11-25 at 03:28 AM I have the same problem in two projects, both of which use lombok and hibernate validator annotations. |
|
Original comment posted by mark.mclaren on 2013-12-04 at 09:19 AM I also saw this issue when using hibernate-validator-annotation-processor, I found if I set the scope in the pom.xml for this artifact to runtime the issue went away (more of a workaround than a solution) |
|
Original comment posted by eaftan@google.com on 2013-12-31 at 12:55 AM I've got a fix out for review here: After the review, I'll have to merge this, do an error-prone release, and then update the version of error-prone used by the plexus-compiler-javac-errorprone plugin. Sorry for the long delay. Status: Started |
|
Original comment posted by eaftan@google.com on 2014-01-10 at 09:43 PM Fix is committed. Will do a release and do the followup work with the maven error-prone plugin. I'll update this bug when the maven plugin works out of the box. |
|
Original comment posted by eaftan@google.com on 2014-02-22 at 12:36 AM FYI, in lieu of getting plexus-compiler-javac-errorprone updated to depend on the new version of error-prone, you can override the default in your own POM file. See https://github.com/cushon/issues-import/wiki/InstallingErrorProne#Maven for how to add an explicit dependency on error-prone-core 1.1.1. I'm closing this since it works from our end. Will still send a pull request to plexus-compiler-javac-errorprone. Status: Fixed |
Original issue created by Arne.Osthues on 2013-09-12 at 10:18 AM
When I try to compile I get the error:
No error-prone scanner registered in context. Is annotation processing enabled? Please report bug to error-prone
I am using the maven configuration from the wiki. I using the maven-processor-plugin for annotation processing but without any luck. Did I miss something in my configuration?
Do you need more Information?
Using win 8 x64; java 1.7.0_25
The text was updated successfully, but these errors were encountered: