You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Filip Maj <fi...@adobe.com> on 2012/12/18 00:20:38 UTC
Cordova CLI in Apache
We now have the cordova-cli repo set up. I have migrated my temporary
space on GitHub for it over to this repo. There is a component set up in
JIRA for it now (CLI).
Currently it only supports iOS, Android and BlackBerry 10. The CLI tools
run on OS X and Linux. I have outstanding tasks to add support for windows
(which, according to some users, is only a matter of appending ".bat" to
the shell commands, so shouldn't be far off), and explore the potential of
incorporating Win8, WP7 and WP8 support into it as well.
Another outstanding task is to allow the use of different versions of
cordova when creating projects using the tools.
I have to still run RAT on it and get the license headers and all that bs
in place :P
If you use it, feel free to file issues if you find something broken.
I do have a request for people involved in maintaining the platform
libraries. If there are changes being introduced into your platform
library that affects the "structure" of the library, it may also affect
the cli tools. If this is the case, can you ping me (or even better: get
involved in the cli tool dev!) so that I can update them? The CLI tools
edit the various metadata files (config.xml, for example), as well as copy
over the javascript files into appropriate spots. Some things that have
broken cordova-cli in the past between cordova versions are:
- moving around .plist or .xml config files, or renaming them
- moving around or renaming the cordova.js files
- renaming the repos
- changing the structure/contents of xml or config files
The above is very likely not an exhaustive list :)
Thanks all!
Re: Cordova CLI in Apache
Posted by Michal Mocny <mm...@chromium.org>.
Woot! Excited to see progress here.
For those of us who go looking for this, look here:
https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=summary
On Tue, Dec 18, 2012 at 4:53 PM, Brian LeRoux <b...@brian.io> wrote:
> YES---looking forward to removing plugins from platforms and making
> those opt in as a result. =)
>
> On Tue, Dec 18, 2012 at 12:51 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> > Great work Fil! Excited to see this move into Apache. Can't wait until
> CLI
> > becomes the default.
> >
> >
> > On Mon, Dec 17, 2012 at 6:20 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> We now have the cordova-cli repo set up. I have migrated my temporary
> >> space on GitHub for it over to this repo. There is a component set up in
> >> JIRA for it now (CLI).
> >>
> >> Currently it only supports iOS, Android and BlackBerry 10. The CLI tools
> >> run on OS X and Linux. I have outstanding tasks to add support for
> windows
> >> (which, according to some users, is only a matter of appending ".bat" to
> >> the shell commands, so shouldn't be far off), and explore the potential
> of
> >> incorporating Win8, WP7 and WP8 support into it as well.
> >>
> >> Another outstanding task is to allow the use of different versions of
> >> cordova when creating projects using the tools.
> >>
> >> I have to still run RAT on it and get the license headers and all that
> bs
> >> in place :P
> >>
> >> If you use it, feel free to file issues if you find something broken.
> >>
> >> I do have a request for people involved in maintaining the platform
> >> libraries. If there are changes being introduced into your platform
> >> library that affects the "structure" of the library, it may also affect
> >> the cli tools. If this is the case, can you ping me (or even better: get
> >> involved in the cli tool dev!) so that I can update them? The CLI tools
> >> edit the various metadata files (config.xml, for example), as well as
> copy
> >> over the javascript files into appropriate spots. Some things that have
> >> broken cordova-cli in the past between cordova versions are:
> >>
> >> - moving around .plist or .xml config files, or renaming them
> >> - moving around or renaming the cordova.js files
> >> - renaming the repos
> >> - changing the structure/contents of xml or config files
> >>
> >> The above is very likely not an exhaustive list :)
> >>
> >> Thanks all!
> >>
> >>
>
Re: Cordova CLI in Apache
Posted by Brian LeRoux <b...@brian.io>.
YES---looking forward to removing plugins from platforms and making
those opt in as a result. =)
On Tue, Dec 18, 2012 at 12:51 PM, Andrew Grieve <ag...@chromium.org> wrote:
> Great work Fil! Excited to see this move into Apache. Can't wait until CLI
> becomes the default.
>
>
> On Mon, Dec 17, 2012 at 6:20 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> We now have the cordova-cli repo set up. I have migrated my temporary
>> space on GitHub for it over to this repo. There is a component set up in
>> JIRA for it now (CLI).
>>
>> Currently it only supports iOS, Android and BlackBerry 10. The CLI tools
>> run on OS X and Linux. I have outstanding tasks to add support for windows
>> (which, according to some users, is only a matter of appending ".bat" to
>> the shell commands, so shouldn't be far off), and explore the potential of
>> incorporating Win8, WP7 and WP8 support into it as well.
>>
>> Another outstanding task is to allow the use of different versions of
>> cordova when creating projects using the tools.
>>
>> I have to still run RAT on it and get the license headers and all that bs
>> in place :P
>>
>> If you use it, feel free to file issues if you find something broken.
>>
>> I do have a request for people involved in maintaining the platform
>> libraries. If there are changes being introduced into your platform
>> library that affects the "structure" of the library, it may also affect
>> the cli tools. If this is the case, can you ping me (or even better: get
>> involved in the cli tool dev!) so that I can update them? The CLI tools
>> edit the various metadata files (config.xml, for example), as well as copy
>> over the javascript files into appropriate spots. Some things that have
>> broken cordova-cli in the past between cordova versions are:
>>
>> - moving around .plist or .xml config files, or renaming them
>> - moving around or renaming the cordova.js files
>> - renaming the repos
>> - changing the structure/contents of xml or config files
>>
>> The above is very likely not an exhaustive list :)
>>
>> Thanks all!
>>
>>
Re: Cordova CLI in Apache
Posted by Andrew Grieve <ag...@chromium.org>.
Great work Fil! Excited to see this move into Apache. Can't wait until CLI
becomes the default.
On Mon, Dec 17, 2012 at 6:20 PM, Filip Maj <fi...@adobe.com> wrote:
> We now have the cordova-cli repo set up. I have migrated my temporary
> space on GitHub for it over to this repo. There is a component set up in
> JIRA for it now (CLI).
>
> Currently it only supports iOS, Android and BlackBerry 10. The CLI tools
> run on OS X and Linux. I have outstanding tasks to add support for windows
> (which, according to some users, is only a matter of appending ".bat" to
> the shell commands, so shouldn't be far off), and explore the potential of
> incorporating Win8, WP7 and WP8 support into it as well.
>
> Another outstanding task is to allow the use of different versions of
> cordova when creating projects using the tools.
>
> I have to still run RAT on it and get the license headers and all that bs
> in place :P
>
> If you use it, feel free to file issues if you find something broken.
>
> I do have a request for people involved in maintaining the platform
> libraries. If there are changes being introduced into your platform
> library that affects the "structure" of the library, it may also affect
> the cli tools. If this is the case, can you ping me (or even better: get
> involved in the cli tool dev!) so that I can update them? The CLI tools
> edit the various metadata files (config.xml, for example), as well as copy
> over the javascript files into appropriate spots. Some things that have
> broken cordova-cli in the past between cordova versions are:
>
> - moving around .plist or .xml config files, or renaming them
> - moving around or renaming the cordova.js files
> - renaming the repos
> - changing the structure/contents of xml or config files
>
> The above is very likely not an exhaustive list :)
>
> Thanks all!
>
>
Re: Cordova CLI in Apache
Posted by Filip Maj <fi...@adobe.com>.
The tests can take a while - not uncommon for it to need 2-3 minutes to
run on a Macbook Air. Suggestions welcome :)
On 12/20/12 11:33 AM, "Shazron" <sh...@gmail.com> wrote:
>Thanks Fil, will do! I will run the cordova-cli tests occasionally as I do
>the platform tests as well.
>
>
>On Mon, Dec 17, 2012 at 3:20 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> We now have the cordova-cli repo set up. I have migrated my temporary
>> space on GitHub for it over to this repo. There is a component set up in
>> JIRA for it now (CLI).
>>
>> Currently it only supports iOS, Android and BlackBerry 10. The CLI tools
>> run on OS X and Linux. I have outstanding tasks to add support for
>>windows
>> (which, according to some users, is only a matter of appending ".bat" to
>> the shell commands, so shouldn't be far off), and explore the potential
>>of
>> incorporating Win8, WP7 and WP8 support into it as well.
>>
>> Another outstanding task is to allow the use of different versions of
>> cordova when creating projects using the tools.
>>
>> I have to still run RAT on it and get the license headers and all that
>>bs
>> in place :P
>>
>> If you use it, feel free to file issues if you find something broken.
>>
>> I do have a request for people involved in maintaining the platform
>> libraries. If there are changes being introduced into your platform
>> library that affects the "structure" of the library, it may also affect
>> the cli tools. If this is the case, can you ping me (or even better: get
>> involved in the cli tool dev!) so that I can update them? The CLI tools
>> edit the various metadata files (config.xml, for example), as well as
>>copy
>> over the javascript files into appropriate spots. Some things that have
>> broken cordova-cli in the past between cordova versions are:
>>
>> - moving around .plist or .xml config files, or renaming them
>> - moving around or renaming the cordova.js files
>> - renaming the repos
>> - changing the structure/contents of xml or config files
>>
>> The above is very likely not an exhaustive list :)
>>
>> Thanks all!
>>
>>
Re: Cordova CLI in Apache
Posted by Shazron <sh...@gmail.com>.
Thanks Fil, will do! I will run the cordova-cli tests occasionally as I do
the platform tests as well.
On Mon, Dec 17, 2012 at 3:20 PM, Filip Maj <fi...@adobe.com> wrote:
> We now have the cordova-cli repo set up. I have migrated my temporary
> space on GitHub for it over to this repo. There is a component set up in
> JIRA for it now (CLI).
>
> Currently it only supports iOS, Android and BlackBerry 10. The CLI tools
> run on OS X and Linux. I have outstanding tasks to add support for windows
> (which, according to some users, is only a matter of appending ".bat" to
> the shell commands, so shouldn't be far off), and explore the potential of
> incorporating Win8, WP7 and WP8 support into it as well.
>
> Another outstanding task is to allow the use of different versions of
> cordova when creating projects using the tools.
>
> I have to still run RAT on it and get the license headers and all that bs
> in place :P
>
> If you use it, feel free to file issues if you find something broken.
>
> I do have a request for people involved in maintaining the platform
> libraries. If there are changes being introduced into your platform
> library that affects the "structure" of the library, it may also affect
> the cli tools. If this is the case, can you ping me (or even better: get
> involved in the cli tool dev!) so that I can update them? The CLI tools
> edit the various metadata files (config.xml, for example), as well as copy
> over the javascript files into appropriate spots. Some things that have
> broken cordova-cli in the past between cordova versions are:
>
> - moving around .plist or .xml config files, or renaming them
> - moving around or renaming the cordova.js files
> - renaming the repos
> - changing the structure/contents of xml or config files
>
> The above is very likely not an exhaustive list :)
>
> Thanks all!
>
>