[
http://jira.codehaus.org/browse/MCOMPILER-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Hedman updated MCOMPILER-130:
---------------------------------
Attachment: patch_MCOMPILER-130.txt
A patch that informs the user if there is a white-space within the
<compilerArgument> and a explanation in the FAQ segment of site. Added a
parameter to turn the warning off.
The faq text may need checking.
> 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
> Attachments: patch_MCOMPILER-130.txt
>
>
> 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
