Uploaded image for project: 'Maven Compiler Plugin'
  1. Maven Compiler Plugin
  2. MCOMPILER-236

Compilation error due to MCOMPILER-157 in deploy phase

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 3.2
    • Fix Version/s: 3.5.1
    • Labels:
      None
    • Environment:
      Maven 3.2.3, Java 1.8.0_25

      Description

      After upgrading from 3.1 to 3.2 i'm experiencing compilation errors when running deploy phase.

      It's a mult module project where plugin is configured in master pom:

      <plugin>
      				<groupId>org.apache.maven.plugins</groupId>
      				<artifactId>maven-compiler-plugin</artifactId>
      				<version>3.1</version>
      				<configuration>
      					<source>${compiler.version}</source>
      					<target>${compiler.version}</target>
      					<encoding>UTF-8</encoding>
      					<!-- -parameter: used to retrieve parameter names in runtime. i.e get parameter names for api validations -->
      					<compilerArgument>-parameters</compilerArgument>
      				</configuration>
      			</plugin>
      

      And in one of the modules like this:

       				<plugin>
      					<groupId>org.apache.maven.plugins</groupId>
      					<artifactId>maven-compiler-plugin</artifactId>
      					<configuration>
      						<annotationProcessors>
      							<!-- JPAMetaModelEntityProcessor is an annotation processor based on JSR_269 with the task of creating JPA 2 static metamodel classes -->
      							<annotationProcessor>
      								org.hibernate.jpamodelgen.JPAMetaModelEntityProcessor
      							</annotationProcessor>
      						</annotationProcessors>
      					</configuration>
      				</plugin>
      

      Common builds are all ok, but when using deploy phase i got a compiler error

      An exception has occurred in the compiler (1.8.0_25). Please file a bug at the Java Developer Connection (http://java.sun.com/webapps/bugreport)  after checking the Bug Parade for duplicates. Include your program and the following diagnostic in your report.  Thank you.
      java.lang.IllegalStateException: endPosTable already set
      	at com.sun.tools.javac.util.DiagnosticSource.setEndPosTable(DiagnosticSource.java:136)
      	at com.sun.tools.javac.util.Log.setEndPosTable(Log.java:350)
      	at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:667)
      	at com.sun.tools.javac.main.JavaCompiler.parseFiles(JavaCompiler.java:950)
      	at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.<init>(JavacProcessingEnvironment.java:892)
      	at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.next(JavacProcessingEnvironment.java:921)
      	at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1187)
      	at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)
      	at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
      	at com.sun.tools.javac.main.Main.compile(Main.java:523)
      	at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)
      	at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)
      	at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125)
      	at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
      	at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:823)
      	at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
      	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
      	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
      	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
      	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
      	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
      	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
      	at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
      	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
      	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
      	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
      	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
      	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
      	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:483)
      	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
      	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
      	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
      	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
      
      

      Here's the full maven -X log.
      http://cryptb.in/Vz9#f956618b3adf70be3133d996ece36db9

      In case you need more information, just let me know

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                agudian Andreas Gudian
                Reporter:
                fgaule Federico Gaule
              • Votes:
                13 Vote for this issue
                Watchers:
                20 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: