Community
Participate
Working Groups
This is to track basic support for importing and working with projects using m2e. There is an existing open source project called m2e-android which provides this support for ADT. We should work with that project to provide support for Andmore, or work with them to bring the core support that doesn't require ADT specific items over to Andmore for maintenance. Regardless of how this is solved, we need integration with the android-maven-plugin.
We've raised a ticket for this: https://github.com/rgladwell/m2e-android/issues/294 Please subscribe to this (I've subscribed to this ticket). Are Andmore p2 repositories available?
(In reply to Ricardo Gladwell from comment #1) > We've raised a ticket for this: > > https://github.com/rgladwell/m2e-android/issues/294 > > Please subscribe to this (I've subscribed to this ticket). > > Are Andmore p2 repositories available? The closest we have at this point, is the following: https://hudson.eclipse.org/andmore/job/Andmore-Develop/lastSuccessfulBuild/artifact/andmore-core/site/target/repository/ I have some more build migration to do before I can start producing signed items. You can also clone the project, run a build, and get the p2 repository generated locally. Then it is just a matter of pointing tycho to use that local repository as part of the build. Hopefully soon I can get an official p2 repository for devs to start working with.
With m2e-android now working with Andmore. What other items do we need to support. AAR and a the new Android Studio directory structures being features that need to be added. For AAR support what functionality or extension points do we need to provide for m2e-android to make that project's life a bit easier.
I though we already supported Android Studio directory structures? Is there some part of the folder layout we don't support? There is an open ticket for AAR support: https://github.com/rgladwell/m2e-android/issues/177
The ADT plugins, do a really ugly hack to get some of the directory structures in place with the existing tooling. They put virtual links that point to different locations. The goal here is to make this more configurable in a bit more future proof. So that tooling can specify the locations for the RES, ASSET, LIB, and other folders. I know that Android Studio and Gradel now use src/main/ to store AndroidMainfest.xml, and the RES directory. Basically we need to be able to support this without the use of link hackery within Andmore. The same thing for generated source folders, those should be configurable, and have Andmore use what the tooling tells it to use (i.e use the appropriate generated-sources folder provided and configured by m2e-android or gradel). This ticket should also provide you with any additional items you need to enable or disable within andmore so that m2e-android can provided generated sources, and Andmore uses them when building instead of generating it's own folders, etc.
Moving to 0.5-M3
