[ https://issues.apache.org/jira/browse/MCOMPILER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495025#comment-14495025 ]
Sergei Ivanov commented on MCOMPILER-225: ----------------------------------------- Still an issue with {{maven-compiler-plugin:3.3}}. It manifests itself in Maven Invoker ITs, which typically run in verbose mode (implying {{-X}} for {{javac}}). > javac.bat and args file added to archive when fork and -X used > -------------------------------------------------------------- > > Key: MCOMPILER-225 > URL: https://issues.apache.org/jira/browse/MCOMPILER-225 > Project: Maven Compiler Plugin > Issue Type: Bug > Affects Versions: 2.3.2, 3.1 > Environment: Windows 7 x64 > Reporter: Jeffrey Hagelberg > > When you compile a java project with -X maven option and <fork>true</fork> in > the maven-compiler-plugin configuration, the following extra files are > written to target\classes and bundled in the root directory of the jar: > javac.bat > org.codehaus.plexus.compiler.javac.JavacCompiler8515975925044691799arguments > The precise name of the arguments file varies from build to build. The exact > configuration we are using is: > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.6</source> > <target>1.6</target> > <fork>true</fork> > <showDeprecation>true</showDeprecation> > <showWarnings>true</showWarnings> > </configuration> > </plugin> > We originally saw this in version 2.3.2 of the maven-compiler-plugin. I've > verified that it also occurs in version 3.1. We are able to work around this > issue by setting fork to false. The issue also does not occur if -X is not > used. This can be reproduced in any maven java project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)