[aerogear-dev] [aerogear-android-todo]

[Matthias Wessendorf]

>> 2) Why aren't we following the maven project layout, as suggested by the archetype we are using?
>
> We're following a simple convention for the Android maven plugin
> (http://code.google.com/p/maven-android-plugin/).  You can see a similar
> example at
> https://github.com/jayway/maven-android-plugin-samples/tree/master/helloflashlight.
>  The idea is that it's an Android project first and a maven project second.


I think using this format is right...
http://www.vogella.com/articles/AndroidBuildMaven/article.html

>> 3) Why the API and the example app are intermixed?
>>       - Ideally these should be separate repositories, like the iOS version
>
> Definitely!  This is mentioned in TODO comments in the code.  I wanted
> to get the prototype up quickly to link it to
> https://issues.jboss.org/browse/AEROGEAR-353, and didn't have time to
> both merge in the new UI and split out the API jar.  Next on my list.

yeah +1 on separating the bits

-M

>
> --Glen
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf