[MCOMPILER-260] Incorrect <compilerArgs> behavior when multiple number <arg>'s have the same value

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3
• Fix Version/s: 3.6.0
• Environment: JDK 1.8.0_45; Maven 3.3.1
• Assignee: Robert Scholte
• Reporter: Anthony Vanelverdinghe
• Created: 07/Jan/16 12:04
• Updated: 06/Oct/16 20:23
• Resolved: 06/Oct/16 20:00

Description

The following configuration:

<compilerArgs>
    <arg>-Xmaxwarns</arg>
    <arg>7</arg>
    <arg>-Xmaxerrs</arg>
    <arg>7</arg>
</compilerArgs>

always fails, because the last 7 is not passed to javac. However, changing any of the numbers so that they're not equal, makes it succeed. Another case where it may succeed, is when an additional argument is appended. For example the following succeeds:

<compilerArgs>
    <arg>-Xmaxwarns</arg>
    <arg>7</arg>
    <arg>-Xmaxerrs</arg>
    <arg>7</arg>
    <arg>-Werror</arg>
</compilerArgs>

However, this is not always the case. For example, the following fails:

<compilerArgs>
    <arg>-Xmaxwarns</arg>
    <arg>7</arg>
    <arg>-source</arg>
    <arg>7</arg>
    <arg>-Werror</arg>
</compilerArgs>

Also note that the numbers do not necessarily have to be adjacent, e.g. the following fails as well:

<compilerArgs>
    <arg>-Xmaxwarns</arg>
    <arg>7</arg>
    <arg>-source</arg>
    <arg>1.5</arg>
    <arg>-Xmaxerrs</arg>
    <arg>7</arg>
</compilerArgs>