Hi,
I work with Android development for Sony Mobile and I'm getting dirty looks from my colleges for sticking with Eclipse. So I thought that the best way to remedy that is to try to get involved with you guys.
I started to look in to supporting Gradle project structures in Eclipse.
I have two commits so far (though, they are by no means ready for a pull request)
The first commit is for assuming that a gradle project is a possible Android project, and therefore it should be listed in the available projects when creating projects from existing sources.
The second commit is for allowing the AndroidManifest.xml to be located anywhere within the project.
Are you are interested in a contribution for this ticket, or are you already working on it?
This is my thoughts so far:
- I'm currently adding the AndroidManifest.xml path as a value in project.properties. (for example manifest.file=src/main/AndroidManifest.xml). I don't actually like this, since I'm using a property key that I came up with my self. We should probably persist properties like this within .settings instead. Is there an existing .settings property for android natures that can be used to persist the path of AndroidManifest.xml?
- Currently I'm performing a recursive search within the project to locate the AndroidManifest.xml and I'll just pick the first I encounter. This could be a problem if there are multiple AndroidManifest.xml files in the project (for example bin/build directories might have AndroidManifest.xml copies). Is it an ok solution to add a UI element to the wizard to let the user select what AndroidManifest.xml to use, so there is a chance to edit the path? An alternative could be to parse build.gradle to find the path, but I'm uncertain of if it is ok to start utilizing the gradle files at this stage.
Do you have any other thoughts on how this should be implemented?
