You know, writing out my thoughts has crystallized that I think we should
just be shipping the scripts as independent packages instead of bundling
directly inside platforms.
With that conclusion, I have to re-think what that implies ;)
On Mon, Feb 9, 2015 at 5:07 PM, Michal Mocny
Thoughts:
1. I'm happy to require cordova-android@FOO is required to be installed if
you want to prepare a project that was created with it. I think we should
leave a created-with file inside the platform artifacts to confirm this.
Possibly it makes in-place upgrades harder, but I think the
Been thinking about this as well, and one part I'm not 100% sure about is
having this logic at create-time vs prepare-time vs plugin-add time.
create-time - easy to see we just put it in cordova-FOO and allow deps
within package.json
prepare/plugin-add time though, should we relay on having the
I'm thinking we should move parsers (
https://github.com/apache/cordova-lib/tree/master/cordova-lib/src/cordova/metadata)
into platforms before each platforms 4.0.0 goes out.
These files would still live in the CLI so older platforms can work with
newer cli releases.
A future cli release can
+1
Sent from my BlackBerry 10 smartphone.
smime.p7s
Description: S/MIME cryptographic signature
