Run checks in Eclipse

[cushon]

Original issue created by alexeagle@google.com on 2012-01-29 at 07:56 PM

---

ECJ (eclipse compiler for Java) has its own representation of the source. We need to abstract our usage of the AST and symbol table to be able to operate on this representation. Then, we need to figure out where to wire in the execution of our TreeScanners.

[cushon]

Original comment posted by eaftan@google.com on 2013-02-11 at 07:42 PM

---

Our summer intern might work on this.

---

Labels: Priority-Low, Type-Enhancement

[cushon]

Original comment posted by eaftan@google.com on 2014-03-04 at 12:13 AM

---

I think the best way to go about this is to write an Eclipse plugin that runs javac/error-prone. I would be surprised if this doesn't already exist in some form. It's probably worth exploring this, since it might be really easy to do.

Increasing priority to high for the investigation.

---

Owner: eaftan@google.com
Labels: -Priority-Low, Priority-High

[JeffFaer]

Has there been any progress on this?

[cushon]

Sorry, no one is working on this currently.

[eaftan]

We would be happy to take a pull request, if anyone wants to take this on.

[onlynone]

I noticed that I'm getting the following error in eclipse after enabling error-prone:

Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (execution: default-compile, phase: compile)

According to this stackoverflow answer having an eclipse plugin would help solve this issue. Just wondering if that is related to the work proposed here.

[eperret]

This would be very useful.