<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 4, 2014 at 9:11 AM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello iOS folks<br>
<br>
I’ve started looking at sync part, I’ve created a separate repo [1]. For now, this lib is dependant on iOS-core. does is worth having it separate for folks that what to use core without sync?<br></blockquote><div><br></div>
<div>yes</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Same question applies for encrypted store. Right now encrypted store are part of iOS-core. do we want to separate it for people who want core without encrypted store ?<br></blockquote><div><br></div><div>I do like the idea of separation</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
what about people who all it all, encrypted store+sync, we’ll have to manage correctly transitive dependencies.<br></blockquote><div><br></div><div>could we bundle something like an 'AeroGear-All-You-Can-Eat-iOS' (similar like something you can do w/ the maven-shade-plugin?). Adding Andrea, perhaps he has an idea on that</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
wdty?<br>
<br>
++<br>
Corinne<br>
[1] <a href="https://github.com/corinnekrych/aerogear-sync-ios" target="_blank">https://github.com/corinnekrych/aerogear-sync-ios</a><br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>