You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:23 UTC

[jira] [Issue Comment Deleted] (MESOS-1743) mesos build looks for MAVEN_HOME

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

Gavin updated MESOS-1743:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> mesos build looks for MAVEN_HOME
> --------------------------------
>
>                 Key: MESOS-1743
>                 URL: https://issues.apache.org/jira/browse/MESOS-1743
>             Project: Mesos
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.20.0
>            Reporter: Henning Schmiedehausen
>            Priority: Major
>              Labels: newbie
>
> Mesos contains in configure.ac
> AC_ARG_VAR([MAVEN_HOME], [looks for mvn at MAVEN_HOME/bin/mvn])
> MAVEN_HOME was only used for maven 1, the current version (mvn 2 and 3) do not use this environment variable. If it is set for a maven 1 install, mesos does not build (it assumes that the mvn binary is available from this path, which it generally is not).
> The Mesos build should just ensure that mvn is present on the current path or expose an option from configure to set the path to the binary manually.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)