Open jmhodges opened 9 years ago
The hack I found is in the "Maven" section at the bottom of this blog post. I'm not sure what is colliding with AutoValue here. http://dresscode.renttherunway.com/blog/718
This seems to be straight up bug in maven 3.2 and 3.3. Related tickets: https://issues.apache.org/jira/browse/MCOMPILER-235 and https://issues.apache.org/jira/browse/MCOMPILER-236
A workaround is to add "
The ticket has been open for a while.
The other workaround available is using maven-compiler-plugin 3.1.
The next POM release will use
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<source>${java.version}</source>
<target>${java.version}</target>
<debug>true</debug>
<debuglevel>lines,vars,source</debuglevel>
<compilerArgument>-Werror</compilerArgument>
<compilerArgument>-Xlint:deprecation</compilerArgument>
</configuration>
</plugin>
and the properties section has been changed to update java.version to 1.7.
Upgrading to maven-compiler-plugin:3.5.1 fixes this.
The current build breaks when
mvn compile
is run twice with nomvn clean
between. I've not been able to figure out what is going wrong. I did find a hack that works where you add -proc:none to the javac compiler arguments and also add an old maven-processor-plugin to the pom, but that seems.. well, silly.Here's the errors: