Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Provide Maven integration instruction

See original GitHub issue

See a well explained Gradle integration example. Would be good

To confirm if the tool would work with maven
If yes, a sample project would help.

BTW, tried on my maven project and struck with below error. Any help would be appreciated.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project myapp: Compilation failure [ERROR] javac: invalid flag: -Xep:PatchChecks:Piranha [ERROR] Usage: javac <options> <source files> [ERROR] use --help for a list of possible options

Issue Analytics

State:
Created 3 years ago
Comments:16 (9 by maintainers)

Top GitHub Comments

2reactions

mkr-plsecommented, Apr 7, 2020

@sivacoder I have updated instructions for Maven. See here.

There were a few typos in your pom.xml. -Xep:PatchChecks:Piranha -Xep:PatchLocation:IN_PLACE should have been -XepPatchChecks:Piranha -XepPatchLocation:IN_PLACE.

It works for the example given for PiranhaJava. For the specific example given by you, since the flag name is a string literal (“dummy-flag”) as opposed to some symbol, Piranha fails to refactor. If this is a blocker, let us know. It will be a simple fix to the check here.

1reaction

msridharcommented, Apr 4, 2020

I think you need to combine all the error prone arguments into a single Maven compiler arg when Error Prone is used as a plugin. See the example here:

https://github.com/google/error-prone/issues/1242#issuecomment-554964390