Re: Proof-of-Concept: Studio Project Structure Cleanup

[Joe Bowser <bo...@gmail.com>]

Hey

After the eslint merge, I redid the PR, so here's the new branch for the
StudioProjectCleanup.  Can more people look at it, I'll be working on some
refactors on here, but AFAIK, there's no good reason to not merge this into
master and get ready to start ramping up Cordova-Android 7.0.0

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

Any thoughts?

Joe

On Fri, Jun 9, 2017 at 3:27 PM, Joe Bowser <bo...@gmail.com> wrote:

> Hey
>
> I know that I've talked about this before, but I think that with the
> adoption of Kolton as a supported Android development language and with
> recent Gradle changes on the CLI, it's time to migrate our generated
> Android project structure to something a bit more modern so that we can
> support modern Android development.  That being said, we need to make sure
> that existing projects can just keep the same code that has worked for them
> working, so here's the branch that I've been working on.  All the plugin
> installation works, but I need help with the upgrade scripts working for
> both structures:
>
> https://github.com/infil00p/cordova-android/tree/StudioProjectCleanup
>
> Here's the PR: (It's HUGE)
> https://github.com/apache/cordova-android/pull/384
>
> The downside of all of this is that we've now forever adopted
> project.properties to keep track of all the Android libraries that the
> plugins use, but that's the price we have to pay currently if we want to be
> able to have the plugins install gradle dependencies, otherwise managing
> the dependencies would be a nightmare.  (You'd think Gradle could do this
> on its own, but nope)
>
> So, if anyone hates Java and wants to write Kolton, or if people just want
> their Cordova-Android projects to look like a regular Android project, this
> PR may be right for you.  Feel free to check it out.  This would be a
> Cordova-Android 7.0 change.
>
> BTW: This is not directly related to Android O, but it may help.
>
> Joe
>