Is this the same problem that (allegedly) can be fixed by using this plugin? https://github.com/dpa99c/cordova-android-support-gradle-release
2017-08-18 18:02 GMT+02:00 julio cesar sanchez <jcesarmob...@gmail.com>: > This problem is not only present on Play Services version, any other > library or framework, from Android (like support libraries) or any 3rd > party. > For 3rd party is less common, but for support libraries is very common to > have this kind of problem. > > I have had another idea that I think should be simpler, but will be a big > breaking change. > > What if we drop support for the framework tag in plugin xml and move the > functionality to config.xml? > > Plugin authors should use config-file tag to add the framework on the > config.xml, something like > <config-file target="config.xml" parent="/*"> > <framework src="com.android.support:support-v4:24.1.1+" /> > </config-file> > > > The problem is that any plugin using a framework will need an update, while > the other proposed approach will only need to update conflicting plugins. > > > And if the config.xml already includes a com.android.support:support-v4 > then ignore it. > > El 8 ago. 2017 3:03 p. m., "Audrey So" <a...@adobe.com.invalid> escribió: > >> Hi all! >> >> >> There is a proposal to offer an alternative solution for CB-13145: >> https://issues.apache.org/jira/browse/CB-13145. >> >> Please review the proposal below: >> >> https://github.com/cordova/cordova-discuss/pull/74/files >> >> >> We would appreciate any feedback, advice, comments, and questions you have >> on this proposal. Looking forward to hearing any thoughts. Thanks so much! >> >> >> Audrey >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
