Well, you also have to look at what is being used out in the field
as well.
1. Gradle is top priority as that is what the AOSP is using and
what Android Studio is using. However....
2. In the field, both Gradle and Maven are being used. In fact the
current client I have is a Maven shop, so they went with Maven for
their Android builds as well. Maven supports AARs already and we
can do similar things that we do with gradle, allow Maven to build
artifacts when necessary, we just have to make the new build system
flexible enough to handle it on the Andmore side.
3. IntelliJ Community edition... supports both Gradle and Maven.
Enterprise customers are using both, and if we can support both
going forward we should. Ricardo did a lot of work on M2E-Android,
and I'd personally hate to see it die away, but I also know
resources are constrained on the project.
I actually wanted to bring M2E-Android over to Andmore when I
brought the rest of ADT it would have been an easier way to get the
configuration plugin out to more people.
Anyways, it is up to Ricardo if he wants to contribute the plugin or
not, I've got a clone of the repository already, it'll just be much
easier to bring it over sooner rather than later if any IP issues or
concerns arise.
Dave
On 2/3/16 12:34 PM, Doug Schaefer
wrote:
It's pretty clear the future of Android is Gradle.
I really appreciate your efforts to get m2e working for Android
projects. Unless we have someone contributing to Andmore who
wants to take it further, I don't think it's worth that effort.
But that's just my thoughts.
Doug.
_______________________________________________
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
|