Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of purplecabbage@gmail.com
 designates 209.85.214.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAE6O_-b97e=N2EwNjGmFGTX=GraE8C4j5QFy6_2XvJkOVP07+g@mail.gmail.com>
References: 
 <DM2PR03MB3669A7C67442743EA620A80D6E70@DM2PR03MB366.namprd03.prod.outlook.com>
	<CAE6O_-b97e=N2EwNjGmFGTX=GraE8C4j5QFy6_2XvJkOVP07+g@mail.gmail.com>
Date: Mon, 13 Apr 2015 12:07:23 -0700
Message-ID: 
 <CAKP6k2u+oJWnVK_OoKOwSiPWw-pPnefKv6ccY9mBE6XEDOkfvA@mail.gmail.com>
Subject: Re: Proposal: Expose check_reqs at the CLI level
From: Jesse <purplecabbage@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=001a113cd964f3cc0405139fd22d

--001a113cd964f3cc0405139fd22d
Content-Type: text/plain; charset=UTF-8

+1
Sounds great!

@purplecabbage
risingj.com

On Mon, Apr 13, 2015 at 11:56 AM, Shazron <shazron@gmail.com> wrote:

> +1
> This will be great for users
>
> On Mon, Apr 13, 2015 at 11:53 AM, Parashuram N (MS OPEN TECH)
> <panarasi@microsoft.com> wrote:
> > Hi,
> >
> > One of the main problems a lot of developers seem to have is the issue
> to setting up their machines for building various platforms. This came out
> from the Stack overflow survey, and the number of questions on stack
> overflow, twitter. Etc.
> >
> > I thought it would be helpful to have a check_reqs command exposed at
> the CLI level. This is similar to `brew doctor` or `appium doctor`. The
> idea is
> >
> >
> > 1.       Have a way for the user to see if they have all dependencies
> (like JAVA_HOME or ANDROID_HOME) set up? This happens at build time, but
> moving it out to a CLI level command where you can run cordova check_reqs
> (or something similar) would be useful to the users.
> >
> > 2.       Today, the build command shows one error at a time. The
> check_reqs could run all the checks, and show a summary of the issues so
> that the user can fix them all, instead of fixing one, running build,
> fixing again, etc.
> >
> > What does the community think of this idea ? Can we implement a
> prototype and see if this is useful to our developers ?
> > Note that this does not change or break existing functionality - it just
> exposes the already existing check_reqs in the CLI. Build will continue to
> call check_reqs.
> >
> > Please vote on this proposal, or raise any concerns you may have.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>

--001a113cd964f3cc0405139fd22d--