Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
Andmore - Eclipse Android Tooling
Some of the components in Andmore were originally written for the DSDP/TmL and DSDP/MTJ projects. Some of the components were written for the Tools/Sequoyah project. Some of the components were authored by Motorola Mobility and contributed to the Android Open Source Project in 2012. The ADT Eclipse plugins are from the Android Open Source Project.
The Andmore project has Google's blessing to fork the code for ADT and the former Motorola “MOTODEV” plugins as part of this project.
The scope of the project is to develop and maintain technologies for creating Android applications. This ranges from creating new Eclipse components and updating existing components that support Android development to a downloadable package that can be used for new developers and students. The project aims to maintain the parity with current development trends in phones, tablets, smart watches, smart TVs, embedded Android, and future directions for Android development.
The Andmore EPP package will have the core IDE, JDT, CDT, the Android Eclipse plugins, Maven, Gradle, Gerrit, Git, and the relevant functionality from the former MOTODEV tools. The purpose of this package is is to provide an environment that is easily installed and configured for the least amount of confusion and the quickest time to development. Download the official Android SDK and Proteus, that's all you need.
The project will not focus on teaching new developers how to write Android applications.
The purpose of Andmore is to provide Android Eclipse tooling without having to go through multiple steps.
The technology development will involve integrating and refactoring the Google ADT plugins as necessary to work with the project. Similarly, the former MOTODEV plugins have many useful components that can be integrated into the project. Once these are integrated, new components may be added.
There have been several attempts at this in the past, as EPP projects and commercial endeavors with varied success. The aim of this project is to integrate several open source projects that have been abandoned or will soon cease to be supported and combine them with the ongoing needs of Android developers.
JDT for Android Java applications.
CDT for C/C++ shared libraries.
Gradle builds via the Spring Gradle Tools for Eclipse Project.
Maven Build support via the M2E-Android Eclipse Plugin.
Ant support via the built in Eclipse support for ANT.
A fork of Google's ADT (Android Development Tools) plugins for Eclipse. These will be maintained and updated separately from Google's code line, which is anticipated will not be actively improved as Google moves toward Android Studio.
The former MOTODEV Studio Plugins (now part of the Android Open Source Project) upgraded to work with the latest ADT.
A p2 repository and product build using tycho.
Mylyn Reviews for Gerrit Review integration.
EGit for source code management.
GitHub Plugin from EGit for better collaboration with GitHub projects.
In addition to components, Andmore will produce an EPP package. There was previously an "Eclipse for Mobile Developers" package in 2012 for Juno that was shipped for 1 year without the ADT plugins. That package was the 4th most popular EPP package, after CDT, and shipped just over 1 million total downloads. There is clearly an audience for this type of package.
Nearly all the technologies are built on Eclipse or contain other Eclipse projects.
Professional embedded and enterprise developers are comfortable with Eclipse. Educational institutions appreciate both the “libre” and “gratis” aspects of open source projects and guide students toward Eclipse. The Andmore project will fulfill the needs of both new and professional developers who depend on Eclipse for their daily development needs.
GitHub repository kingargyle/proteus that was built by forking Google ADT and the MOTODEV plugins from AOSP.
Some work to remove MotoDev specific items like links to non existent tooling web sites.
Some renamings for perspectives from MotoDev to Proteus.
Updates to the former MOTODEV source code to compile and work with the latest ADT 23 plugins.
- Migration of the current snapshots of the Android Development Tools to Andmore as a separate project. Work has started to get these to compile and have all dependencies included. AOSP external libraries should be converted to Orbit or P2 standalone repository. Some work started by Google in the AOSP to this effect but has since been reverted.
The Google ADT plugins are EPL 1.0, the Moto Dev Studio plugins are Apache License v2.
The Motorola MOTODEV plugins were originally proprietary, but were released to the Android Open Source Project on August 15  and August 21  by Eric Cloninger of Motorola Mobility, at which point, they became Apache v2. These commits were reviewed and accepted by Xavier Ducrohet of Google.
No GPL and no commercial licenses.
Andmore will deliver an EPP package off-train, prior to the next major release. Plan is to refactor and stabilize the components and deliver on the release train.
Strong interest from corporate sponsors and individuals who wish to continue seeing support for Android application and library development with Eclipse. The initial leadership of the project are experienced Eclipse leaders who also have a vested interest in Android development and an ability to create communities.
The initial work will be to stabilize the code, create an EPP and an update site. Ongoing development will be to support the different build and test automation environments, Java and C/C++ build and debugging to connected and remote processor targets, including emulators.
Future work will involve refactoring classes and renaming to allow future development to be more efficient.