[jira] [Resolved] (MCOMPILER-225) javac.bat and args file added to archive when fork and -X used

["Olivier Lamy (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MCOMPILER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Olivier Lamy resolved MCOMPILER-225.
------------------------------------
    Resolution: Fixed

> 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
>            Assignee: Olivier Lamy
>            Priority: Minor
>             Fix For: 3.10.0
>
>
> 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:
> {code:xml}
>  <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>
> {code}
> 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
(v8.20.1#820001)