You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Isabel Jimenez (JIRA)" <ji...@apache.org> on 2014/06/18 01:09:04 UTC
[jira] [Commented] (MESOS-1290) Unable to find mvn on your path.
[ https://issues.apache.org/jira/browse/MESOS-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034570#comment-14034570 ]
Isabel Jimenez commented on MESOS-1290:
---------------------------------------
commit 2aeebd550d446d1a9ddfa2961cbaa0d4cc00c8af
Author: Isabel Jimenez <co...@isabeljimenez.com>
Date: Mon Jun 16 08:18:20 2014 -0700
Verbose Maven configure error.
Review: https://reviews.apache.org/r/21950
> Unable to find mvn on your path.
> ---------------------------------
>
> Key: MESOS-1290
> URL: https://issues.apache.org/jira/browse/MESOS-1290
> Project: Mesos
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.18.1
> Environment: Fedora20
> Reporter: Till Toenshoff
> Assignee: Isabel Jimenez
> Priority: Minor
> Labels: build, configure, maven, mvn
>
> While running configure:
> {{../configure CXX=clang++ CC=clang}}
> the following is displayed:
> {noformat}
> [...]
> checking whether -pthread is sufficient with -shared... yes
> checking for backtrace in -lunwind... no
> checking whether or not we can build with JNI... yes
> checking for mvn... no
> configure: error: Unable to find mvn on your path.
> {noformat}
> While I do know that the culprit is a missing Maven installation, a quick google on that exact error message only reveals some Mesos specific links. I think it would be great if that error message was a bit more verbose, similar to those we display in cases where dependencies like JNI-headers, Zookeeper or LevelDB are not found.
--
This message was sent by Atlassian JIRA
(v6.2#6252)