Bug 459572 - Support Gradle and the Buildship project and Android Gradle Plugin
Summary: Support Gradle and the Buildship project and Android Gradle Plugin
Status: ASSIGNED
Alias: None
Product: andmore
Classification: Tools
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: David Carver CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on: 463610
Blocks:
  Show dependency tree
 
Reported: 2015-02-10 11:16 EST by David Carver CLA
Modified: 2019-08-06 05:12 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Carver CLA 2015-02-10 11:16:03 EST 
Andmore needs to support builds that use Gradle.  This means we need to be able to import projects, handle build varients, and work with the Android Gradle Plugin to consume artifacts it produces.

This like the M2E integration needs to provide a seamless integration and provide the full lifecycle of activities.
Comment 1 David Carver CLA 2019-03-21 13:01:29 EDT 
Note that this looks like it might be possible now with Buildship 3.0.   They have added a Gradle Configuration extension point that will allow better possible support and to provide similar level of support that the Maven plugin has currently.

By turning most things over the Gradle we can possibly eliminate some of the tooling dependency issues we run into and not have to update versions all the time.

This will need to be a proof of concept implementation, but I'm putting this back on my radar.

An example of using the Configurator can be seen for the WtpConfigurator.

https://github.com/eclipse/buildship/blob/master/org.eclipse.buildship.core/src/main/java/org/eclipse/buildship/core/internal/workspace/WtpConfigurator.java