[jira] [Commented] (BIGTOP-1852) neither ant nor mvn (probably others) are in the PATH after running ./gradlew toolchain

["Caleb Wharton (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064361#comment-15064361 ] 

Caleb Wharton commented on BIGTOP-1852:
---------------------------------------

My two cents: 

I am a new user attempting to build Hadoop/Spark RPMs on a fresh install of CentOS 7 with 1.8-openjdk and have already spent two days wrestling with this issue before stumbling on this ticket. After restarting after running "./gradlew toolchain" I find that my shell is now able to find mvn, but I am still getting a "mvn not found" when running "sudo ./gradlew hadoop-rpm" ("./gradlew. fails due to issues with DaemonClient"). I don't understand what a login shell would mean in this situation and am still trying to resolve this issue.

I understand that you cannot anticipate all the particularities of people's development environment, but I suggest you write your documentation from the perspective of a fresh install for some benchmark OS to minimize the pitfalls of those starting out.

> neither ant nor mvn (probably others) are in the PATH after running ./gradlew toolchain
> ---------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-1852
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1852
>             Project: Bigtop
>          Issue Type: Bug
>          Components: documentation, toolchain
>    Affects Versions: 1.0.0
>         Environment: centos 6.6
>            Reporter: André Kelpe
>            Priority: Minor
>
> I am getting started with bigtop and in order to learn the ins and outs I started with a blank Centos 6.6 machine and ran ./gradlew toolchain as instructed. After it ran to completion I tried building one of the rpm packages which failed because mvn is not in the path after ./gradlew toolchain completes. This should either be fixed or documented in some way. Running a login shell solves the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)