maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Parry (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MCOMPILER-307) Improve error message when compiler executable path invalid
Date Mon, 04 Sep 2017 23:53:00 GMT

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

Bryan Parry updated MCOMPILER-307:
----------------------------------
    Description: 
When the compiler executable path and fork properties are set, and also the compiler executable
file does not exist, a CompilationFailureException is thrown with a message: "Compilation
failure". The plugin should be able to check whether the compiler executable is a valid file,
and print a message if it does not exist (e.g. {{"Path to compiler executable " + path + "
is invalid. File not found."}})

Here is an example of the maven compiler properties that can cause the error to occur:
{code}
<properties>
  <maven.compiler.executable>/invalid/path/to/bin/javac</maven.compiler.executable>
  <maven.compiler.fork>true</maven.compiler.fork>
</properties>
{code}

This error can be tricky to debug when a specific maven profile is enabled only on a build
server by default.

  was:
When the compiler executable path and fork properties are set, and also the compiler executable
file does not exist, a CompilationFailureException is thrown with a message: "Compilation
failure". The plugin should be able to check whether the compiler executable is a valid file,
and print a message if it does not exist (e.g. {{"Path to compiler executable " + path + "
is invalid. File not found."}})

Here is an example of the maven compiler properties that can cause the error to occur:
{code}
<properties>
  <maven.compiler.executable>/invalid/path/to/bin/javac</maven.compiler.executable>
  <maven.compiler.fork>true</maven.compiler.fork>
</properties>
{code}


> Improve error message when compiler executable path invalid
> -----------------------------------------------------------
>
>                 Key: MCOMPILER-307
>                 URL: https://issues.apache.org/jira/browse/MCOMPILER-307
>             Project: Maven Compiler Plugin
>          Issue Type: Improvement
>    Affects Versions: 3.6.2
>            Reporter: Bryan Parry
>         Attachments: Maven compiler error.txt
>
>
> When the compiler executable path and fork properties are set, and also the compiler
executable file does not exist, a CompilationFailureException is thrown with a message: "Compilation
failure". The plugin should be able to check whether the compiler executable is a valid file,
and print a message if it does not exist (e.g. {{"Path to compiler executable " + path + "
is invalid. File not found."}})
> Here is an example of the maven compiler properties that can cause the error to occur:
> {code}
> <properties>
>   <maven.compiler.executable>/invalid/path/to/bin/javac</maven.compiler.executable>
>   <maven.compiler.fork>true</maven.compiler.fork>
> </properties>
> {code}
> This error can be tricky to debug when a specific maven profile is enabled only on a
build server by default.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message