[GitHub] cordova-plugin-media pull request: Streaming & Background threadin...

[ghenry22]

Github user ghenry22 commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/62#issuecomment-176651587
  
@purplecabbage sorry to bug you but if you could have a look at my previous 
comment that would be great, I really want to get this merged as it has been 
hanging for a long time and is starting to be difficult to maintain my fork and 
keep everything up to date.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: geolocation getCurrentPosition and disabled location services

[julio cesar sanchez]

Carlos, the message he is talking about is a system message, so we don't
have to worry about how it works or the message it has to show.
It's displayed automatically when you call [self.locationManager
startUpdatingLocation]; and the geolocation services are turned off, but
the current implementation of the plugin doesn't call [self.locationManager
startUpdatingLocation]; if the permissions are turned off.

Bad thing is geolocation plugin follows the W3C API, and I don't see any
way of adding this option without "breaking" the API

2016-01-29 14:18 GMT+01:00 Carlos Santana :

> Thanks for opening the JIRA that says a lot about your interest to help.
> But my opinion the request is for a specific implementation related to
> UI/UX, then what would the dialog say and how to handle language etc...
>
> This is the reason in core Cordova we try to stay away from providing
> specific UI implementations
>
> Also there is no native iOS API to open settings app in the specific
> section of Location Services that I'm aware. There are some APIs to go the
> your app section but not the location services.
>
> I would consider the use case be concern of Dev space how to handle the
> UI/UX when our current API returns with permission denied
> On Fri, Jan 29, 2016 at 7:07 AM Zarko Hristovski  wrote:
>
> > Thanks.
> >
> > Created CB-10478 (getCurrentPosition should trigger system dialog for
> > enabling location services):
> > https://issues.apache.org/jira/browse/CB-10478
> >
> > It's a feature request, so fingers crossed.
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
> >
>

geolocation getCurrentPosition and disabled location services

[Zarko Hristovski]

Hi folks,

I wonder if anyone knows of a solution to the following case regarding 
cordova-plugin-geolocation.


The use case is when an app/user needs to access geoposition while 
device's location services are disabled. Let's say for the first time / 
attempt.
While I've been able to find a way to send the user directly to the 
system setting on Android (via cordova-diagnostic-plugin's 
switchToLocationSettings),
it seems to be no obvious way to achieve the same on iOS with the 
plugin(s) at present.


I'll point you to two existing threads that explain in more detail so 
that I don't repeat myself here:


- 
https://forum.ionicframework.com/t/ios-plugin-for-sending-user-to-settings-privacy-location-services


- https://github.com/dpa99c/cordova-diagnostic-plugin/issues/31


Thanks,
Zarko


-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: don't copy resource-files at plugin ...

[sgrebnov]

Github user sgrebnov commented on the pull request:

https://github.com/apache/cordova-windows/pull/139#issuecomment-176733241
  
I've tried this approach and it seems to work very well. The only two 
things I've noticed are:
1. Generated `Include` is absolute, this could be a problem for remote 
build tools and when you move the app or send someone else. But I think this 
could be easily fixed.
```

x64/foo.dll
Always

```
2. Includes to files which are outside the VS project are showed like 
linked folder is missing so this may confuse people

![image](https://cloud.githubusercontent.com/assets/981580/12675912/d74da02a-c69e-11e5-871b-844b37729d8a.png)

But in general this works well and should simplify working with 
arch-specific native dependencies a lot. File is correctly placed in generated 
package so there should no be any runtime issues


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [DISCUSS] Improving core plugins automated test coverage

[Carlos Santana]

Thanks for the effort into looking into it.
For now continue as plan, maybe in the future a portion of the tests can be
ran on Soucelabs if it make sense to complement on what we have with our
devices and emulators.
On Fri, Jan 29, 2016 at 3:20 AM Alexander Sorokin (Akvelon) <
v-als...@microsoft.com> wrote:

> It looks like the Saucelabs infrastructure won't suit our needs. A lot of
> Appium tests for Android platform now need to connect to the emulator
> directly via adb or telnet to send mock commands.
>
> For example, to mock charger in the battery-status tests, we execute "adb
> shell dumpsys battery set ac 0".
>
> It looks like saucelabs won't let us do that, so we're bound to our own
> devices and emulators.
>
> -Original Message-
> From: Alexander Sorokin (Akvelon) [mailto:v-als...@microsoft.com]
> Sent: Friday, January 22, 2016 12:11 PM
> To: dev@cordova.apache.org
> Subject: RE: [DISCUSS] Improving core plugins automated test coverage
>
> Thanks for suggesting saucelabs! I'll take a look at it.
>
> -Original Message-
> From: Carlos Santana [mailto:csantan...@gmail.com]
> Sent: Thursday, January 21, 2016 4:25 AM
> To: dev@cordova.apache.org
> Subject: Re: [DISCUSS] Improving core plugins automated test coverage
>
> Wow this is great! not just for our cordova code, but app developers that
> want to learn how to use appium to test their own plugins and app code
>
> Is this something we can run on saucelabs?, I think is free for open
> source projects.
>
>
> On Wed, Jan 20, 2016 at 8:16 PM Steven Gill 
> wrote:
>
> > Sweet! Thanks for doing this Alexander! Always thought it would be a
> > great idea to write some our tests with appium
> >
> > On Wed, Jan 20, 2016 at 5:07 PM, Joe Bowser  wrote:
> >
> > > So, Appium works now and I can close the issue complaining that
> > > Appium doesn't work?
> > >
> > > On Wed, Jan 20, 2016, 9:12 AM Alexander Sorokin (Akvelon) <
> > > v-als...@microsoft.com> wrote:
> > >
> > > > Hi guys.
> > > >
> > > > Lately I've been working on improving automated test coverage of
> > > > core plugins. Work is still in progress but there are some results
> > > > that I
> > want
> > > > to share.
> > > >
> > > > The idea is to use Appium framework to automate core plugins
> > > > manual
> > tests
> > > > in mobilespec app. I've implemented a new command for Medic. It
> > > > starts
> > an
> > > > Appium server instance, looks for the tests, then runs the
> > > > mobilespec
> > app
> > > > from the specified folder and runs the tests.
> > > >
> > > > Appium supports only iOS and Android platforms so there are tests
> > > > only
> > > for
> > > > these two, but we can extend the coverage of other platforms using
> > > > different ui testing frameworks.
> > > >
> > > > The tests themselves are written for jasmine-node and are using "wd"
> > > > module to connect to Appium server. They are currently located in
> > plugin
> > > > repos. Here's some links:
> > > >
> > > > Test runner (medic):
> > > > https://github.com/apache/cordova-medic/pull/70
> > > >
> > > > Battery Status tests:
> > > > https://github.com/apache/cordova-plugin-battery-status/pull/29
> > > >
> > > > Camera tests:
> > > > https://github.com/apache/cordova-plugin-camera/pull/156
> > > >
> > > > Contacts tests:
> > > > https://github.com/apache/cordova-plugin-contacts/pull/101
> > > >
> > > > Device Motion tests:
> > > > https://github.com/apache/cordova-plugin-device-motion/pull/39
> > > >
> > > > Tests can run on both real devices and emulators/simulators.
> > > > While developing the tests, I've been using Android emulator and
> > > > device with API level 19 (Android 4.4, KitKat) and iOS device
> > > > (iPad 2) with
> > iOS
> > > > 7.1 so the tests can fail on other devices/emulators. I'm going to
> > > > add
> > > the
> > > > support for other versions/devices as well as implement more
> > > > Appium
> > tests
> > > > for other plugins in the nearest future.
> > > >
> > > > To run the tests:
> > > > 1. Clone cordova-medic repo
> > > > 2. Clone tested plugins repos (appium tests are there, in
> > > > appium-tests
> > > > folder)
> > > > 3. Create mobile spec app with tested plugins:
> > > >node
> > > > cordova-mobile-spec/createmobilespec/createmobilespec.js
> > > > mobspec-android --android --plugins "cordova-plugin-battery-status
> > > > cordova-plugin-camera cordova-plugin-contacts
> > > cordova-plugin-device-motion"
> > > > 4. Build the mobilespec app:
> > > >cd mobspec-android && cordova build 5. Start the
> > > > emulator/connect the device 6. Run the tests using command:
> > > > node cordova-medic/medic/medic.js appium --app [mobilespec folder]
> > > > --platform [platform] --device-name [device/emulator name]
> > > > --platform-version [platform version] --plugins [list of plugins
> > > > to
> > test
> > > > separated by space] [--device (only if running on a real device)]
> > --udid
> > > > [iOS real devices only, device UDID] 

[GitHub] cordova-plugin-media pull request: CB-10476 - fix problem where ca...

[jclalala]

GitHub user jclalala opened a pull request:

https://github.com/apache/cordova-plugin-media/pull/78

CB-10476 - fix problem where callbacks were not invoked on android du…

seems like the faulty code was added back in this commit:


https://github.com/apache/cordova-plugin-media/commit/c4547c94c5850c619b0936551ec1180f4465a95b#diff-ea1d1dcd03fa62ee9f2774edbf524977

line 121.

problem happens when messageChannel is reset with callbackContext every 
call... removing this will fix the problem.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jclalala/cordova-plugin-media master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-media/pull/78.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #78


commit 8801f3943c557a82747781696f1e20978b8184e0
Author: Jeffrey Chang 
Date:   2016-01-29T13:13:59Z

CB-10476 - fix problem where callbacks were not invoked on android due to 
messageChannel being overridden by callbackContext in every execut() call




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-contacts pull request: Label for custum type phone ...

[javray]

GitHub user javray opened a pull request:

https://github.com/apache/cordova-plugin-contacts/pull/102

Label for custum type phone numbers

It's useful when user contacts have several number with custom labels 
defined by user.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/javray/cordova-plugin-contacts master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-contacts/pull/102.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #102


commit e0acfb8b8dd36cf257f13b8df819121ab8775046
Author: Fco. Javier Martín Carrasco 
Date:   2016-01-29T11:21:54Z

Label for custum type phone numbers




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: don't copy resource-files at plugin ...

[sgrebnov]

Github user sgrebnov commented on the pull request:

https://github.com/apache/cordova-windows/pull/139#issuecomment-176740857
  
Here is my +1, but it will be great if someone else can take a look on this 
change as well.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: geolocation getCurrentPosition and disabled location services

[Carlos Santana]

Thanks for opening the JIRA that says a lot about your interest to help.
But my opinion the request is for a specific implementation related to
UI/UX, then what would the dialog say and how to handle language etc...

This is the reason in core Cordova we try to stay away from providing
specific UI implementations

Also there is no native iOS API to open settings app in the specific
section of Location Services that I'm aware. There are some APIs to go the
your app section but not the location services.

I would consider the use case be concern of Dev space how to handle the
UI/UX when our current API returns with permission denied
On Fri, Jan 29, 2016 at 7:07 AM Zarko Hristovski  wrote:

> Thanks.
>
> Created CB-10478 (getCurrentPosition should trigger system dialog for
> enabling location services):
> https://issues.apache.org/jira/browse/CB-10478
>
> It's a feature request, so fingers crossed.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: geolocation getCurrentPosition and disabled location services

[julio cesar sanchez]

Hi.

The dialog you talk about is shown by the system when you try use the
CLLocationManager startUpdatingLocation and the permissions are off.
The way the geolocation plugin is built, it checks the permissions first,
and if they are off it doesn't call the CLLocationManager
startUpdatingLocation.
You can send a feature request on http://issues.cordova.io/ asking for a
new feature on the geolocation plugin to force the use of the
CLLocationManager startUpdatingLocation even if the permissions are off,
that should show the message you want (didn't try).





2016-01-29 12:02 GMT+01:00 Zarko Hristovski :

> Hi folks,
>
> I wonder if anyone knows of a solution to the following case regarding
> cordova-plugin-geolocation.
>
> The use case is when an app/user needs to access geoposition while
> device's location services are disabled. Let's say for the first time /
> attempt.
> While I've been able to find a way to send the user directly to the system
> setting on Android (via cordova-diagnostic-plugin's
> switchToLocationSettings),
> it seems to be no obvious way to achieve the same on iOS with the
> plugin(s) at present.
>
> I'll point you to two existing threads that explain in more detail so that
> I don't repeat myself here:
>
> -
> https://forum.ionicframework.com/t/ios-plugin-for-sending-user-to-settings-privacy-location-services
>
> - https://github.com/dpa99c/cordova-diagnostic-plugin/issues/31
>
>
> Thanks,
> Zarko
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>
>

Re: geolocation getCurrentPosition and disabled location services

[Zarko Hristovski]

Thanks.

Created CB-10478 (getCurrentPosition should trigger system dialog for 
enabling location services):

https://issues.apache.org/jira/browse/CB-10478

It's a feature request, so fingers crossed.

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-media pull request: Streaming & Background threadin...

[imsingh]

Github user imsingh commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/62#issuecomment-176632291
  
@ghenry22 MPESG Radio is just name of Cordova App and m3u file has a single 
URL entry. I Tried using the URL Directly again it is not working. However the 
plugin at https://github.com/keosuofficial/cordova-audio-stream-plugin works 
fine, but it has not implemented callbacks so I can't use it either. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-windows pull request: CB-10446 Windows 10 Cordova Applicat...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-windows/pull/144


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-media pull request: Streaming & Background threadin...

[ghenry22]

Github user ghenry22 commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/62#issuecomment-176651285
  
@imsingh where are you loading the m3u file from?  If you are opening the 
m3u file from the local file system it will try to play it like a local file.  
If you open it from a http url then it will try to stream it.  This is just the 
logic in the media plugin, it looks at the source prefix to determine if it 
should stream or play locally.

If you haven't already done so I have a fork of the plugin here that you 
can install using the command below, this fork has the updated ios streaming 
code from this pull request build in.  If you install from here and you're m3u 
file is being loaded from a url that starts with http or https you should see a 
message in the native console saying "playing stream with avplayer" instead of 
the normal message you see which is tied to "avaudioplayer".  avaudioplayer is 
the original implementation that does not support streaming, avplayer is the 
framework implemented in this PR to add proper streaming support.

cordova plugin add 
https://github.com/ghenry22/cordova-plugin-media.git#integrated_fixes

that's the best that I can think to recommend, hope it helps a bit!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: [DISCUSS] Improving core plugins automated test coverage

[Alexander Sorokin (Akvelon)]

It looks like the Saucelabs infrastructure won't suit our needs. A lot of 
Appium tests for Android platform now need to connect to the emulator directly 
via adb or telnet to send mock commands.

For example, to mock charger in the battery-status tests, we execute "adb shell 
dumpsys battery set ac 0".

It looks like saucelabs won't let us do that, so we're bound to our own devices 
and emulators.

-Original Message-
From: Alexander Sorokin (Akvelon) [mailto:v-als...@microsoft.com] 
Sent: Friday, January 22, 2016 12:11 PM
To: dev@cordova.apache.org
Subject: RE: [DISCUSS] Improving core plugins automated test coverage

Thanks for suggesting saucelabs! I'll take a look at it.

-Original Message-
From: Carlos Santana [mailto:csantan...@gmail.com]
Sent: Thursday, January 21, 2016 4:25 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Improving core plugins automated test coverage

Wow this is great! not just for our cordova code, but app developers that want 
to learn how to use appium to test their own plugins and app code

Is this something we can run on saucelabs?, I think is free for open source 
projects.


On Wed, Jan 20, 2016 at 8:16 PM Steven Gill  wrote:

> Sweet! Thanks for doing this Alexander! Always thought it would be a 
> great idea to write some our tests with appium
>
> On Wed, Jan 20, 2016 at 5:07 PM, Joe Bowser  wrote:
>
> > So, Appium works now and I can close the issue complaining that 
> > Appium doesn't work?
> >
> > On Wed, Jan 20, 2016, 9:12 AM Alexander Sorokin (Akvelon) < 
> > v-als...@microsoft.com> wrote:
> >
> > > Hi guys.
> > >
> > > Lately I've been working on improving automated test coverage of 
> > > core plugins. Work is still in progress but there are some results 
> > > that I
> want
> > > to share.
> > >
> > > The idea is to use Appium framework to automate core plugins 
> > > manual
> tests
> > > in mobilespec app. I've implemented a new command for Medic. It 
> > > starts
> an
> > > Appium server instance, looks for the tests, then runs the 
> > > mobilespec
> app
> > > from the specified folder and runs the tests.
> > >
> > > Appium supports only iOS and Android platforms so there are tests 
> > > only
> > for
> > > these two, but we can extend the coverage of other platforms using 
> > > different ui testing frameworks.
> > >
> > > The tests themselves are written for jasmine-node and are using "wd"
> > > module to connect to Appium server. They are currently located in
> plugin
> > > repos. Here's some links:
> > >
> > > Test runner (medic):
> > > https://github.com/apache/cordova-medic/pull/70
> > >
> > > Battery Status tests:
> > > https://github.com/apache/cordova-plugin-battery-status/pull/29
> > >
> > > Camera tests:
> > > https://github.com/apache/cordova-plugin-camera/pull/156
> > >
> > > Contacts tests:
> > > https://github.com/apache/cordova-plugin-contacts/pull/101
> > >
> > > Device Motion tests:
> > > https://github.com/apache/cordova-plugin-device-motion/pull/39
> > >
> > > Tests can run on both real devices and emulators/simulators.
> > > While developing the tests, I've been using Android emulator and 
> > > device with API level 19 (Android 4.4, KitKat) and iOS device 
> > > (iPad 2) with
> iOS
> > > 7.1 so the tests can fail on other devices/emulators. I'm going to 
> > > add
> > the
> > > support for other versions/devices as well as implement more 
> > > Appium
> tests
> > > for other plugins in the nearest future.
> > >
> > > To run the tests:
> > > 1. Clone cordova-medic repo
> > > 2. Clone tested plugins repos (appium tests are there, in 
> > > appium-tests
> > > folder)
> > > 3. Create mobile spec app with tested plugins:
> > >node
> > > cordova-mobile-spec/createmobilespec/createmobilespec.js
> > > mobspec-android --android --plugins "cordova-plugin-battery-status 
> > > cordova-plugin-camera cordova-plugin-contacts
> > cordova-plugin-device-motion"
> > > 4. Build the mobilespec app:
> > >cd mobspec-android && cordova build 5. Start the 
> > > emulator/connect the device 6. Run the tests using command:
> > > node cordova-medic/medic/medic.js appium --app [mobilespec folder] 
> > > --platform [platform] --device-name [device/emulator name] 
> > > --platform-version [platform version] --plugins [list of plugins 
> > > to
> test
> > > separated by space] [--device (only if running on a real device)]
> --udid
> > > [iOS real devices only, device UDID] Every argument except 
> > > --platform is optional. On iOS, --udid is
> mandatory
> > > if running on real device.
> > >
> > > For example, android emulator:
> > > node cordova-medic/medic/medic.js appium --app mobspec-android
> --platform
> > > android --device-name appium --platform-version 19 --plugins 
> > > "cordova-plugin-device-motion"
> > >
> > > Android device:
> > > node cordova-medic/medic/medic.js appium --platform android --app 
> > > mobspec-android --plugins "cordova-plugin-contacts" --device
> > >
> > > 

Re: geolocation getCurrentPosition and disabled location services

[Carlos Santana]

I see so there is an API to force the OS dialog?

it would be another option in geolocationOptions, and would be only and iOS
Quirk type of thing.

I think we decided that moving forward that we should stay away of
implementing things for a single platform.




On Fri, Jan 29, 2016 at 10:14 AM julio cesar sanchez 
wrote:

> Carlos, the message he is talking about is a system message, so we don't
> have to worry about how it works or the message it has to show.
> It's displayed automatically when you call [self.locationManager
> startUpdatingLocation]; and the geolocation services are turned off, but
> the current implementation of the plugin doesn't call [self.locationManager
> startUpdatingLocation]; if the permissions are turned off.
>
> Bad thing is geolocation plugin follows the W3C API, and I don't see any
> way of adding this option without "breaking" the API
>
> 2016-01-29 14:18 GMT+01:00 Carlos Santana :
>
> > Thanks for opening the JIRA that says a lot about your interest to help.
> > But my opinion the request is for a specific implementation related to
> > UI/UX, then what would the dialog say and how to handle language etc...
> >
> > This is the reason in core Cordova we try to stay away from providing
> > specific UI implementations
> >
> > Also there is no native iOS API to open settings app in the specific
> > section of Location Services that I'm aware. There are some APIs to go
> the
> > your app section but not the location services.
> >
> > I would consider the use case be concern of Dev space how to handle the
> > UI/UX when our current API returns with permission denied
> > On Fri, Jan 29, 2016 at 7:07 AM Zarko Hristovski 
> wrote:
> >
> > > Thanks.
> > >
> > > Created CB-10478 (getCurrentPosition should trigger system dialog for
> > > enabling location services):
> > > https://issues.apache.org/jira/browse/CB-10478
> > >
> > > It's a feature request, so fingers crossed.
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > >
> > >
> >
>

Re: [REVIEW] CB-10472 NullPointerException: org.apache.cordova.PluginManager.onSaveInstanceState

[Joe Bowser]

Do we have unit tests for that? Can we have unit tests for that?

I know we can test this because it's on SaveInstanceState, and we just have
to make sure that we don't crash.  Actually, I'm not sure how we'd test
this.

Thoughts?

On Fri, Jan 29, 2016 at 9:34 AM, Carlos Santana 
wrote:

> Thanks for looking into it, I will merge and look into adding a unit test
> to check that certain methods can be called .
> I think can add JUnit tests to cover the small use case.
> Anyone know what were the unit tests added with 5.1.0 to test the new
> feature about saving and restoring state for plugins?
> It would be easier for me to piggy back and add my condition in there
>
> Richard in the JIRA Issue I added the setup to replicate with minimal
> effort.
> My use case didn't destroy the other activity it was just stopped.
> The use case was not about having a fully initialize Cordova Activity being
> destroy or stopped. That works
>
> On Thu, Jan 28, 2016 at 8:01 PM Richard Knoll 
> wrote:
>
> > I also think we should add tests for this. Carlos, do you have a setup
> for
> > this bug that you could share? It would be nice to have mobilespec tests
> > for save/restore in general, but that ends up being sort of tricky
> because
> > it requires enabling the "Don't Keep Activities" dev setting.
> >
> > Thanks,
> > Richard
> >
> > -Original Message-
> > From: Joe Bowser [mailto:bows...@gmail.com]
> > Sent: Thursday, January 28, 2016 1:39 PM
> > To: dev 
> > Subject: Re: [REVIEW] CB-10472 NullPointerException:
> > org.apache.cordova.PluginManager.onSaveInstanceState
> >
> > LGTM, but we should have a unit test to cover this behaviour somehow.
> >
> > On Thu, Jan 28, 2016 at 2:23 PM, Carlos Santana 
> > wrote:
> >
> > > It's being a while since I have done Android native dev, Can someone
> > > review the PR I sent
> > > https://github.com/apache/cordova-android/pull/255
> > >
> > > This hit us today at work, we have a complex launch of multiple
> > > Cordova Activities to deal with security aspects and crosswalk.
> > >
> > > It's only in cordova-android@5.1.0 due to the recent changes for
> > > saveState and restoreState for plugins
> > >
> > > It will be great to release a 5.1.1 next week with a couple of other
> > > bugs that are already seating in master.
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > For additional commands, e-mail: dev-h...@cordova.apache.org
> >
>

[GitHub] cordova-plugin-contacts pull request: back button not working fine...

[rakeshpalivela]

GitHub user rakeshpalivela opened a pull request:

https://github.com/apache/cordova-plugin-contacts/pull/103

back button not working fine...

when I clicking on back button of uinavigationcontroller, one black screen 
was appearing and it was not going back to app.
Did any one face this issue.?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/cordova-plugin-contacts dev

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-plugin-contacts/pull/103.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #103


commit fc2552522b6465301b1787dfe0d4730f83bddd73
Author: Ian Clelland 
Date:   2014-04-25T18:09:46Z

CB-6521: Remove development branch




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: [REVIEW] CB-10472 NullPointerException: org.apache.cordova.PluginManager.onSaveInstanceState

[Carlos Santana]

Thanks for looking into it, I will merge and look into adding a unit test
to check that certain methods can be called .
I think can add JUnit tests to cover the small use case.
Anyone know what were the unit tests added with 5.1.0 to test the new
feature about saving and restoring state for plugins?
It would be easier for me to piggy back and add my condition in there

Richard in the JIRA Issue I added the setup to replicate with minimal
effort.
My use case didn't destroy the other activity it was just stopped.
The use case was not about having a fully initialize Cordova Activity being
destroy or stopped. That works

On Thu, Jan 28, 2016 at 8:01 PM Richard Knoll  wrote:

> I also think we should add tests for this. Carlos, do you have a setup for
> this bug that you could share? It would be nice to have mobilespec tests
> for save/restore in general, but that ends up being sort of tricky because
> it requires enabling the "Don't Keep Activities" dev setting.
>
> Thanks,
> Richard
>
> -Original Message-
> From: Joe Bowser [mailto:bows...@gmail.com]
> Sent: Thursday, January 28, 2016 1:39 PM
> To: dev 
> Subject: Re: [REVIEW] CB-10472 NullPointerException:
> org.apache.cordova.PluginManager.onSaveInstanceState
>
> LGTM, but we should have a unit test to cover this behaviour somehow.
>
> On Thu, Jan 28, 2016 at 2:23 PM, Carlos Santana 
> wrote:
>
> > It's being a while since I have done Android native dev, Can someone
> > review the PR I sent
> > https://github.com/apache/cordova-android/pull/255
> >
> > This hit us today at work, we have a complex launch of multiple
> > Cordova Activities to deal with security aspects and crosswalk.
> >
> > It's only in cordova-android@5.1.0 due to the recent changes for
> > saveState and restoreState for plugins
> >
> > It will be great to release a 5.1.1 next week with a couple of other
> > bugs that are already seating in master.
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> For additional commands, e-mail: dev-h...@cordova.apache.org
>

Re: [DISCUSS] Improving core plugins automated test coverage

[Filip Maj]

O hey!

This is pretty sweet, Alexander. It's been so long since I've looked
at medic code, oh my. I feel so old all of a sudden :D

A few notes:

 - The way you use appium in here is mostly for navigating the UI -
that is awesome. Totally agree with this approach - automate all the
things so y'all can get closer and closer to a continuous integration
nirvana.
 - If you can get an appium run to work locally for you, moving to
Sauce Labs is a breeze - you just change the endpoint of the appium
server from wherever you are running it to ondemand.saucelabs.com:80.
Sauce provides "Open Sauce" for open source projects [1] - which
Cordova certainly falls under. That'll give y'all 5 concurrent VMs to
run tests on. Only iOS and Android are supported right now, but I
think it'd be a big win for Cordova to move to this. You don't have to
worry about managing the emulators/simulators, and parallelizing some
of these functional tests helps speed them up, too, giving you faster
feedback. I'm happy to help getting y'all set up here, too.
 - appium, at this time, doesn't expose a command directly to change
the battery level. However, we've filed an issue [2] and hopefully
that will bubble up to the main project in a release or two. So,
functional tests for the battery functionality are probably some of
the more out-of-reach-ones. That said, if you want to use Sauce, and
if we can write the test such that we isolate _just_ the battery
functionality, we can leverage pre-run executables [3] to basically
have an open shell prompt to the VM running the emulator - and `adb`
within it. So we can:
- take those `adb shell set battery blah` and stuff 'em into a
shell script we can host somewhere
- specify the URL to the script as a pre-run executable as part of
the appium test's desired capabilities
- kick off the appium test, which spins up a VM on Sauce's side
- the VM starts the emulator, then runs your pre-run exec scripts,
full of adb commands to tweak the emulator
- finally, the appium test automation commands interacting with
the emulator and the cordova app (presumably with mobile-spec in it?)
start executing, and you get test results back

I think we should start with the simplest APIs possible that are easy
to automate. Build out the framework to do that UI testing - and i
highly recommend we leverage the 5 free VMs from sauce to offload that
- and start integrating that into your day-to-day development work.
Once we've got the basics covered, I'm happy to help work through the
more complex testing cases involving disparate device APIs and see
what we can do on the appium (and/or Sauce) side to help make a
fully-automated testing suite a reality for the cordova project.

Let's do this!

-fil

[1] https://saucelabs.com/opensauce/
[2] https://github.com/appium/appium-adb/issues/133
[3] 
https://wiki.saucelabs.com/display/DOCS/Test+Configuration+Options#TestConfigurationOptions-Pre-runExecutables

On Fri, Jan 29, 2016 at 4:53 AM, Carlos Santana  wrote:
> Thanks for the effort into looking into it.
> For now continue as plan, maybe in the future a portion of the tests can be
> ran on Soucelabs if it make sense to complement on what we have with our
> devices and emulators.
> On Fri, Jan 29, 2016 at 3:20 AM Alexander Sorokin (Akvelon) <
> v-als...@microsoft.com> wrote:
>
>> It looks like the Saucelabs infrastructure won't suit our needs. A lot of
>> Appium tests for Android platform now need to connect to the emulator
>> directly via adb or telnet to send mock commands.
>>
>> For example, to mock charger in the battery-status tests, we execute "adb
>> shell dumpsys battery set ac 0".
>>
>> It looks like saucelabs won't let us do that, so we're bound to our own
>> devices and emulators.
>>
>> -Original Message-
>> From: Alexander Sorokin (Akvelon) [mailto:v-als...@microsoft.com]
>> Sent: Friday, January 22, 2016 12:11 PM
>> To: dev@cordova.apache.org
>> Subject: RE: [DISCUSS] Improving core plugins automated test coverage
>>
>> Thanks for suggesting saucelabs! I'll take a look at it.
>>
>> -Original Message-
>> From: Carlos Santana [mailto:csantan...@gmail.com]
>> Sent: Thursday, January 21, 2016 4:25 AM
>> To: dev@cordova.apache.org
>> Subject: Re: [DISCUSS] Improving core plugins automated test coverage
>>
>> Wow this is great! not just for our cordova code, but app developers that
>> want to learn how to use appium to test their own plugins and app code
>>
>> Is this something we can run on saucelabs?, I think is free for open
>> source projects.
>>
>>
>> On Wed, Jan 20, 2016 at 8:16 PM Steven Gill 
>> wrote:
>>
>> > Sweet! Thanks for doing this Alexander! Always thought it would be a
>> > great idea to write some our tests with appium
>> >
>> > On Wed, Jan 20, 2016 at 5:07 PM, Joe Bowser  wrote:
>> >
>> > > So, Appium works now and I can close the issue complaining that
>> > > Appium doesn't work?
>> > >
>> > > On Wed, Jan 

Re: geolocation getCurrentPosition and disabled location services

[julio cesar sanchez]

It's not really an API to force the dialog, it's just how the
CLLocationManager works if you try to use it when the location services are
not enabled (not the app permissions, the whole device location).

Anyway, I've been doing some tests, and it will only show the dialog twice,
it doesn't matter if you press "settings" or "cancel" on the dialog, the
third time you launch the app with the location services disabled, the
dialog won't appear again, so I don't think it's really helpful to add this
"feature".



2016-01-29 17:28 GMT+01:00 Carlos Santana :

> I see so there is an API to force the OS dialog?
>
> it would be another option in geolocationOptions, and would be only and iOS
> Quirk type of thing.
>
> I think we decided that moving forward that we should stay away of
> implementing things for a single platform.
>
>
>
>
> On Fri, Jan 29, 2016 at 10:14 AM julio cesar sanchez <
> jcesarmob...@gmail.com>
> wrote:
>
> > Carlos, the message he is talking about is a system message, so we don't
> > have to worry about how it works or the message it has to show.
> > It's displayed automatically when you call [self.locationManager
> > startUpdatingLocation]; and the geolocation services are turned off, but
> > the current implementation of the plugin doesn't call
> [self.locationManager
> > startUpdatingLocation]; if the permissions are turned off.
> >
> > Bad thing is geolocation plugin follows the W3C API, and I don't see any
> > way of adding this option without "breaking" the API
> >
> > 2016-01-29 14:18 GMT+01:00 Carlos Santana :
> >
> > > Thanks for opening the JIRA that says a lot about your interest to
> help.
> > > But my opinion the request is for a specific implementation related to
> > > UI/UX, then what would the dialog say and how to handle language etc...
> > >
> > > This is the reason in core Cordova we try to stay away from providing
> > > specific UI implementations
> > >
> > > Also there is no native iOS API to open settings app in the specific
> > > section of Location Services that I'm aware. There are some APIs to go
> > the
> > > your app section but not the location services.
> > >
> > > I would consider the use case be concern of Dev space how to handle the
> > > UI/UX when our current API returns with permission denied
> > > On Fri, Jan 29, 2016 at 7:07 AM Zarko Hristovski 
> > wrote:
> > >
> > > > Thanks.
> > > >
> > > > Created CB-10478 (getCurrentPosition should trigger system dialog for
> > > > enabling location services):
> > > > https://issues.apache.org/jira/browse/CB-10478
> > > >
> > > > It's a feature request, so fingers crossed.
> > > >
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
> > > > For additional commands, e-mail: dev-h...@cordova.apache.org
> > > >
> > > >
> > >
> >
>

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[dblotsky]

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-176998784
  
Two things:
1. I think the `medic log` command gets executed outside of the mobilespec 
app, so `./cordova` is not available there. This can be fixed though.
2. I think there is some code already within cordova-ios to do logging. So 
maybe this can be ported to there? The idea with medic-log was that eventually 
it would make its way into platforms and cordova-lib, and we could just call 
`cordova log android` or `cordova log ios`.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: help running android native tests

[Homer, Tony]

HtmlNotFoundTest fails for me too.

Is it a problem that the CordovaActivity displays an error dialog?
If it is, we could override displayError in MainTestActivity.

Maybe it's simpler than that - should the test be setting an errorUrl and then 
asserting that the errorUrl has been loaded?
If no errorUrl is set, testActivity.getCordovaWebView().getUrl() would still be 
equal to START_URL, wouldn't it?


In that case the current assertion should fail (and the test would fail).

On 1/29/16, 5:16 PM, "Joe Bowser"  wrote:

>Run it a few times to be sure it's failing.  This test shouldn't fail, but
>isn't as stable as it should be.
>
>On Fri, Jan 29, 2016, 2:41 PM Carlos Santana  wrote:
>
>> I working on getting my environment and all test pass except for one
>>
>> junit.framework.AssertionFailedError
>> at org.apache.cordova.test.HtmlNotFoundTest$1.run(HtmlNotFoundTest.java:36)
>> at
>>
>> android.test.InstrumentationTestCase$1.run(InstrumentationTestCase.java:138)
>> at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1871)
>> at android.os.Handler.handleCallback(Handler.java:739)
>> at android.os.Handler.dispatchMessage(Handler.java:95)
>> at android.os.Looper.loop(Looper.java:135)
>> at android.app.ActivityThread.main(ActivityThread.java:5254)
>> at
>>
>> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
>> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
>>
>> Are the tests wrong, or my setup missing something I followed the
>> instructions in the README.md in the test folder
>>
>>
>> [1]: https://github.com/apache/cordova-android/blob/master/test/README.md
>>

[GitHub] cordova-plugin-media pull request: Streaming & Background threadin...

[johncblandii]

Github user johncblandii commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/62#issuecomment-177030807
  
Sweet!!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Changing the XML reference formatting f...

[nikhilkh]

Github user nikhilkh commented on the pull request:

https://github.com/apache/cordova-docs/pull/473#issuecomment-177046094
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: help running android native tests

[Joe Bowser]

Run it a few times to be sure it's failing.  This test shouldn't fail, but
isn't as stable as it should be.

On Fri, Jan 29, 2016, 2:41 PM Carlos Santana  wrote:

> I working on getting my environment and all test pass except for one
>
> junit.framework.AssertionFailedError
> at org.apache.cordova.test.HtmlNotFoundTest$1.run(HtmlNotFoundTest.java:36)
> at
>
> android.test.InstrumentationTestCase$1.run(InstrumentationTestCase.java:138)
> at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1871)
> at android.os.Handler.handleCallback(Handler.java:739)
> at android.os.Handler.dispatchMessage(Handler.java:95)
> at android.os.Looper.loop(Looper.java:135)
> at android.app.ActivityThread.main(ActivityThread.java:5254)
> at
>
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
>
> Are the tests wrong, or my setup missing something I followed the
> instructions in the README.md in the test folder
>
>
> [1]: https://github.com/apache/cordova-android/blob/master/test/README.md
>

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[dblotsky]

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-177001181
  
@riknoll but if we pass a callback, it defaults to `true`.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-177008077
  
The script should still run synchronously even if those calls are async, 
but it's still a good idea to clean up that code. @dblotsky how can I determine 
what directory this script is being run from so I can reference the correct CLI?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Docs versioning scheme

[Carlos Santana]

+1

On Fri, Jan 29, 2016 at 8:47 PM Nikhil Khandelwal 
wrote:

> Looks we did a release for the docs with the tools release. Is it possible
> to name it 6.x instead of 6.0.0? All URLs to 6.0.0 will break if we do that
> but we should do that sooner rather than later to minimize impact.
>
> As discussed, micro-versioning of docs does not buy us much. I'll enhance
> our cordova-docs readme and editorial guide for docs with details on how we
> handle versioning.
>
> -Nikhil
>
> -Original Message-
> From: Jesse [mailto:purplecabb...@gmail.com]
> Sent: Thursday, January 21, 2016 2:50 PM
> To: dev@cordova.apache.org
> Subject: Re: Docs versioning scheme
>
> SGTM! +1
>
>
> @purplecabbage
>
> https://na01.safelinks.protection.outlook.com/?url=risingj.com=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=fiC5HqwZWlaOSZD4ipn97isk7hjFjVCht9IzgKZKnFA%3d
>
> On Thu, Jan 21, 2016 at 1:47 PM, Steven Gill 
> wrote:
>
> > +1
> >
> > On Thu, Jan 21, 2016 at 1:38 PM, Nikhil Khandelwal
> >  > >
> > wrote:
> >
> > > Should we version our docs on every major version (instead of minor
> > > version) of cordova CLI that comes out? Should the next version of
> > > the
> > docs
> > > be "6.x"? Honestly, not much changes every minor release and
> > > maintaining multiple copies has quite a few downsides w.r.t. SEO
> > > (referring to older versions of docs), slow docs builds, huge website
> duplication.
> > >
> > > Lot of our docs relate to platform updates and we need clear
> > > sections within them that specify the version of the platform for
> > > which the docs apply to. For example, Android 5.1 will introduce new
> > > lifetime concepts which will be part of Cordova 6.0 docs release.
> > > It's best for the text of the docs itself to have something along
> > > the lines of "This applies to cordova-android > 5.1"
> > >
> > > Similarly, significant future updates to CLI/Lib features can
> > > contain the same "This applies to cordova > 6.2".
> > >
> > > I think it will lead to a simpler model on our website and prevent
> > > future version explosion [1].
> > >
> > > Thanks,
> > > Nikhil
> > >
> > > [1]
> > > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fimgu
> > > r.com%2fvkeNvUL=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846
> > > b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=
> > > Yh%2b9h4MUN9VfUADA1unTmUExqioMs75xG1HjVYmDSBc%3d
> > >
> > >
> >
>

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338062
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
--- End diff --

Shouldn't this be an npm-style identifier (whatever that's called)?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10389: Turning config.xml documentat...

[rakatyal]

Github user rakatyal commented on the pull request:

https://github.com/apache/cordova-docs/pull/463#issuecomment-176992408
  
Yup. +1 to Dmitry's suggestion for using *Required* instead of *Required: 
true*. Also for platforms we plan of using customized highlight tag provoded by 
redcarpet. I will update my XML reference PR soon to reflect the changes.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[dblotsky]

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-17682
  
Also:
3. `shelljs.exec` needs `{silent: false, async: false}` to run 
synchronously, which it seems like is more fitting for a script.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-176999829
  
@dblotsky I agree that this should be in the platform and I know that there 
is a log script there already, but how do you invoke that script from the CLI? 
I don't think there is a `cordova log` command


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[dblotsky]

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-177000279
  
@riknoll I think for Android it gets called directly, so we can do the same 
for iOS for now maybe.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Changing the XML reference formatting f...

[rakatyal]

GitHub user rakatyal opened a pull request:

https://github.com/apache/cordova-docs/pull/473

Changing the XML reference formatting for required and platforms attr…

…ibutes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-docs raghav/required

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-docs/pull/473.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #473


commit b88b091ae78a898ea993a3071598058bab2e5df1
Author: Raghav Katyal 
Date:   2016-01-29T23:20:39Z

Changing the XML reference formatting for required and platforms attributes




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

RE: Docs versioning scheme

[Nikhil Khandelwal]

Looks we did a release for the docs with the tools release. Is it possible to 
name it 6.x instead of 6.0.0? All URLs to 6.0.0 will break if we do that but we 
should do that sooner rather than later to minimize impact.

As discussed, micro-versioning of docs does not buy us much. I'll enhance our 
cordova-docs readme and editorial guide for docs with details on how we handle 
versioning.

-Nikhil

-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com] 
Sent: Thursday, January 21, 2016 2:50 PM
To: dev@cordova.apache.org
Subject: Re: Docs versioning scheme

SGTM! +1


@purplecabbage
https://na01.safelinks.protection.outlook.com/?url=risingj.com=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=fiC5HqwZWlaOSZD4ipn97isk7hjFjVCht9IzgKZKnFA%3d

On Thu, Jan 21, 2016 at 1:47 PM, Steven Gill  wrote:

> +1
>
> On Thu, Jan 21, 2016 at 1:38 PM, Nikhil Khandelwal 
>  >
> wrote:
>
> > Should we version our docs on every major version (instead of minor
> > version) of cordova CLI that comes out? Should the next version of 
> > the
> docs
> > be "6.x"? Honestly, not much changes every minor release and 
> > maintaining multiple copies has quite a few downsides w.r.t. SEO 
> > (referring to older versions of docs), slow docs builds, huge website 
> > duplication.
> >
> > Lot of our docs relate to platform updates and we need clear 
> > sections within them that specify the version of the platform for 
> > which the docs apply to. For example, Android 5.1 will introduce new 
> > lifetime concepts which will be part of Cordova 6.0 docs release. 
> > It's best for the text of the docs itself to have something along 
> > the lines of "This applies to cordova-android > 5.1"
> >
> > Similarly, significant future updates to CLI/Lib features can 
> > contain the same "This applies to cordova > 6.2".
> >
> > I think it will lead to a simpler model on our website and prevent 
> > future version explosion [1].
> >
> > Thanks,
> > Nikhil
> >
> > [1] 
> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fimgu
> > r.com%2fvkeNvUL=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846
> > b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=
> > Yh%2b9h4MUN9VfUADA1unTmUExqioMs75xG1HjVYmDSBc%3d
> >
> >
>

[GitHub] cordova-docs pull request: Changing the XML reference formatting f...

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/473#discussion_r51330969
  
--- Diff: www/static/css-src/main.scss ---
@@ -173,6 +173,12 @@ code.prettyprint {
 border: none !important;
 }
 
+mark {
+background-color: lightblue;
+padding: 0.1px 0.2px 0.1px 0.2px;
+margin-right: 7px;
+}
+
--- End diff --

Right.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-media pull request: Streaming & Background threadin...

[purplecabbage]

Github user purplecabbage commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/62#issuecomment-177022108
  
Good to go. Thanks for sharing your work @ghenry22 !


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-plugin-media pull request: Streaming & Background threadin...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-media/pull/62


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[sarangan12]

Github user sarangan12 commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-177000821
  
@riknoll But if silent is set to true, can the results be seen in the logs 
by build sheriff?

From: Dmitry Blotsky [mailto:notificati...@github.com]
Sent: Friday, January 29, 2016 2:34 PM
To: apache/cordova-medic 
Cc: Sarangan Rajamanickam 
Subject: Re: [cordova-medic] CB-10474: Fix cordova-ios logging (#73)


Also:
3. shelljs.exec needs {silent: false, async: false} to run synchronously, 
which it seems like is more fitting for a script.

—
Reply to this email directly or view it on 
GitHub.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: help running android native tests

[Carlos Santana]

you are correct Homer and Joe, I figured it out the test needs some love

I added the 


On Fri, Jan 29, 2016 at 6:58 PM Joe Bowser  wrote:

> Yeah, it looks like the behaviour has changed since this was run.  I have a
> feeling that someone "refactored" and "cleaned up" the tests and the
> original intent of this test was lost.
>
> So, yeah, this should have an intent provided to it, and this test should
> fail.  The tests definitely need to be looked at again and their usefulness
> re-evaluated.
>
> On Fri, Jan 29, 2016 at 4:35 PM, Homer, Tony  wrote:
>
> > HtmlNotFoundTest fails for me too.
> >
> > Is it a problem that the CordovaActivity displays an error dialog?
> > If it is, we could override displayError in MainTestActivity.
> >
> > Maybe it's simpler than that - should the test be setting an errorUrl and
> > then asserting that the errorUrl has been loaded?
> > If no errorUrl is set, testActivity.getCordovaWebView().getUrl() would
> > still be equal to START_URL, wouldn't it?
> >
> >
> > In that case the current assertion should fail (and the test would fail).
> >
> > On 1/29/16, 5:16 PM, "Joe Bowser"  wrote:
> >
> > >Run it a few times to be sure it's failing.  This test shouldn't fail,
> but
> > >isn't as stable as it should be.
> > >
> > >On Fri, Jan 29, 2016, 2:41 PM Carlos Santana 
> > wrote:
> > >
> > >> I working on getting my environment and all test pass except for one
> > >>
> > >> junit.framework.AssertionFailedError
> > >> at
> > org.apache.cordova.test.HtmlNotFoundTest$1.run(HtmlNotFoundTest.java:36)
> > >> at
> > >>
> > >>
> >
> android.test.InstrumentationTestCase$1.run(InstrumentationTestCase.java:138)
> > >> at
> > android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1871)
> > >> at android.os.Handler.handleCallback(Handler.java:739)
> > >> at android.os.Handler.dispatchMessage(Handler.java:95)
> > >> at android.os.Looper.loop(Looper.java:135)
> > >> at android.app.ActivityThread.main(ActivityThread.java:5254)
> > >> at
> > >>
> > >>
> >
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
> > >> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
> > >>
> > >> Are the tests wrong, or my setup missing something I followed the
> > >> instructions in the README.md in the test folder
> > >>
> > >>
> > >> [1]:
> > https://github.com/apache/cordova-android/blob/master/test/README.md
> > >>
> >
>

[GitHub] cordova-docs pull request: CB-10332 Android Guide Improvements

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-docs/pull/471#issuecomment-177044144
  
@vladimir-kotikov Thanks for the heads up, I wasn't aware of that! After 
discussing this with @nikhilkh, I think I'm going to leave the instructions in 
but add that Cordova will try to do it automatically. Seems like that script 
might not always work.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-177000890
  
`silent` and `async` both default to false. See 
https://github.com/shelljs/shelljs#execcommand--options--callback


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: help running android native tests

[Joe Bowser]

Yeah, it looks like the behaviour has changed since this was run.  I have a
feeling that someone "refactored" and "cleaned up" the tests and the
original intent of this test was lost.

So, yeah, this should have an intent provided to it, and this test should
fail.  The tests definitely need to be looked at again and their usefulness
re-evaluated.

On Fri, Jan 29, 2016 at 4:35 PM, Homer, Tony  wrote:

> HtmlNotFoundTest fails for me too.
>
> Is it a problem that the CordovaActivity displays an error dialog?
> If it is, we could override displayError in MainTestActivity.
>
> Maybe it's simpler than that - should the test be setting an errorUrl and
> then asserting that the errorUrl has been loaded?
> If no errorUrl is set, testActivity.getCordovaWebView().getUrl() would
> still be equal to START_URL, wouldn't it?
>
>
> In that case the current assertion should fail (and the test would fail).
>
> On 1/29/16, 5:16 PM, "Joe Bowser"  wrote:
>
> >Run it a few times to be sure it's failing.  This test shouldn't fail, but
> >isn't as stable as it should be.
> >
> >On Fri, Jan 29, 2016, 2:41 PM Carlos Santana 
> wrote:
> >
> >> I working on getting my environment and all test pass except for one
> >>
> >> junit.framework.AssertionFailedError
> >> at
> org.apache.cordova.test.HtmlNotFoundTest$1.run(HtmlNotFoundTest.java:36)
> >> at
> >>
> >>
> android.test.InstrumentationTestCase$1.run(InstrumentationTestCase.java:138)
> >> at
> android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1871)
> >> at android.os.Handler.handleCallback(Handler.java:739)
> >> at android.os.Handler.dispatchMessage(Handler.java:95)
> >> at android.os.Looper.loop(Looper.java:135)
> >> at android.app.ActivityThread.main(ActivityThread.java:5254)
> >> at
> >>
> >>
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
> >> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
> >>
> >> Are the tests wrong, or my setup missing something I followed the
> >> instructions in the README.md in the test folder
> >>
> >>
> >> [1]:
> https://github.com/apache/cordova-android/blob/master/test/README.md
> >>
>

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[rakatyal]

GitHub user rakatyal opened a pull request:

https://github.com/apache/cordova-docs/pull/474

CB-10364: Making plugin.xml a reference



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-docs raghav/plugin

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-docs/pull/474.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #474


commit 37e6781bb0c8a2bdd730a915e4be6d1cb361346d
Author: Raghav Katyal 
Date:   2016-01-30T02:01:39Z

Making plugin.xml a reference




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Changing the XML reference formatting f...

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-docs/pull/473#issuecomment-177046166
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-177002066
  
Alright, I'll change it but logging was async before.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10389: Turning config.xml documentat...

[dblotsky]

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-docs/pull/463#issuecomment-176991484
  
@rakatyal, do you think it might be better to use _Required_ instead of 
_Required: true_?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[DISCUSS] Cordova windows 4.3.1 release

[Vladimir Kotikov (Akvelon)]

Hi all



We're planning to do a patch release of cordova-windows (proposed version is 
4.3.1) to address some regressions.

Here is the patches to be included in this release:



  * CB-10394 Do not cache manifest file while getting package name

  * CB-10446 Windows 10 Cordova Application restart instead of resume

  * CB-10440 Add CSS color names support for BackgroundColor on Windows

  * CB-10234 Better error message when Windows10 requires 'arch' flag

  * CB-10381 fix the bug when removing a plugin with a  tag



Does anyone have any reason to delay this release? Any other patches to land?



-

Best regards, Vladimir

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[dblotsky]

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-177015645
  
@riknoll one way is to pass the mobilespec dir. Another is to just assume 
that it gets called from the build root.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338528
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+
+  
+  ```
 
-
-
-
-
-
+  Engine elements may also specify fuzzy matches using '>', '>=' etc. to 
avoid repetition, and to reduce maintenance when the underlying 

[GitHub] cordova-medic pull request: CB-10405 - Connectivity issue to Cordo...

[nikhilkh]

Github user nikhilkh commented on a diff in the pull request:

https://github.com/apache/cordova-medic/pull/74#discussion_r51338537
  
--- Diff: lib/testcheck.js ---
@@ -21,22 +21,40 @@
 
 "use strict";
 
-module.exports = function (sha, dbHost) {
+module.exports = function (sha, dbHost, maxnumberoftries, delay) {
 
 var http = require("http"),
 url = require("url"),
 q = require("q");
 
+function tryConnect(options, d, pendingnumberoftries, operation, 
successCallBack){
+http.get(options, successCallBack)
+.on("error", function(e){
+if(pendingnumberoftries > 1){
+console.log("Connection attempt to " + operation + " 
failed. Will try after: " + delay + " milliseconds.");
--- End diff --

Should you be using the util log function here - as it has some nice 
functionality to put time etc?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Docs versioning scheme

[Steven Gill]

Yes. Sorry. I was just trying to get it out asap. I'll look into updating
it on Sunday/Monday.
On Jan 29, 2016 7:09 PM, "Carlos Santana"  wrote:

> +1
>
> On Fri, Jan 29, 2016 at 8:47 PM Nikhil Khandelwal 
> wrote:
>
> > Looks we did a release for the docs with the tools release. Is it
> possible
> > to name it 6.x instead of 6.0.0? All URLs to 6.0.0 will break if we do
> that
> > but we should do that sooner rather than later to minimize impact.
> >
> > As discussed, micro-versioning of docs does not buy us much. I'll enhance
> > our cordova-docs readme and editorial guide for docs with details on how
> we
> > handle versioning.
> >
> > -Nikhil
> >
> > -Original Message-
> > From: Jesse [mailto:purplecabb...@gmail.com]
> > Sent: Thursday, January 21, 2016 2:50 PM
> > To: dev@cordova.apache.org
> > Subject: Re: Docs versioning scheme
> >
> > SGTM! +1
> >
> >
> > @purplecabbage
> >
> >
> https://na01.safelinks.protection.outlook.com/?url=risingj.com=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=fiC5HqwZWlaOSZD4ipn97isk7hjFjVCht9IzgKZKnFA%3d
> >
> > On Thu, Jan 21, 2016 at 1:47 PM, Steven Gill 
> > wrote:
> >
> > > +1
> > >
> > > On Thu, Jan 21, 2016 at 1:38 PM, Nikhil Khandelwal
> > >  > > >
> > > wrote:
> > >
> > > > Should we version our docs on every major version (instead of minor
> > > > version) of cordova CLI that comes out? Should the next version of
> > > > the
> > > docs
> > > > be "6.x"? Honestly, not much changes every minor release and
> > > > maintaining multiple copies has quite a few downsides w.r.t. SEO
> > > > (referring to older versions of docs), slow docs builds, huge website
> > duplication.
> > > >
> > > > Lot of our docs relate to platform updates and we need clear
> > > > sections within them that specify the version of the platform for
> > > > which the docs apply to. For example, Android 5.1 will introduce new
> > > > lifetime concepts which will be part of Cordova 6.0 docs release.
> > > > It's best for the text of the docs itself to have something along
> > > > the lines of "This applies to cordova-android > 5.1"
> > > >
> > > > Similarly, significant future updates to CLI/Lib features can
> > > > contain the same "This applies to cordova > 6.2".
> > > >
> > > > I think it will lead to a simpler model on our website and prevent
> > > > future version explosion [1].
> > > >
> > > > Thanks,
> > > > Nikhil
> > > >
> > > > [1]
> > > > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fimgu
> > > > r.com%2fvkeNvUL=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846
> > > > b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=
> > > > Yh%2b9h4MUN9VfUADA1unTmUExqioMs75xG1HjVYmDSBc%3d
> > > >
> > > >
> > >
> >
>

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338764
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+
+  
+  ```
 
-
-
-
-
-
+  Engine elements may also specify fuzzy matches using '>', '>=' etc. to 
avoid repetition, and to reduce maintenance when the underlying 

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338252
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+
+  
+  ```
 
-
-
-
-
-
+  Engine elements may also specify fuzzy matches using '>', '>=' etc. to 
avoid repetition, and to reduce maintenance when the underlying 

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338169
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
--- End diff --

The comments here should probably just be put in parentheses. Looks strange 
in plain text


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338367
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+
+  
+  ```
 
-
-
-
-
-
+  Engine elements may also specify fuzzy matches using '>', '>=' etc. to 
avoid repetition, and to reduce maintenance when the underlying 

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338281
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+
+  
+  ```
 
-
-
-
-
-
+  Engine elements may also specify fuzzy matches using '>', '>=' etc. to 
avoid repetition, and to reduce maintenance when the underlying 

[GitHub] cordova-medic pull request: CB-10405 - Connectivity issue to Cordo...

[sarangan12]

GitHub user sarangan12 opened a pull request:

https://github.com/apache/cordova-medic/pull/74

CB-10405 - Connectivity issue to Cordova VM

Added Retry Logic to connect to cordova VM.

@dblotsky @riknoll @nikhilkh Please review and merge this PR?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sarangan12/cordova-medic CB-10405

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-medic/pull/74.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #74


commit 016f6e51ed192c51d9b82312aba378ce3a0f865a
Author: Sarangan Rajamanickam 
Date:   2016-01-29T23:47:54Z

CB-10405 - Connectivity issue to Cordova VM

Added Retry Logic to connect to cordova VM.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Add "Linux" to "blackberry10"

[Wesley-Chan]

GitHub user Wesley-Chan opened a pull request:

https://github.com/apache/cordova-docs/pull/475

Add "Linux" to "blackberry10"

You can build blackberry10 app in Linux.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Wesley-Chan/cordova-docs patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-docs/pull/475.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #475


commit 1aab76826402d4d1e441f5918822c422b86152f2
Author: Wesley 
Date:   2016-01-30T02:18:25Z

Add "Linux" to "blackberry10"

You can build blackberry10 app in Linux.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

Re: Docs versioning scheme

[Steven Gill]

I'll try to add a redirect in .htaccess to point 6.0.0 to 6.x
On Jan 29, 2016 7:35 PM, "Steven Gill"  wrote:

> Yes. Sorry. I was just trying to get it out asap. I'll look into updating
> it on Sunday/Monday.
> On Jan 29, 2016 7:09 PM, "Carlos Santana"  wrote:
>
>> +1
>>
>> On Fri, Jan 29, 2016 at 8:47 PM Nikhil Khandelwal > >
>> wrote:
>>
>> > Looks we did a release for the docs with the tools release. Is it
>> possible
>> > to name it 6.x instead of 6.0.0? All URLs to 6.0.0 will break if we do
>> that
>> > but we should do that sooner rather than later to minimize impact.
>> >
>> > As discussed, micro-versioning of docs does not buy us much. I'll
>> enhance
>> > our cordova-docs readme and editorial guide for docs with details on
>> how we
>> > handle versioning.
>> >
>> > -Nikhil
>> >
>> > -Original Message-
>> > From: Jesse [mailto:purplecabb...@gmail.com]
>> > Sent: Thursday, January 21, 2016 2:50 PM
>> > To: dev@cordova.apache.org
>> > Subject: Re: Docs versioning scheme
>> >
>> > SGTM! +1
>> >
>> >
>> > @purplecabbage
>> >
>> >
>> https://na01.safelinks.protection.outlook.com/?url=risingj.com=01%7c01%7cnikhilkh%40microsoft.com%7c82dab60846b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=fiC5HqwZWlaOSZD4ipn97isk7hjFjVCht9IzgKZKnFA%3d
>> >
>> > On Thu, Jan 21, 2016 at 1:47 PM, Steven Gill 
>> > wrote:
>> >
>> > > +1
>> > >
>> > > On Thu, Jan 21, 2016 at 1:38 PM, Nikhil Khandelwal
>> > > > > > >
>> > > wrote:
>> > >
>> > > > Should we version our docs on every major version (instead of minor
>> > > > version) of cordova CLI that comes out? Should the next version of
>> > > > the
>> > > docs
>> > > > be "6.x"? Honestly, not much changes every minor release and
>> > > > maintaining multiple copies has quite a few downsides w.r.t. SEO
>> > > > (referring to older versions of docs), slow docs builds, huge
>> website
>> > duplication.
>> > > >
>> > > > Lot of our docs relate to platform updates and we need clear
>> > > > sections within them that specify the version of the platform for
>> > > > which the docs apply to. For example, Android 5.1 will introduce new
>> > > > lifetime concepts which will be part of Cordova 6.0 docs release.
>> > > > It's best for the text of the docs itself to have something along
>> > > > the lines of "This applies to cordova-android > 5.1"
>> > > >
>> > > > Similarly, significant future updates to CLI/Lib features can
>> > > > contain the same "This applies to cordova > 6.2".
>> > > >
>> > > > I think it will lead to a simpler model on our website and prevent
>> > > > future version explosion [1].
>> > > >
>> > > > Thanks,
>> > > > Nikhil
>> > > >
>> > > > [1]
>> > > >
>> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fimgu
>> > > > r.com%2fvkeNvUL=01%7c01%7cnikhilkh%40microsoft.com
>> %7c82dab60846
>> > > > b14dded12d08d322b54957%7c72f988bf86f141af91ab2d7cd011db47%7c1=
>> > > > Yh%2b9h4MUN9VfUADA1unTmUExqioMs75xG1HjVYmDSBc%3d
>> > > >
>> > > >
>> > >
>> >
>>
>

Re: help running android native tests

[Homer, Tony]

I thought about the test some more and looked at what happens when a missing 
file is loaded.
Normally CordovaActivity shows a dialog that exits when the user presses ok 
button.
I think this test should check that displayError is being called with an 
appropriate message.
To test this, I overrode displayError in the test activity (showing dialog is 
not very useful in tests).

I submitted a PR with this change.
Joe and Carlos, please let me know if you think it's a reasonable approach.



On 1/29/16, 7:19 PM, "Carlos Santana"  wrote:

>you are correct Homer and Joe, I figured it out the test needs some love
>
>I added the 
>
>
>On Fri, Jan 29, 2016 at 6:58 PM Joe Bowser  wrote:
>
>> Yeah, it looks like the behaviour has changed since this was run.  I have a
>> feeling that someone "refactored" and "cleaned up" the tests and the
>> original intent of this test was lost.
>>
>> So, yeah, this should have an intent provided to it, and this test should
>> fail.  The tests definitely need to be looked at again and their usefulness
>> re-evaluated.
>>
>> On Fri, Jan 29, 2016 at 4:35 PM, Homer, Tony  wrote:
>>
>> > HtmlNotFoundTest fails for me too.
>> >
>> > Is it a problem that the CordovaActivity displays an error dialog?
>> > If it is, we could override displayError in MainTestActivity.
>> >
>> > Maybe it's simpler than that - should the test be setting an errorUrl and
>> > then asserting that the errorUrl has been loaded?
>> > If no errorUrl is set, testActivity.getCordovaWebView().getUrl() would
>> > still be equal to START_URL, wouldn't it?
>> >
>> >
>> > In that case the current assertion should fail (and the test would fail).
>> >
>> > On 1/29/16, 5:16 PM, "Joe Bowser"  wrote:
>> >
>> > >Run it a few times to be sure it's failing.  This test shouldn't fail,
>> but
>> > >isn't as stable as it should be.
>> > >
>> > >On Fri, Jan 29, 2016, 2:41 PM Carlos Santana 
>> > wrote:
>> > >
>> > >> I working on getting my environment and all test pass except for one
>> > >>
>> > >> junit.framework.AssertionFailedError
>> > >> at
>> > org.apache.cordova.test.HtmlNotFoundTest$1.run(HtmlNotFoundTest.java:36)
>> > >> at
>> > >>
>> > >>
>> >
>> android.test.InstrumentationTestCase$1.run(InstrumentationTestCase.java:138)
>> > >> at
>> > android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1871)
>> > >> at android.os.Handler.handleCallback(Handler.java:739)
>> > >> at android.os.Handler.dispatchMessage(Handler.java:95)
>> > >> at android.os.Looper.loop(Looper.java:135)
>> > >> at android.app.ActivityThread.main(ActivityThread.java:5254)
>> > >> at
>> > >>
>> > >>
>> >
>> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
>> > >> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
>> > >>
>> > >> Are the tests wrong, or my setup missing something I followed the
>> > >> instructions in the README.md in the test folder
>> > >>
>> > >>
>> > >> [1]:
>> > https://github.com/apache/cordova-android/blob/master/test/README.md
>> > >>
>> >
>>

[GitHub] cordova-docs pull request: Multi-level ToC Implementation

[nikhilkh]

Github user nikhilkh commented on the pull request:

https://github.com/apache/cordova-docs/pull/464#issuecomment-177052823
  
This looks great! One issue: "Architecture" has no children with URLs and 
it shows up in the TOC. 

![image](https://cloud.githubusercontent.com/assets/2417321/12693212/18418cd0-c6b9-11e5-8cad-11737e0ea161.png)
 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-docs/pull/474#issuecomment-177054397
  
General Comments (sorry for duplication):
* There are a lot of Plugman mentions left. We should probably move to 
talking about the CLI
* A lot of the examples use the old reverse domain style ids
* In the rest of the docs, filenames and directories are usually put in 
inline code blocks. It switches back and forth here


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Changing the XML reference formatting f...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-docs/pull/473


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338469
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+
+  
+  ```
 
-
-
-
-
-
+  Engine elements may also specify fuzzy matches using '>', '>=' etc. to 
avoid repetition, and to reduce maintenance when the underlying 

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338895
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+
+  
+  ```
 
-
-
-
-
-
+  Engine elements may also specify fuzzy matches using '>', '>=' etc. to 
avoid repetition, and to reduce maintenance when the underlying 

[GitHub] cordova-docs pull request: CB-10364: Making plugin.xml a reference

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/474#discussion_r51338219
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
--- End diff --

I think we actually support semver ranges here. See 
https://github.com/apache/cordova-plugin-whitelist/blob/master/plugin.xml#L30


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-android pull request: fix HtmlNotFoundTest so that it pass...

[tony--]

GitHub user tony-- opened a pull request:

https://github.com/apache/cordova-android/pull/256

fix HtmlNotFoundTest so that it passes when file not found is handled 
correctly

override displayError in testActivity to send message to queue (dialogs are 
not very useful in tests)
evaluate message to make sure it contains ERR_FILE_NOT_FOUND and the 
(invalid) START_URL

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tony--/cordova-android fixHtmlNotFoundTest

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-android/pull/256.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #256


commit 4730d9fc6348e4a030c10ec1a7a203bbe96c45fe
Author: Tony Homer 
Date:   2016-01-30T02:28:07Z

fix HtmlNotFoundTest so that it passes when file not found is handled 
correctly




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-medic pull request: CB-10405 - Connectivity issue to Cordo...

[nikhilkh]

Github user nikhilkh commented on a diff in the pull request:

https://github.com/apache/cordova-medic/pull/74#discussion_r51338551
  
--- Diff: lib/testcheck.js ---
@@ -21,22 +21,40 @@
 
 "use strict";
 
-module.exports = function (sha, dbHost) {
+module.exports = function (sha, dbHost, maxnumberoftries, delay) {
 
 var http = require("http"),
 url = require("url"),
 q = require("q");
 
+function tryConnect(options, d, pendingnumberoftries, operation, 
successCallBack){
+http.get(options, successCallBack)
+.on("error", function(e){
+if(pendingnumberoftries > 1){
+console.log("Connection attempt to " + operation + " 
failed. Will try after: " + delay + " milliseconds.");
--- End diff --

Also, consider logging e.message for every failure


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Sitemap Improvements

[nikhilkh]

Github user nikhilkh commented on the pull request:

https://github.com/apache/cordova-docs/pull/472#issuecomment-177050841
  
I'm curious what's the motivation for not using the plugin?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: Changing the XML reference formatting f...

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/473#discussion_r51330488
  
--- Diff: www/static/css-src/main.scss ---
@@ -173,6 +173,12 @@ code.prettyprint {
 border: none !important;
 }
 
+mark {
+background-color: lightblue;
+padding: 0.1px 0.2px 0.1px 0.2px;
+margin-right: 7px;
+}
+
--- End diff --

This should probably go in `_docs.scss`


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[nikhilkh]

Github user nikhilkh commented on the pull request:

https://github.com/apache/cordova-cli/pull/233#issuecomment-177045922
  
Thanks for all the comments! I have made some updates and added missing 
commands. It will be great if you can review again. You may only review: 
677380e5ef928bfc5632dee998bab87f2c40af96 instead of everything again.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

help running android native tests

[Carlos Santana]

I working on getting my environment and all test pass except for one

junit.framework.AssertionFailedError
at org.apache.cordova.test.HtmlNotFoundTest$1.run(HtmlNotFoundTest.java:36)
at
android.test.InstrumentationTestCase$1.run(InstrumentationTestCase.java:138)
at android.app.Instrumentation$SyncRunnable.run(Instrumentation.java:1871)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)

Are the tests wrong, or my setup missing something I followed the
instructions in the README.md in the test folder


[1]: https://github.com/apache/cordova-android/blob/master/test/README.md

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[nikhilkh]

Github user nikhilkh commented on a diff in the pull request:

https://github.com/apache/cordova-cli/pull/233#discussion_r51319845
  
--- Diff: doc/readme.md ---
@@ -0,0 +1,337 @@
+
+
+#Cordova Command-line-interface (CLI) Reference
+
+##Syntax
+
+cordova command [options]
+
+##Global Commands
+
+These commands are available at all times.
+
+| Command  | Description
+|--|--
+| create | Create a project
+| help  | Get help for a command
+
+##Project Commands
+
+These commands are supported in a valid Cordova project.
+
+| Command  | Description
+|--|--
+| info | Generate project information
+| requirements | Checks and print out all the installation requirements 
for platforms specified
+| platform | Manage project platforms
+| plugin   | Manage project plugins
+| prepare  | Copy files into platform(s) for building
+| compile  | Build platform(s)
+| clean| Cleanup project from build artifacts
+| run  | Run project (including prepare && compile)
+| serve| Run project with a local webserver (including prepare)
+
+##Common options
+
+These options appply to all cordova-cli commands.
+
+| Option   | Description
+|--|
+| -d or --verbose  | Pipe out more verbose output to your shell. You 
can also subscribe to `log` and `warn` events if you are consuming 
`cordova-cli` as a node module by calling `cordova.on('log', function() {})` or 
`cordova.on('warn', function() {})`.
+| -v or --version  | Print out the version of your `cordova-cli` 
install.
+| --no-update-notifier | will disable updates check. Alternatively set 
`"optOut": true` in `~/.config/configstore/update-notifier-cordova.json` or set 
`NO_UPDATE_NOTIFIER` environment variable with any value (see details in 
[update-notifier 
docs](https://www.npmjs.com/package/update-notifier#user-settings)).
+|--nohooks | suppress executing hooks (taking RegExp hook 
patterns as parameters)
+
+##Examples
+- The following commands will:
+- Create a cordova project in `myApp` directory.
+- Add `cordova-plugin-camera` to the project and `config.xml`.
+- Add `android` platform to the project
+- Check for system requirements for the `android` platform.
+- Build the project for the `android` platform and emit verbose output.
+- Run the project on `android` emulator or device.
+- Build `android` platform using custom signing options.
+
+```
+cordova create myApp org.apache.cordova.myApp myApp
+cordova plugin add cordova-plugin-camera --save
+cordova platform add android --save
+cordova requirements android
+cordova build android --verbose
+cordova run android
+cordova build android --release -- --keystore="..\android.keystore" 
--storePassword=android --alias=mykey
+```
+##cordova create command
+
+###Synopsis
+
+Create the directory structure for the Cordova project in the specified 
path.
+
+###Syntax
+
+cordova create path [id [name [config]]] [options] 
+
+| Value | Description   |
+|---|---| 
+| path  |  Directory which should not already exist. Cordova will create 
this directory. For more details on the directory structure, see below. |
+| id| _Default_: `io.cordova.hellocordova`   Reverse domain-style 
identifier that maps to `id` attirbute of `widget` element in `config.xml`. 
This can be changed but there may be code generated using this value, such as 
Java package names. It is recommended that you select an appropriate value.  |
+| name  | _Default_: `HelloCordova`  Application's display title that 
maps `name` element in `config.xml` file. This can be changed but there may be 
code generated using this value, such as Java class names. The default value is 
`HelloCordova`, but it is recommended that you select an appropriate value. |
+| config | JSON string whose key/values will be included in 
``/.cordova/config.json |
+
+###Options
+
+| Option | Description |
+||-|
+| --template |  Use a custom template located locally, in NPM, or GitHub. |
+| --copy-from\|--src | _Deprecated_  Use --template instead. 
Specifies a directory from which to copy the current Cordova project. |
+|--link-to | Symlink to specified `www` directory without creating a copy. 
|
+
+###Directory structure
+A Cordova application built with `cordova-cli` will have the following 
directory structure:
+
+myapp/
+|-- config.xml
+|-- hooks/
+|-- merges/
+| | |-- android/
+| | |-- 

[GitHub] cordova-android pull request: CB-10472 NullPointerException: org.a...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-android/pull/255


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10389: Turning config.xml documentat...

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/463#discussion_r51297388
  
--- Diff: www/docs/en/dev/config_ref/index.md ---
@@ -22,8 +22,8 @@ title: The config.xml File
 
 # The config.xml File
--- End diff --

Rename this to 'Config.xml'?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: CB-10459: cordova platform list should m...

[sarangan12]

GitHub user sarangan12 opened a pull request:

https://github.com/apache/cordova-lib/pull/368

CB-10459: cordova platform list should mark amazon-fireos and wp8 as 
deprecated

Added depracted information to wp8 and amazon-fireos

JIRA Issue Link: https://issues.apache.org/jira/browse/CB-10459

@nikhilkh @dblotsky @riknoll Can you please review and merge this  PR?

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sarangan12/cordova-lib CB-10459

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-lib/pull/368.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #368


commit db5d2fc65bb3e5ef78cf9e0fe5ad68b2d219e57a
Author: Sarangan Rajamanickam 
Date:   2016-01-29T00:17:52Z

CB-10459: cordova platform list should mark amazon-fireos and wp8 as 
deprecated

Added depracted information to wp8 and amazon-fireos




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10389: Turning config.xml documentat...

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/463#discussion_r51298135
  
--- Diff: www/docs/en/dev/config_ref/index.md ---
@@ -45,207 +45,356 @@ passively copied into various `platforms/` 
subdirectories, for example:
 app/platforms/blackberry10/www/config.xml
 app/platforms/android/res/xml/config.xml
 
-This section details global and cross-platform configuration options.
-See the following sections for platform-specific options:
-
-- [iOS Configuration](../guide/platforms/ios/config.html)
-- [Android Configuration](../guide/platforms/android/config.html)
-- [BlackBerry 10 
Configuration](../guide/platforms/blackberry10/config.html)
-
 In addition to the various configuration options detailed below, you
 can also configure an application's core set of images for each target
 platform. See [Icons and Splash Screens](images.html) for more information.
 
-## Core Configuration Elements
-
-This example shows the default `config.xml` generated by the CLI's
-`create` command, described in [The Command-Line 
Interface](../guide/cli/index.html):
-
-
-HelloWorld
-
-A sample Apache Cordova application that responds to the 
deviceready event.
-
-http://cordova.io;>
-Apache Cordova Team
-
-
-
-
-
-The following configuration elements appear in the top-level
-`config.xml` file, and are supported across all supported Cordova
-platforms:
-
-- The `` element's `id` attribute provides the app's
-  reverse-domain identifier, and the `version` its full version number
-  expressed in major/minor/patch notation.
-
-  The widget tag can also have attributes that specify alternative 
versions,
-  namely `versionCode` for Android, `CFBundleVersion` for iOS, and 
-  `packageVersion` for Windows. See the Additional Versioning section 
below 
-  for details.
-
-- The `` element specifies the app's formal name, as it appears
-  on the device's home screen and within app-store interfaces.
-
-- The `` and `` elements specify metadata and
-  contact information that may appear within app-store listings.
-
-- The optional `` element defines the app's starting
-  page in the top-level web assets directory. The default value is
-  `index.html`, which customarily appears in a project's top-level
-  `www` directory.
-
-- `` elements define the set of external domains the app is
-  allowed to communicate with. The default value shown above allows
-  it to access any server. See the Domain [Whitelist 
Guide](../guide/appdev/whitelist/index.html) for details.
-
-- The `` tag sets various options as pairs of
-  `name`/`value` attributes. Each preference's `name` is
-  case-insensitive.  Many preferences are unique to specific
-  platforms, as listed at the top of this page. The following sections
-  detail preferences that apply to more than one platform.
-
-### Additional Versioning
+# widget
+   Root element of the config.xml document.
+
+   Attributes(type) | Description
+    | 
+   id (string) | *Required: true*  Specifies the app's reverse-domain 
identifier, and the `version` its full version number expressed in 
major/minor/patch notation.
+   version (string) | *Required: true*  Full version number expressed 
in major/minor/patch notation.
+   versionCode (string) | *Required: false*  **Platforms supported: 
Android**  Alternative version for Android.
+   CFBundleVersion (string) | *Required: false*  **Platforms 
supported: iOS**  Alternative version for iOS.  
+   packageVersion (string) | *Required: false*  **Platforms 
supported: Windows**  Alternative version for Windows.
+   packageName (string) | *Default: Cordova.Example*  **Platforms 
supported: Windows**  Package name for Windows.
+   xmlns (string) | *Required: true*  namespace for the config.xml 
document.
+   xmlns:cdv (string) | *Required: true*  namespace prefix.
--- End diff --

'N'amespace.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10389: Turning config.xml documentat...

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/463#discussion_r51298099
  
--- Diff: www/docs/en/dev/config_ref/index.md ---
@@ -45,207 +45,356 @@ passively copied into various `platforms/` 
subdirectories, for example:
 app/platforms/blackberry10/www/config.xml
 app/platforms/android/res/xml/config.xml
 
-This section details global and cross-platform configuration options.
-See the following sections for platform-specific options:
-
-- [iOS Configuration](../guide/platforms/ios/config.html)
-- [Android Configuration](../guide/platforms/android/config.html)
-- [BlackBerry 10 
Configuration](../guide/platforms/blackberry10/config.html)
-
 In addition to the various configuration options detailed below, you
 can also configure an application's core set of images for each target
 platform. See [Icons and Splash Screens](images.html) for more information.
 
-## Core Configuration Elements
-
-This example shows the default `config.xml` generated by the CLI's
-`create` command, described in [The Command-Line 
Interface](../guide/cli/index.html):
-
-
-HelloWorld
-
-A sample Apache Cordova application that responds to the 
deviceready event.
-
-http://cordova.io;>
-Apache Cordova Team
-
-
-
-
-
-The following configuration elements appear in the top-level
-`config.xml` file, and are supported across all supported Cordova
-platforms:
-
-- The `` element's `id` attribute provides the app's
-  reverse-domain identifier, and the `version` its full version number
-  expressed in major/minor/patch notation.
-
-  The widget tag can also have attributes that specify alternative 
versions,
-  namely `versionCode` for Android, `CFBundleVersion` for iOS, and 
-  `packageVersion` for Windows. See the Additional Versioning section 
below 
-  for details.
-
-- The `` element specifies the app's formal name, as it appears
-  on the device's home screen and within app-store interfaces.
-
-- The `` and `` elements specify metadata and
-  contact information that may appear within app-store listings.
-
-- The optional `` element defines the app's starting
-  page in the top-level web assets directory. The default value is
-  `index.html`, which customarily appears in a project's top-level
-  `www` directory.
-
-- `` elements define the set of external domains the app is
-  allowed to communicate with. The default value shown above allows
-  it to access any server. See the Domain [Whitelist 
Guide](../guide/appdev/whitelist/index.html) for details.
-
-- The `` tag sets various options as pairs of
-  `name`/`value` attributes. Each preference's `name` is
-  case-insensitive.  Many preferences are unique to specific
-  platforms, as listed at the top of this page. The following sections
-  detail preferences that apply to more than one platform.
-
-### Additional Versioning
+# widget
+   Root element of the config.xml document.
+
+   Attributes(type) | Description
+    | 
+   id (string) | *Required: true*  Specifies the app's reverse-domain 
identifier, and the `version` its full version number expressed in 
major/minor/patch notation.
+   version (string) | *Required: true*  Full version number expressed 
in major/minor/patch notation.
+   versionCode (string) | *Required: false*  **Platforms supported: 
Android**  Alternative version for Android.
+   CFBundleVersion (string) | *Required: false*  **Platforms 
supported: iOS**  Alternative version for iOS.  
+   packageVersion (string) | *Required: false*  **Platforms 
supported: Windows**  Alternative version for Windows.
+   packageName (string) | *Default: Cordova.Example*  **Platforms 
supported: Windows**  Package name for Windows.
+   xmlns (string) | *Required: true*  namespace for the config.xml 
document.
--- End diff --

'N'amespace. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: CB-10459: cordova platform list should m...

[riknoll]

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-lib/pull/368#issuecomment-176912757
  
LGTM. My only suggestion would be that it might be nice if we grabbed the 
deprecation info from somewhere instead of hard coding it in that method. Is it 
already encoded somewhere in cordova-lib? If not, should it be? Or should it be 
specified in the platform somehow?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-cli/pull/233#discussion_r51300911
  
--- Diff: doc/readme.md ---
@@ -0,0 +1,337 @@
+
+
+#Cordova Command-line-interface (CLI) Reference
+
+##Syntax
+
+cordova command [options]
+
+##Global Commands
+
+These commands are available at all times.
+
+| Command  | Description
+|--|--
+| create | Create a project
+| help  | Get help for a command
+
+##Project Commands
+
+These commands are supported in a valid Cordova project.
+
+| Command  | Description
+|--|--
+| info | Generate project information
+| requirements | Checks and print out all the installation requirements 
for platforms specified
+| platform | Manage project platforms
+| plugin   | Manage project plugins
+| prepare  | Copy files into platform(s) for building
+| compile  | Build platform(s)
+| clean| Cleanup project from build artifacts
+| run  | Run project (including prepare && compile)
+| serve| Run project with a local webserver (including prepare)
+
+##Common options
+
+These options appply to all cordova-cli commands.
+
+| Option   | Description
+|--|
+| -d or --verbose  | Pipe out more verbose output to your shell. You 
can also subscribe to `log` and `warn` events if you are consuming 
`cordova-cli` as a node module by calling `cordova.on('log', function() {})` or 
`cordova.on('warn', function() {})`.
+| -v or --version  | Print out the version of your `cordova-cli` 
install.
+| --no-update-notifier | will disable updates check. Alternatively set 
`"optOut": true` in `~/.config/configstore/update-notifier-cordova.json` or set 
`NO_UPDATE_NOTIFIER` environment variable with any value (see details in 
[update-notifier 
docs](https://www.npmjs.com/package/update-notifier#user-settings)).
+|--nohooks | suppress executing hooks (taking RegExp hook 
patterns as parameters)
+
+##Examples
+- The following commands will:
+- Create a cordova project in `myApp` directory.
+- Add `cordova-plugin-camera` to the project and `config.xml`.
+- Add `android` platform to the project
+- Check for system requirements for the `android` platform.
+- Build the project for the `android` platform and emit verbose output.
+- Run the project on `android` emulator or device.
+- Build `android` platform using custom signing options.
+
+```
+cordova create myApp org.apache.cordova.myApp myApp
+cordova plugin add cordova-plugin-camera --save
+cordova platform add android --save
+cordova requirements android
+cordova build android --verbose
+cordova run android
+cordova build android --release -- --keystore="..\android.keystore" 
--storePassword=android --alias=mykey
+```
+##cordova create command
+
+###Synopsis
+
+Create the directory structure for the Cordova project in the specified 
path.
+
+###Syntax
+
+cordova create path [id [name [config]]] [options] 
+
+| Value | Description   |
+|---|---| 
+| path  |  Directory which should not already exist. Cordova will create 
this directory. For more details on the directory structure, see below. |
+| id| _Default_: `io.cordova.hellocordova`   Reverse domain-style 
identifier that maps to `id` attirbute of `widget` element in `config.xml`. 
This can be changed but there may be code generated using this value, such as 
Java package names. It is recommended that you select an appropriate value.  |
+| name  | _Default_: `HelloCordova`  Application's display title that 
maps `name` element in `config.xml` file. This can be changed but there may be 
code generated using this value, such as Java class names. The default value is 
`HelloCordova`, but it is recommended that you select an appropriate value. |
+| config | JSON string whose key/values will be included in 
``/.cordova/config.json |
+
+###Options
+
+| Option | Description |
+||-|
+| --template |  Use a custom template located locally, in NPM, or GitHub. |
+| --copy-from\|--src | _Deprecated_  Use --template instead. 
Specifies a directory from which to copy the current Cordova project. |
+|--link-to | Symlink to specified `www` directory without creating a copy. 
|
+
+###Directory structure
+A Cordova application built with `cordova-cli` will have the following 
directory structure:
+
+myapp/
+|-- config.xml
+|-- hooks/
+|-- merges/
+| | |-- android/
+| | |-- 

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-cli/pull/233#discussion_r51300687
  
--- Diff: doc/readme.md ---
@@ -0,0 +1,337 @@
+
+
+#Cordova Command-line-interface (CLI) Reference
+
+##Syntax
+
+cordova command [options]
+
+##Global Commands
+
+These commands are available at all times.
+
+| Command  | Description
+|--|--
+| create | Create a project
+| help  | Get help for a command
+
+##Project Commands
+
+These commands are supported in a valid Cordova project.
+
+| Command  | Description
+|--|--
+| info | Generate project information
+| requirements | Checks and print out all the installation requirements 
for platforms specified
+| platform | Manage project platforms
+| plugin   | Manage project plugins
+| prepare  | Copy files into platform(s) for building
+| compile  | Build platform(s)
+| clean| Cleanup project from build artifacts
+| run  | Run project (including prepare && compile)
+| serve| Run project with a local webserver (including prepare)
+
+##Common options
+
+These options appply to all cordova-cli commands.
+
+| Option   | Description
+|--|
+| -d or --verbose  | Pipe out more verbose output to your shell. You 
can also subscribe to `log` and `warn` events if you are consuming 
`cordova-cli` as a node module by calling `cordova.on('log', function() {})` or 
`cordova.on('warn', function() {})`.
+| -v or --version  | Print out the version of your `cordova-cli` 
install.
+| --no-update-notifier | will disable updates check. Alternatively set 
`"optOut": true` in `~/.config/configstore/update-notifier-cordova.json` or set 
`NO_UPDATE_NOTIFIER` environment variable with any value (see details in 
[update-notifier 
docs](https://www.npmjs.com/package/update-notifier#user-settings)).
+|--nohooks | suppress executing hooks (taking RegExp hook 
patterns as parameters)
--- End diff --

'S'uppress


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10389: Turning config.xml documentat...

[riknoll]

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/463#discussion_r51300878
  
--- Diff: www/docs/en/dev/config_ref/index.md ---
@@ -45,207 +45,356 @@ passively copied into various `platforms/` 
subdirectories, for example:
 app/platforms/blackberry10/www/config.xml
 app/platforms/android/res/xml/config.xml
 
-This section details global and cross-platform configuration options.
-See the following sections for platform-specific options:
-
-- [iOS Configuration](../guide/platforms/ios/config.html)
-- [Android Configuration](../guide/platforms/android/config.html)
-- [BlackBerry 10 
Configuration](../guide/platforms/blackberry10/config.html)
-
 In addition to the various configuration options detailed below, you
 can also configure an application's core set of images for each target
 platform. See [Icons and Splash Screens](images.html) for more information.
 
-## Core Configuration Elements
-
-This example shows the default `config.xml` generated by the CLI's
-`create` command, described in [The Command-Line 
Interface](../guide/cli/index.html):
-
-
-HelloWorld
-
-A sample Apache Cordova application that responds to the 
deviceready event.
-
-http://cordova.io;>
-Apache Cordova Team
-
-
-
-
-
-The following configuration elements appear in the top-level
-`config.xml` file, and are supported across all supported Cordova
-platforms:
-
-- The `` element's `id` attribute provides the app's
-  reverse-domain identifier, and the `version` its full version number
-  expressed in major/minor/patch notation.
-
-  The widget tag can also have attributes that specify alternative 
versions,
-  namely `versionCode` for Android, `CFBundleVersion` for iOS, and 
-  `packageVersion` for Windows. See the Additional Versioning section 
below 
-  for details.
-
-- The `` element specifies the app's formal name, as it appears
-  on the device's home screen and within app-store interfaces.
-
-- The `` and `` elements specify metadata and
-  contact information that may appear within app-store listings.
-
-- The optional `` element defines the app's starting
-  page in the top-level web assets directory. The default value is
-  `index.html`, which customarily appears in a project's top-level
-  `www` directory.
-
-- `` elements define the set of external domains the app is
-  allowed to communicate with. The default value shown above allows
-  it to access any server. See the Domain [Whitelist 
Guide](../guide/appdev/whitelist/index.html) for details.
-
-- The `` tag sets various options as pairs of
-  `name`/`value` attributes. Each preference's `name` is
-  case-insensitive.  Many preferences are unique to specific
-  platforms, as listed at the top of this page. The following sections
-  detail preferences that apply to more than one platform.
-
-### Additional Versioning
+# widget
+   Root element of the config.xml document.
+
+   Attributes(type) | Description
+    | 
+   id (string) | *Required: true*  Specifies the app's reverse-domain 
identifier, and the `version` its full version number expressed in 
major/minor/patch notation.
+   version (string) | *Required: true*  Full version number expressed 
in major/minor/patch notation.
+   versionCode (string) | *Required: false*  **Platforms supported: 
Android**  Alternative version for Android.
+   CFBundleVersion (string) | *Required: false*  **Platforms 
supported: iOS**  Alternative version for iOS.  
+   packageVersion (string) | *Required: false*  **Platforms 
supported: Windows**  Alternative version for Windows.
+   packageName (string) | *Default: Cordova.Example*  **Platforms 
supported: Windows**  Package name for Windows.
+   xmlns (string) | *Required: true*  namespace for the config.xml 
document.
+   xmlns:cdv (string) | *Required: true*  namespace prefix.
+
+   Examples:
 
-Android, iOS, and Windows support a second version string (or number) in 
-addition to the one visible in app stores:
+
+
 
-- 
[versionCode](http://developer.android.com/tools/publishing/versioning.html)
-  for Android
-- 
[CFBundleVersion](http://stackoverflow.com/questions/4933093/cfbundleversion-in-the-info-plist-upload-error)
-  for iOS
-- 
[packageVersion](https://msdn.microsoft.com/en-us/library/windows/apps/br211441.aspx)
-  for Windows
+
+
 
-Below is an example that explicitly sets these properties:
+
+
+
 
  

[GitHub] cordova-medic pull request: CB-10474: Fix cordova-ios logging

[riknoll]

GitHub user riknoll opened a pull request:

https://github.com/apache/cordova-medic/pull/73

CB-10474: Fix cordova-ios logging

We were searching for the simulator logs in the wrong place. This fix 
attempts to figure out what simulator is running and grab the system logs for 
it.

@dblotsky @nikhilkh @sarangan12 please review and make sure that I'm not 
doing terrible things with `shelljs.exec()`.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-medic CB-10474rebase

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-medic/pull/73.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #73


commit ea6bc93bcf52d484ff2e2c8ade7aedc331f9516b
Author: Richard Knoll 
Date:   2016-01-29T01:18:22Z

CB-10474: Fix medic-log behavior for cordova-ios

commit dbd675eb5475ab7b040b54399bb51673d91604f4
Author: Richard Knoll 
Date:   2016-01-29T01:45:30Z

CB-10474: Using local CLI for cordova run




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10389: Turning config.xml documentat...

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/463#discussion_r51297739
  
--- Diff: www/docs/en/dev/config_ref/index.md ---
@@ -45,207 +45,356 @@ passively copied into various `platforms/` 
subdirectories, for example:
 app/platforms/blackberry10/www/config.xml
 app/platforms/android/res/xml/config.xml
 
-This section details global and cross-platform configuration options.
-See the following sections for platform-specific options:
-
-- [iOS Configuration](../guide/platforms/ios/config.html)
-- [Android Configuration](../guide/platforms/android/config.html)
-- [BlackBerry 10 
Configuration](../guide/platforms/blackberry10/config.html)
-
 In addition to the various configuration options detailed below, you
 can also configure an application's core set of images for each target
 platform. See [Icons and Splash Screens](images.html) for more information.
 
-## Core Configuration Elements
-
-This example shows the default `config.xml` generated by the CLI's
-`create` command, described in [The Command-Line 
Interface](../guide/cli/index.html):
-
-
-HelloWorld
-
-A sample Apache Cordova application that responds to the 
deviceready event.
-
-http://cordova.io;>
-Apache Cordova Team
-
-
-
-
-
-The following configuration elements appear in the top-level
-`config.xml` file, and are supported across all supported Cordova
-platforms:
-
-- The `` element's `id` attribute provides the app's
-  reverse-domain identifier, and the `version` its full version number
-  expressed in major/minor/patch notation.
-
-  The widget tag can also have attributes that specify alternative 
versions,
-  namely `versionCode` for Android, `CFBundleVersion` for iOS, and 
-  `packageVersion` for Windows. See the Additional Versioning section 
below 
-  for details.
-
-- The `` element specifies the app's formal name, as it appears
-  on the device's home screen and within app-store interfaces.
-
-- The `` and `` elements specify metadata and
-  contact information that may appear within app-store listings.
-
-- The optional `` element defines the app's starting
-  page in the top-level web assets directory. The default value is
-  `index.html`, which customarily appears in a project's top-level
-  `www` directory.
-
-- `` elements define the set of external domains the app is
-  allowed to communicate with. The default value shown above allows
-  it to access any server. See the Domain [Whitelist 
Guide](../guide/appdev/whitelist/index.html) for details.
-
-- The `` tag sets various options as pairs of
-  `name`/`value` attributes. Each preference's `name` is
-  case-insensitive.  Many preferences are unique to specific
-  platforms, as listed at the top of this page. The following sections
-  detail preferences that apply to more than one platform.
-
-### Additional Versioning
+# widget
--- End diff --

I followed the format of  as heading i.e.  here, for 
plugin.xml. What do you think is better? We should be consistent.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: CB-10459: cordova platform list should m...

[sarangan12]

Github user sarangan12 closed the pull request at:

https://github.com/apache/cordova-lib/pull/367


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-lib pull request: CB-10459: cordova platform list should m...

[sarangan12]

Github user sarangan12 commented on the pull request:

https://github.com/apache/cordova-lib/pull/367#issuecomment-176899461
  
I will open a new PR after squashing the commits into a single one


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[rakatyal]

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-cli/pull/233#discussion_r51300643
  
--- Diff: doc/readme.md ---
@@ -0,0 +1,337 @@
+
+
+#Cordova Command-line-interface (CLI) Reference
+
+##Syntax
+
+cordova command [options]
+
+##Global Commands
+
+These commands are available at all times.
+
+| Command  | Description
+|--|--
+| create | Create a project
+| help  | Get help for a command
+
+##Project Commands
+
+These commands are supported in a valid Cordova project.
+
+| Command  | Description
+|--|--
+| info | Generate project information
+| requirements | Checks and print out all the installation requirements 
for platforms specified
+| platform | Manage project platforms
+| plugin   | Manage project plugins
+| prepare  | Copy files into platform(s) for building
+| compile  | Build platform(s)
+| clean| Cleanup project from build artifacts
+| run  | Run project (including prepare && compile)
+| serve| Run project with a local webserver (including prepare)
+
+##Common options
+
+These options appply to all cordova-cli commands.
+
+| Option   | Description
+|--|
+| -d or --verbose  | Pipe out more verbose output to your shell. You 
can also subscribe to `log` and `warn` events if you are consuming 
`cordova-cli` as a node module by calling `cordova.on('log', function() {})` or 
`cordova.on('warn', function() {})`.
+| -v or --version  | Print out the version of your `cordova-cli` 
install.
+| --no-update-notifier | will disable updates check. Alternatively set 
`"optOut": true` in `~/.config/configstore/update-notifier-cordova.json` or set 
`NO_UPDATE_NOTIFIER` environment variable with any value (see details in 
[update-notifier 
docs](https://www.npmjs.com/package/update-notifier#user-settings)).
--- End diff --

'W'ill disable updates check. We should have all of them start with a caps 
for consistency.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10332 Android Guide Improvements

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51309545
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
--- End diff --

I'm not 100% sure, but this is someting that should be set by `check_reqs` 
at the [build 
time](https://github.com/apache/cordova-android/blob/master/bin/lib/check_reqs.js#L99)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-docs pull request: CB-10332 Android Guide Improvements

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51309554
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
-run and debug Android platform. Otherwise, `Android Stand-alone SDK Tools`
-are enough to build and deploy Android application.
+run and debug the Android platform. Otherwise, the Android Stand-alone SDK 
Tools
+are enough to build and deploy Android applications.
 
 Detailed installation instructions are available as part of installation
 links above.
 
-For Cordova command-line tools to work, or the CLI that is based upon

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-cli/pull/233#discussion_r51310924
  
--- Diff: doc/readme.md ---
@@ -0,0 +1,337 @@
+
+
+#Cordova Command-line-interface (CLI) Reference
+
+##Syntax
+
+cordova command [options]
+
+##Global Commands
+
+These commands are available at all times.
+
+| Command  | Description
+|--|--
+| create | Create a project
+| help  | Get help for a command
+
+##Project Commands
+
+These commands are supported in a valid Cordova project.
+
+| Command  | Description
+|--|--
+| info | Generate project information
+| requirements | Checks and print out all the installation requirements 
for platforms specified
+| platform | Manage project platforms
+| plugin   | Manage project plugins
+| prepare  | Copy files into platform(s) for building
+| compile  | Build platform(s)
+| clean| Cleanup project from build artifacts
+| run  | Run project (including prepare && compile)
+| serve| Run project with a local webserver (including prepare)
+
+##Common options
+
+These options appply to all cordova-cli commands.
+
+| Option   | Description
+|--|
+| -d or --verbose  | Pipe out more verbose output to your shell. You 
can also subscribe to `log` and `warn` events if you are consuming 
`cordova-cli` as a node module by calling `cordova.on('log', function() {})` or 
`cordova.on('warn', function() {})`.
+| -v or --version  | Print out the version of your `cordova-cli` 
install.
+| --no-update-notifier | will disable updates check. Alternatively set 
`"optOut": true` in `~/.config/configstore/update-notifier-cordova.json` or set 
`NO_UPDATE_NOTIFIER` environment variable with any value (see details in 
[update-notifier 
docs](https://www.npmjs.com/package/update-notifier#user-settings)).
+|--nohooks | suppress executing hooks (taking RegExp hook 
patterns as parameters)
+
+##Examples
+- The following commands will:
+- Create a cordova project in `myApp` directory.
+- Add `cordova-plugin-camera` to the project and `config.xml`.
+- Add `android` platform to the project
+- Check for system requirements for the `android` platform.
+- Build the project for the `android` platform and emit verbose output.
+- Run the project on `android` emulator or device.
+- Build `android` platform using custom signing options.
+
+```
+cordova create myApp org.apache.cordova.myApp myApp
+cordova plugin add cordova-plugin-camera --save
+cordova platform add android --save
+cordova requirements android
+cordova build android --verbose
+cordova run android
+cordova build android --release -- --keystore="..\android.keystore" 
--storePassword=android --alias=mykey
+```
+##cordova create command
+
+###Synopsis
+
+Create the directory structure for the Cordova project in the specified 
path.
+
+###Syntax
+
+cordova create path [id [name [config]]] [options] 
+
+| Value | Description   |
+|---|---| 
+| path  |  Directory which should not already exist. Cordova will create 
this directory. For more details on the directory structure, see below. |
+| id| _Default_: `io.cordova.hellocordova`   Reverse domain-style 
identifier that maps to `id` attirbute of `widget` element in `config.xml`. 
This can be changed but there may be code generated using this value, such as 
Java package names. It is recommended that you select an appropriate value.  |
+| name  | _Default_: `HelloCordova`  Application's display title that 
maps `name` element in `config.xml` file. This can be changed but there may be 
code generated using this value, such as Java class names. The default value is 
`HelloCordova`, but it is recommended that you select an appropriate value. |
+| config | JSON string whose key/values will be included in 
``/.cordova/config.json |
+
+###Options
+
+| Option | Description |
+||-|
+| --template |  Use a custom template located locally, in NPM, or GitHub. |
+| --copy-from\|--src | _Deprecated_  Use --template instead. 
Specifies a directory from which to copy the current Cordova project. |
+|--link-to | Symlink to specified `www` directory without creating a copy. 
|
+
+###Directory structure
+A Cordova application built with `cordova-cli` will have the following 
directory structure:
+
+myapp/
+|-- config.xml
+|-- hooks/
+|-- merges/
+| | |-- android/
+| | |-- 

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-cli/pull/233#discussion_r51311693
  
--- Diff: doc/readme.md ---
@@ -0,0 +1,337 @@
+
+
+#Cordova Command-line-interface (CLI) Reference
+
+##Syntax
+
+cordova command [options]
+
+##Global Commands
+
+These commands are available at all times.
+
+| Command  | Description
+|--|--
+| create | Create a project
+| help  | Get help for a command
+
+##Project Commands
+
+These commands are supported in a valid Cordova project.
+
+| Command  | Description
+|--|--
+| info | Generate project information
+| requirements | Checks and print out all the installation requirements 
for platforms specified
+| platform | Manage project platforms
+| plugin   | Manage project plugins
+| prepare  | Copy files into platform(s) for building
+| compile  | Build platform(s)
+| clean| Cleanup project from build artifacts
+| run  | Run project (including prepare && compile)
+| serve| Run project with a local webserver (including prepare)
+
+##Common options
+
+These options appply to all cordova-cli commands.
+
+| Option   | Description
+|--|
+| -d or --verbose  | Pipe out more verbose output to your shell. You 
can also subscribe to `log` and `warn` events if you are consuming 
`cordova-cli` as a node module by calling `cordova.on('log', function() {})` or 
`cordova.on('warn', function() {})`.
+| -v or --version  | Print out the version of your `cordova-cli` 
install.
+| --no-update-notifier | will disable updates check. Alternatively set 
`"optOut": true` in `~/.config/configstore/update-notifier-cordova.json` or set 
`NO_UPDATE_NOTIFIER` environment variable with any value (see details in 
[update-notifier 
docs](https://www.npmjs.com/package/update-notifier#user-settings)).
+|--nohooks | suppress executing hooks (taking RegExp hook 
patterns as parameters)
+
+##Examples
+- The following commands will:
+- Create a cordova project in `myApp` directory.
+- Add `cordova-plugin-camera` to the project and `config.xml`.
+- Add `android` platform to the project
+- Check for system requirements for the `android` platform.
+- Build the project for the `android` platform and emit verbose output.
+- Run the project on `android` emulator or device.
+- Build `android` platform using custom signing options.
+
+```
+cordova create myApp org.apache.cordova.myApp myApp
+cordova plugin add cordova-plugin-camera --save
+cordova platform add android --save
+cordova requirements android
+cordova build android --verbose
+cordova run android
+cordova build android --release -- --keystore="..\android.keystore" 
--storePassword=android --alias=mykey
+```
+##cordova create command
+
+###Synopsis
+
+Create the directory structure for the Cordova project in the specified 
path.
+
+###Syntax
+
+cordova create path [id [name [config]]] [options] 
+
+| Value | Description   |
+|---|---| 
+| path  |  Directory which should not already exist. Cordova will create 
this directory. For more details on the directory structure, see below. |
+| id| _Default_: `io.cordova.hellocordova`   Reverse domain-style 
identifier that maps to `id` attirbute of `widget` element in `config.xml`. 
This can be changed but there may be code generated using this value, such as 
Java package names. It is recommended that you select an appropriate value.  |
+| name  | _Default_: `HelloCordova`  Application's display title that 
maps `name` element in `config.xml` file. This can be changed but there may be 
code generated using this value, such as Java class names. The default value is 
`HelloCordova`, but it is recommended that you select an appropriate value. |
+| config | JSON string whose key/values will be included in 
``/.cordova/config.json |
+
+###Options
+
+| Option | Description |
+||-|
+| --template |  Use a custom template located locally, in NPM, or GitHub. |
+| --copy-from\|--src | _Deprecated_  Use --template instead. 
Specifies a directory from which to copy the current Cordova project. |
+|--link-to | Symlink to specified `www` directory without creating a copy. 
|
+
+###Directory structure
+A Cordova application built with `cordova-cli` will have the following 
directory structure:
+
+myapp/
+|-- config.xml
+|-- hooks/
+|-- merges/
+| | |-- android/
+| | |-- 

[GitHub] cordova-lib pull request: CB-10459: cordova platform list should m...

[sarangan12]

Github user sarangan12 commented on the pull request:

https://github.com/apache/cordova-lib/pull/368#issuecomment-176937879
  
@riknoll Agreed. Moved the deprecated info to Json file 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org

[GitHub] cordova-cli pull request: Add cordova CLI readme docs

[vladimir-kotikov]

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-cli/pull/233#discussion_r51311142
  
--- Diff: doc/readme.md ---
@@ -0,0 +1,337 @@
+
+
+#Cordova Command-line-interface (CLI) Reference
+
+##Syntax
+
+cordova command [options]
+
+##Global Commands
+
+These commands are available at all times.
+
+| Command  | Description
+|--|--
+| create | Create a project
+| help  | Get help for a command
+
+##Project Commands
+
+These commands are supported in a valid Cordova project.
+
+| Command  | Description
+|--|--
+| info | Generate project information
+| requirements | Checks and print out all the installation requirements 
for platforms specified
+| platform | Manage project platforms
+| plugin   | Manage project plugins
+| prepare  | Copy files into platform(s) for building
+| compile  | Build platform(s)
+| clean| Cleanup project from build artifacts
+| run  | Run project (including prepare && compile)
+| serve| Run project with a local webserver (including prepare)
+
+##Common options
+
+These options appply to all cordova-cli commands.
+
+| Option   | Description
+|--|
+| -d or --verbose  | Pipe out more verbose output to your shell. You 
can also subscribe to `log` and `warn` events if you are consuming 
`cordova-cli` as a node module by calling `cordova.on('log', function() {})` or 
`cordova.on('warn', function() {})`.
+| -v or --version  | Print out the version of your `cordova-cli` 
install.
+| --no-update-notifier | will disable updates check. Alternatively set 
`"optOut": true` in `~/.config/configstore/update-notifier-cordova.json` or set 
`NO_UPDATE_NOTIFIER` environment variable with any value (see details in 
[update-notifier 
docs](https://www.npmjs.com/package/update-notifier#user-settings)).
+|--nohooks | suppress executing hooks (taking RegExp hook 
patterns as parameters)
+
+##Examples
+- The following commands will:
+- Create a cordova project in `myApp` directory.
+- Add `cordova-plugin-camera` to the project and `config.xml`.
+- Add `android` platform to the project
+- Check for system requirements for the `android` platform.
+- Build the project for the `android` platform and emit verbose output.
+- Run the project on `android` emulator or device.
+- Build `android` platform using custom signing options.
+
+```
+cordova create myApp org.apache.cordova.myApp myApp
+cordova plugin add cordova-plugin-camera --save
+cordova platform add android --save
+cordova requirements android
+cordova build android --verbose
+cordova run android
+cordova build android --release -- --keystore="..\android.keystore" 
--storePassword=android --alias=mykey
+```
+##cordova create command
+
+###Synopsis
+
+Create the directory structure for the Cordova project in the specified 
path.
+
+###Syntax
+
+cordova create path [id [name [config]]] [options] 
+
+| Value | Description   |
+|---|---| 
+| path  |  Directory which should not already exist. Cordova will create 
this directory. For more details on the directory structure, see below. |
+| id| _Default_: `io.cordova.hellocordova`   Reverse domain-style 
identifier that maps to `id` attirbute of `widget` element in `config.xml`. 
This can be changed but there may be code generated using this value, such as 
Java package names. It is recommended that you select an appropriate value.  |
+| name  | _Default_: `HelloCordova`  Application's display title that 
maps `name` element in `config.xml` file. This can be changed but there may be 
code generated using this value, such as Java class names. The default value is 
`HelloCordova`, but it is recommended that you select an appropriate value. |
+| config | JSON string whose key/values will be included in 
``/.cordova/config.json |
+
+###Options
+
+| Option | Description |
+||-|
+| --template |  Use a custom template located locally, in NPM, or GitHub. |
+| --copy-from\|--src | _Deprecated_  Use --template instead. 
Specifies a directory from which to copy the current Cordova project. |
+|--link-to | Symlink to specified `www` directory without creating a copy. 
|
+
+###Directory structure
+A Cordova application built with `cordova-cli` will have the following 
directory structure:
+
+myapp/
+|-- config.xml
+|-- hooks/
+|-- merges/
+| | |-- android/
+| | |--