-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Description
After looking at the existing delombok tools, I decided to roll my own.
So I wrote a plugin to do the job.
The way I ran delombok was to generate a command line string and then use java.lang.ProcessBuilder to run it.
This works fine unless the project is module base.
To overcome this obstacle, I renamed module-info.java to module-info.temp so it will be out of the way...
As part of the plugin process, I dumped the command line string to a file for debugging purposes.
Here is an example:
java -jar G:\MyMavenRepo\org\projectlombok\lombok\1.18.42\lombok-1.18.42.jar delombok K:\JavaProjects\MyEmployee\MyEmployee --verbose --target C:\Users\USER\AppData\Local\Temp\myDeLomboks --classpath G:\MyMavenRepo\net\datafaker\datafaker\2.5.3\datafaker-2.5.3.jar;G:\MyMavenRepo\org\projectlombok\lombok\1.18.42\lombok-1.18.42.jar;G:\MyMavenRepo\org\yaml\snakeyaml\2.5\snakeyaml-2.5.jar --module-path G:\MyMavenRepo\net\datafaker\datafaker\2.5.3\datafaker-2.5.3.jar;G:\MyMavenRepo\org\projectlombok\lombok\1.18.42\lombok-1.18.42.jar;G:\MyMavenRepo\org\yaml\snakeyaml\2.5\snakeyaml-2.5.jar
Since this is a regular Java command, it seems reasonable that it should run standalone; however, when I do, it is bringing up the Lombok install dialog and complaining that package lombok does not exist.
Am I missing something ?