running mvn compile twice without a clean causing duplicate classes about closure-templates HOT 5 OPEN

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

from closure-templates.

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 "false" to the maven-compiler-plugin. (This seems to currently turn on Maven's maybe-not-so bright incremental compiler. See the if-statement here and specifically the "stale sources" code.

The ticket has been open for a while.

from closure-templates.

The other workaround available is using maven-compiler-plugin 3.1.

from closure-templates.

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.

from closure-templates.

Upgrading to maven-compiler-plugin:3.5.1 fixes this.

from closure-templates.