[jira] Commented: (MCOMPILER-130) compilerArgument option doesn't work with maxerrs option, compilerArguments does

["Per Hedman (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MCOMPILER-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234409#action_234409 ] 

Per Hedman commented on MCOMPILER-130:
--------------------------------------

This problem also exists for Windows.

> compilerArgument option doesn't work with maxerrs option, compilerArguments does
> --------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-130
>                 URL: http://jira.codehaus.org/browse/MCOMPILER-130
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Bug
>         Environment: Mac OS X
>            Reporter: Mike Dikan
>
> I looked into using this configuration for maven:
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-compiler-plugin</artifactId>
>   <configuration>
>     <compilerArgument>-Xmaxerrs 1000</compilerArgument>
>   </configuration>
> </plugin>
> But no dice:
> Failure executing javac,  but could not parse the error:
> javac: invalid flag: -Xmaxerrs 1000
> Usage: javac <options> <source files>
> use -help for a list of possible options
> On the command line using javac, the maxerrs flag works as expected, and using the compilerArguments "Map" option works:
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-compiler-plugin</artifactId>
>   <configuration>
>     <fork>true</fork>
>     <compilerArguments>
>       <Xmaxerrs>10</Xmaxerrs>
>     </compilerArguments>
>   </configuration>
> </plugin>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira