Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [andmore-dev] Support Android Studio Project layout
Here is the ticket for supporting Android Studio Project layouts in Eclipse.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=463610

We also have a ticket open for supporting Gradle with Buildship.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=459572

That depends on a couple of items from the Buildship developers to allow us to hook into the configuration of the projects so that we can include the necessary natures.

Also what is needed is AAR support.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=459569

All of these could use help in this area, so any contributions would be appreciated.  

Dave


On 8/11/15 4:55 PM, Martin Wallgren wrote:
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:
  1.   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?
  2.  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?

Martin


_______________________________________________
andmore-dev mailing list
andmore-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/andmore-dev

Back to the top