Sent: Friday, July 17, 2015 6:53 PM
To: dev@cordova.apache.org
Subject: Re: Discuss Android plugin compatibility problem
+1 to doc and maybe add as a comment in plugin template in cli
Having low number of dependencies or not all is something is good that we aim
for.
On Fri, Jul 17, 2015 at 11:59
, July 17, 2015 6:53 PM
To: dev@cordova.apache.org
Subject: Re: Discuss Android plugin compatibility problem
+1 to doc and maybe add as a comment in plugin template in cli
Having low number of dependencies or not all is something is good that we
aim for.
On Fri, Jul 17, 2015 at 11:59 AM Sergey Grebnov
What's the problem Joe? Having declaring cradle dependencies in plugin.xml
I think is a good thing. At high level a plugin should be able to some how
declare its dependencies for things located in gradle/maven via plugin.xml,
a metada file, or hook.
We in IBM are using gradle in plugin.xml for
Stupid iOS autocorrect had a bunch of typos gradle not cradle
On Fri, Jul 17, 2015 at 9:06 AM Carlos Santana csantan...@gmail.com wrote:
What's the problem Joe? Having declaring cradle dependencies in plugin.xml
I think is a good thing. At high level a plugin should be able to some how
I'm fine with it. I just spaced out and forgot we did that for Crosswalk.
I thought we had a reference to a gradle file instead.
On Fri, Jul 17, 2015 at 6:14 AM Carlos Santana csantan...@gmail.com wrote:
What's the problem Joe? Having declaring cradle dependencies in plugin.xml
I think is a
So, it seems like mechanisms are already in place to enable us to do what we
wanna do here.
The actionable step I'm seeing here is 'updating the docs to ask plugin devs to
use plugin.xml to define gradle dependencies'.
If you folks agree with what this actionable item, I will create a jira
(there are actually not so much dependencies at all).
-Original Message-
From: Mefire O. [mailto:ommen...@microsoft.com]
Sent: Friday, July 17, 2015 6:39 PM
To: dev@cordova.apache.org
Subject: Re: Discuss Android plugin compatibility problem
So, it seems like mechanisms are already in place
Message-
From: Mefire O. [mailto:ommen...@microsoft.com]
Sent: Friday, July 17, 2015 6:39 PM
To: dev@cordova.apache.org
Subject: Re: Discuss Android plugin compatibility problem
So, it seems like mechanisms are already in place to enable us to do what
we wanna do here.
The actionable
Ideally Maven should handle all this shit, and it should be invisible. Our
plugin system should not handle Java dependencies or any other platform
dependencies, and we should work behind the scenes to make this work like
how Crosswalk works.
On Thu, Jul 16, 2015 at 10:18 AM Steven Gill
+1 on moving deps to gradle.
On Jul 16, 2015 9:37 AM, Carlos Santana csantan...@gmail.com wrote:
you mean the scripts in cordova-android right? then yes
+1 create jira bug, enhancements etc.. if doesn't get track it doesn't get
done
On Thu, Jul 16, 2015 at 12:26 PM Joe Bowser bows...@gmail.com
Would this be added to plugin.xml?
On Thu, Jul 16, 2015 at 10:09 AM, Mefire O. ommen...@microsoft.com wrote:
+1 on moving deps to gradle.
On Jul 16, 2015 9:37 AM, Carlos Santana csantan...@gmail.com wrote:
you mean the scripts in cordova-android right? then yes
+1 create jira bug,
Is there a bug created for this? It sounds like we should have the local
scripts handle dependency adding on Android.
On Thu, Jul 16, 2015 at 9:14 AM Carlos Santana csantan...@gmail.com wrote:
+1 gradle declared dependencies only, cli to warn users about plugins
having libraries that will
you mean the scripts in cordova-android right? then yes
+1 create jira bug, enhancements etc.. if doesn't get track it doesn't get
done
On Thu, Jul 16, 2015 at 12:26 PM Joe Bowser bows...@gmail.com wrote:
Is there a bug created for this? It sounds like we should have the local
scripts handle
+1 gradle declared dependencies only, cli to warn users about plugins
having libraries that will conflict, future is gradle no ANT I'm ok to
start deprecating ant going forward.
On Thu, Jul 16, 2015 at 11:27 AM Sergey Grebnov (Akvelon)
v-seg...@microsoft.com wrote:
Hi guys, I want to raise
Wait, yeah, plugin.xml does handle that. I was thinking config.xml. WTF?
On Thu, Jul 16, 2015 at 9:21 PM Carlos Santana csantan...@gmail.com wrote:
Steve plugin.xml already supports declaring gradle deps
On Thu, Jul 16, 2015 at 1:29 PM Joe Bowser bows...@gmail.com wrote:
Ideally Maven
Steve plugin.xml already supports declaring gradle deps
On Thu, Jul 16, 2015 at 1:29 PM Joe Bowser bows...@gmail.com wrote:
Ideally Maven should handle all this shit, and it should be invisible. Our
plugin system should not handle Java dependencies or any other platform
dependencies, and we
16 matches
Mail list logo
