<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy <span dir="ltr">&lt;<a href="mailto:mmurphy@redhat.com" target="_blank">mmurphy@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Hi Matthias,</div><div>That would do, however I was think more of this way:</div><div>   <a href="https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477" target="_blank">https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca77f6f32d7f0925c19bb1477</a></div><div>to avoid the risk of pointing at a changing repo.</div></div></blockquote><div><br></div><div>sounds good!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>Can use the one you mentioned, or a combination of them?</div><div><br></div><div>I can certainly do the PR.</div></div></blockquote><div><br></div><div>that would be awesome</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div><br></div><div><div>Best Regards,</div><div>Martin Murphy.</div><div><div class="h5"><div><br></div><div><br></div><blockquote type="cite"><div>On 14 Jul 2015, at 11:59, Matthias Wessendorf &lt;<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>&gt; wrote:</div><br><div><div dir="ltr">Hi Martin,<div><br></div><div>so - it&#39;s basically porting this commit over to the 1.0x branch:</div><div><a href="https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3" target="_blank">https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a0123d092a1d2231911a7c2c3</a></div><div><br></div><div>right ?</div><div><br></div><div>Mind sending a PR ? <br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy <span dir="ltr">&lt;<a href="mailto:mmurphy@redhat.com" target="_blank">mmurphy@redhat.com</a>&gt;</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">Hi folks,<br>
we have a Cordova application that’s using Codrova 3.3.<br>
The application uses org.jboss.aerogear.cordova.push 1.0.2<br>
<br>
When preparing for an android build, there seems to be an problem installing one of the dependencies of the aurora plugin<br>
An id has been updated: com.vladstirbu.cordova.promise, now has a different id: es6-promise-plugin.<br>
<br>
The newer plugin 2.0.2 is in the npm registry.<br>
<br>
Is it possible to add a fix and deploy to the old cordova registry so that it’s usable in 3.x<br>
Is the newer plugin 2.0.2 backward compatible with 1.0.2<br>
<br>
I understand that the ideal approach would be to use a more up-to-date version of Cordova, and use the latest aurora plugin, however it will take some time before I will be able to do that.<br>
I’m open to other suggestions also.<br>
<br>
Best Regards,<br>
Martin Murphy.<br>
<br>
<br>
<br>
_______________________________________________<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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>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></div></div>
_______________________________________________<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></div></blockquote></div></div></div><br></div><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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">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></div>