On Fri, Jan 16, 2015 at 3:30 PM, Summers Pittman <supittma(a)redhat.com>
wrote:
On 01/16/2015 09:20 AM, Daniel Bevenius wrote:
>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.
The server xmpp is only reliant on some xmpp library, not on Google stuff
and def not android stuff.
Right, that's not an issue - we can keep that in there - at the end, if (or
when) the server will support XMPP, this lib/dependency is needed there
anyways
I'm fine with creating aas and moving the sync stuff into it.
On 16 January 2015 at 15:10, Matthias Wessendorf <matzew(a)apache.org>
wrote:
>
>
> On Fri, Jan 16, 2015 at 3:04 PM, Daniel Bevenius <
> daniel.bevenius(a)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(a)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".
>>>
>>> Any thoughts?
>>>
>>> --
>>> Matthias Wessendorf
>>>
>>> blog:
http://matthiaswessendorf.wordpress.com/
>>> sessions:
http://www.slideshare.net/mwessendorf
>>> twitter:
http://twitter.com/mwessendorf
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)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
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing
listaerogear-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)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