[aerogear-dev] [Android] Android project structure for final

[Kris Borchers]

Is this something that a lot of Android projects do? If it's not going to seem weird to Android developers to separate 4+ and 2.3 into separate projects I am +1 for it.

As for separating tests into their own project, that seems to make sense either way.

On Feb 28, 2013, at 6:07 PM, Summers Pittman <supittma at redhat.com> wrote:

> I would like to turn the Android maven project into three separate projects.
> 
> aerogear-android: The core library with everything you need to get going 
> on modern (4.0+) Android devices
> 
> aerogear-android-support: Library shims for older (Android 2.3) 
> devices.  This project will also require the android-support-library.
> 
> aerogear-android-tests: This will house all of the Aerogear tests for 
> Android.  Currently we use Robolectric for testing, but it doesn't 
> accurately support some things (Android threading comes to mind) and 
> doesn't support others at all (Loaders).  A solution is to use a project 
> which runs the tests on a emulator/device.  This can also be the 
> integration test project which we want to make anyway.
> 
> wdyt?
> 
> Summers
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev