>IMO the goal is to create a sync client lib, similar to iOS 
Sorry, I was actually thinking about the server. The clients (xmpp and Java) could be moved out into separate projects.

The servers are currently integrated, so there is a dependency to xmpp there which might still cause people wanting to try out the server having to update Android on their system. We could extract this integrated server into a separate module for those how want to try it out.



On 16 January 2015 at 15:10, Matthias Wessendorf <matzew@apache.org> wrote:


On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius <daniel.bevenius@gmail.com> wrote:
Yeah, something needs to be done about this. Either moving it out, or having it only enabled with a profile (Summers mentioned this yesterday). 

-1 on profile.

IMO the goal is to create a sync client lib, similar to iOS (which is also on its own repo), so that should not be included on the java server. Eventually we should move out the JS bits as well 
 


On 16 January 2015 at 15:01, Matthias Wessendorf <matzew@apache.org> wrote:
Hi,

should we move the Android client-xmpp to its own repo? Right now, when building the server (and with an incomplete Android setup (aka new, clean repo)) you have to comment it out in order to build the server for running the JS demo.

IMO it would be nice if that gets moved out to something like "aerogear-android-xmpp-client".


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev