<div dir="ltr">A few questions:<div><br></div><div>* The best is to "suck in" the 'latest' JS dependency via npm (or similar, or by hand), right ? </div><div><br></div><div>* If yes... doesn't it generally make sense to release the Cordova bits a bit AFTER its core dependencies ? On iOS we did the same (yesterday I moved the Crypto to CocoaPods, today Christos is sucking that in, via CocoaPods (on aerogear-ios)</div>
<div><br></div><div><br></div><div>-Matthias</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 19, 2013 at 10:59 AM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Tue, Nov 19, 2013 at 10:21 AM, Erik Jan de Wit <span dir="ltr"><<a href="mailto:edewit@redhat.com" target="_blank">edewit@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word">Hi,<div><br></div><div>
Last tuesday the PR for the new javascript crypto api landed, because I developed the crypto cordova plugin based on the 'old' api there is now a discrepancy between the 'current' javascript crypto api and the cordova one. We could change that this week as there aren't that many people that use the crypto cordova plugin, but we have frozen so what is the point of a freeze when we change things regardless?</div>
<div><br></div><div>Anyway I think we could still change this what do you think?</div></div></blockquote><div><br></div></div><div>yes, I think updating the Cordova bits makes sense.</div><div><br></div><div>Quote from yesterdays team meeting:</div>
<div><quote></div><div>15:22:50 <qmx> #info qmx proposes to freeze this friday (as an exception to android), freeze this friday, release next week, announce after the holiday"</div><div></quote></div>
<div><br></div><div>So the freeze is this week, and IMO that's perfectly fine to update it.<br></div><div><br></div><div><br></div><div>That said, but I think the only question I really have is why this update to reflect the 'new' API was not addressed already last week.</div>
<div><br></div><div>Greetings,</div><div>Matthias</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
<div style="word-wrap:break-word"><div><br></div><div>Cheers,</div><div><span style="white-space:pre-wrap"> </span>Erik Jan</div><div><br></div><div>p.s.</div><div>have a look at the differences:</div>
<div><br></div><div>current javascript api</div><div><a href="https://github.com/aerogear/aerogear-js/blob/master/tests/unit/crypto/aerogear.crypto.js" target="_blank">https://github.com/aerogear/aerogear-js/blob/master/tests/unit/crypto/aerogear.crypto.js</a></div>
<div><br></div><div>current cordova api</div><div><a href="https://github.com/edewit/aerogear.org/blob/f2fe8a48b2f9d9c581e62292abeaf788c0c4338e/docs/guides/aerogear-cordova/AerogearCordovaCrypto.asciidoc" target="_blank">https://github.com/edewit/aerogear.org/blob/f2fe8a48b2f9d9c581e62292abeaf788c0c4338e/docs/guides/aerogear-cordova/AerogearCordovaCrypto.asciidoc</a></div>
</div><br></div><div class="im">_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></div></blockquote></div><span class="HOEnZb"><font color="#888888"><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>
</font></span></div></div>
</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>