maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Hagelberg (JIRA)" <j...@codehaus.org>
Subject [jira] (MCOMPILER-225) javac.bat and args file added to archive when fork and -X used
Date Wed, 02 Apr 2014 15:06:59 GMT

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

Jeffrey Hagelberg updated MCOMPILER-225:
----------------------------------------

    Description: 
When you compile a java project with -X flag 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.
 This can be reproduced in any maven java project.  The issue also only occurs when the "-X"
maven option is used to enable debug output.

  was:
When you compile a java project with -X flag 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.
 This can be reproduced in any maven java project.


> javac.bat and args file added to archive when fork and -X used
> --------------------------------------------------------------
>
>                 Key: MCOMPILER-225
>                 URL: https://jira.codehaus.org/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 flag 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.  This can be reproduced in any maven java project.  The issue also only occurs when
the "-X" maven option is used to enable debug output.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message