> > To be absolutely clear, the above is NOT the motivation for changing this > stuff around. Cordova-cli needs consistency across platforms. This is the > motivation.
Yep, as long as we can guarantee that each script follows a predictable input and output, I don't care how we implement it. If you guys really want a single entry-point with flags, then go nuts, but we will need to clearly define what happens when: - no flag is provided e.g. `build` - multiple flags are provided e.g. `build --release --debug` --- +1 to adding a script that validates a platform's SDK requirements. This script should not need to modify project files to assert the SDK requirements. I mention this because the current `cordova-cli` Android `check_requirements` must successfully update the Android project target before returning true. However, consider the scenario where you validate the SDK before adding the platform - in this case, the Android `check_requirements` will always fail. Michael On Mon, Mar 25, 2013 at 11:14 AM, Filip Maj <f...@adobe.com> wrote: > > >Hopefully, next time we will change/update these things it will be for a > >real reason (such as SDK tools updates etc...) and not because we think > >that there might be a better implementation in C#. > > To be absolutely clear, the above is NOT the motivation for changing this > stuff around. Cordova-cli needs consistency across platforms. This is the > motivation. > >
