rsmckinney
commented
4 years ago Note tests with latest versions (Manifold 2019.1.26 and Lombok 1.18.10) are working for me locally. For example, the Maven configuration wrt processor path looks like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.0</version>
<configuration>
<encoding>UTF-8</encoding>
<compilerId>javac</compilerId>
<source>11</source>
<target>11</target>
<annotationProcessorPaths>
<processorPath>
<groupId>com.local</groupId>
<artifactId>lombok</artifactId>
<version>${lombok.version}</version>
</processorPath>
<processorPath>
<groupId>systems.manifold</groupId>
<artifactId>manifold-all</artifactId>
<version>${manifold.version}</version>
</processorPath>
</annotationProcessorPaths>
<compilerArgs>
<arg>-Xplugin:Manifold</arg>
</compilerArgs>
<annotationProcessors>
<annotationProcessor>lombok.launch.AnnotationProcessorHider$AnnotationProcessor</annotationProcessor>
</annotationProcessors>
</configuration>
</plugin>
iadcode
sskorol
Running the Manifold and Lombok plugins together causes javac to crash/misbehave when there are compilation warnings/errors.
Both examples below are using these javac arguments:
Given this class as input:
...javac crashes with this exception in ManifoldJavaFileManager:
-Werrorhas no effect.When compiling this class using
-Xlint:all -Werror:...it should print the following output:
...as well as setting a nonzero exit code, and terminating without producing a .class file.
However, the last 3 lines are absent, the resulting exit code is zero, and the .class is successfully created.
Relevant versions:
Both plugins work fine on their own, or when used together with ErrorProne, so the problem appears to be specific to this combination.