Forgot to reply to the mailing list.
    -------- Forwarded Message
      --------
      
      
      
      
      Hey Jonathan, thanks for touching base.   I'm actually not to
        sure, but I would say at one point it was the go to method with
        the m2e-android plugin.   I know that several places probably
        still use maven as their main piece, especially if using
        Eclipse.
      Long term, I'd love to get better gradle support, using the
        buildship project and Andmore, but as most of the committers
        here are volunteers and we try to keep it going the best we can
        in our spare time.   Your best bet would be to reach out to the
        maintainers, of the android-maven-plugin.  They might have more
        concrete numbers.   I know the m2e-android plugin currently
        isn't being maintained unfortunately.
      https://github.com/simpligility/android-maven-plugin
      Please do keep us in the loop on what you find out.
      Glad to hear that Robolectric is moving away from the resource
        emulation, that was always one of the slower and resource
        intensive parts for the framework.
      Dave
      
      
      On 10/16/2017 3:15 PM, Jonathan
        Gerrish wrote:
      
      
        Hey guys,
          
          
          Robolectric admin here :-)
          
          
          Just to bring you up to date with what is happening in
            Robolectric land in case it influences any design decisions
            in your fix. We've moved configuration of manifest,
            resources and assets location to a build system API, see
            here for details:- 
http://robolectric.org/build-system-integration/
          
           This is currently supported in Android Studio / Gradle
            3.0 and we have Bazel supporting soon too.
          
          
          Right now we still deal with raw resources (which should
            be merged by the build system ideally) but later this year
            we plan on supporting binary resources and deprecating
            support for raw resources. This is going to give a more
            actuate simulation of Android since we're no longer
            concerned with emulating resource merging or aapt behavior.
            Robolectric itself will actually be faster although that
            work is pushed into the build system.
          
          
          Do you have any idea what the user base is of folks still
            running Eclipse + Maven for Android Dev? We'd ideally not
            like to break people with our changes.
          
          
          Let me know if this is something you are interested in
            supporting and I'll be happy to help.
          
          
          Jonathan
          
          
          
          
          
          
          
          
        
        
        
        _______________________________________________
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