+1 It sounds like a very good thing to do. Leo
-----Original Message----- From: Jesse [mailto:purplecabb...@gmail.com] Sent: Monday, April 13, 2015 12:24 PM To: dev@cordova.apache.org Subject: Re: Proposal: Expose check_reqs at the CLI level Everyone's +1's count! It's the -1's that may be scrutinized @purplecabbage risingj.com On Mon, Apr 13, 2015 at 12:11 PM, Dmitry Blotsky <dblot...@microsoft.com> wrote: > +1 for me too, even though my +1 points don't matter :) > > I've actually run into this issue when writing documentation for setting > up slaves for medic. My short documentation is here: > https://github.com/apache/cordova-medic/blob/master/SLAVES.md, but it is > best for it to refer to the official Cordova docs instead. > > Should we make a JIRA task for better docs and automated platform > dependency detection? > > Kindly, > Dmitry > > -----Original Message----- > From: Shazron [mailto:shaz...@gmail.com] > Sent: Monday, April 13, 2015 11:56 AM > To: dev@cordova.apache.org > Subject: Re: Proposal: Expose check_reqs at the CLI level > > +1 > This will be great for users > > On Mon, Apr 13, 2015 at 11:53 AM, Parashuram N (MS OPEN TECH) < > panar...@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-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
