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 [mailto:[email protected]] Sent: Monday, March 21, 2016 10:07 AM To: dev <[email protected]> Subject: [Android] Need a solution to config.xml and AndroidManifest.xml feature requests Hey 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: https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10894&data=01%7c01%7cpanarasi%40microsoft.com%7c4430fe17c9d94a96f19608d351ab4028%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=f3qD84Rx%2bc%2bDzryeeXDCIX%2bhrCk%2boM%2f26%2fT5OAy9RMA%3d https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10917&data=01%7c01%7cpanarasi%40microsoft.com%7c4430fe17c9d94a96f19608d351ab4028%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=I1ycCL25rWlN4uTU%2fPXFBkv1PYXrDeX6dF6%2fMzyNSbE%3d https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-8159&data=01%7c01%7cpanarasi%40microsoft.com%7c4430fe17c9d94a96f19608d351ab4028%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=HS3ZRL%2fxY%2fJWZo5eMQPGFO6BS2W03z13va8NV7sZpjo%3d https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-10755&data=01%7c01%7cpanarasi%40microsoft.com%7c4430fe17c9d94a96f19608d351ab4028%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=PeZms4TWbWqHInf%2fnYYbL3e5o9aB3Ijcl8fQxoUmsgU%3d https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissues.apache.org%2fjira%2fbrowse%2fCB-8976&data=01%7c01%7cpanarasi%40microsoft.com%7c4430fe17c9d94a96f19608d351ab4028%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=4VoysIEst8o7k3kvkyYu9MeBDF8VZ3q7aG6oLcoCN2w%3d 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?
