maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MCOMPILER-220) Fix o.a.m.p.c.CompilerMojoTestCase.testCompilerFork(), which fails when javac is not on the PATH
Date Thu, 02 Jan 2014 13:08:45 GMT

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

Robert Scholte closed MCOMPILER-220.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2
         Assignee: Robert Scholte

Fixed in [r1554798|http://svn.apache.org/r1554798]
                
> Fix o.a.m.p.c.CompilerMojoTestCase.testCompilerFork(), which fails when javac is not
on the PATH
> ------------------------------------------------------------------------------------------------
>
>                 Key: MCOMPILER-220
>                 URL: https://jira.codehaus.org/browse/MCOMPILER-220
>             Project: Maven Compiler Plugin
>          Issue Type: Task
>    Affects Versions: 3.1
>            Reporter: Robert Scholte
>            Assignee: Robert Scholte
>            Priority: Minor
>             Fix For: 3.2
>
>
> This test assumes that {{javac}} is available on the path. Most systems have {{JAVA_HOME}}/bin
added to their path, but that's not a requirement for Maven, neither should it be for this
unittest.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message