cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Parashuram N <>
Subject RE: [Android] Need a solution to config.xml and AndroidManifest.xml feature requests
Date Mon, 21 Mar 2016 17:40:53 GMT
Given that we are now using Gradle for builds, could these simply be gradle sub-projects that
define an AndroidManifest.xml, that gets merged during Android build ? One way could be to
support specifying "sub-projects" in config.xml, and these changes get picked up. Would it
work for all cases ? 

-----Original Message-----
From: Joe Bowser [] 
Sent: Monday, March 21, 2016 10:07 AM
To: dev <>
Subject: [Android] Need a solution to config.xml and AndroidManifest.xml feature requests


So, if you've been paying attention to the JIRA, we've been getting slammed with a ton of
feature requests/bugs regarding the Android Manifest where people want to add a 1:1 mapping
between the two XML files.

The thing is that it's getting out of control, and we need to find a better solution to this
problem.  I'm not sure what a better solution to this is, but if you want to see some of the
issues that are related to this, here's a small list:

All of these are either indirectly or directly related to the AndroidManifest, and it's clear
that if we just allowed people to edit an AndroidManifest, or at least allow portions of it
to be immutable, we would be better off.  Obviously, plugins that install third-party activities
and content providers would have to edit the manifest, but I think that things are getting
out of hand with the things that people want to control from config.xml.

What do people think? Does anyone have a good solution to this problem? Are we really abstracting
anything out by duplicating the same config in our own config.xml?
View raw message