<div dir="ltr">However, I can see if PushEE really uses much of JDK 7.<div><br></div><div style>but the vert.x wrapper, for SimplePush, must relay on JDK7, since.... that's target of vert.x</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, May 30, 2013 at 8:37 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">what's wrong when some use JDK7 (e.g. SimplePush/PushEE) and some use JDK6 (e.g. Android, OTP) ?</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 30, 2013 at 8:31 AM, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I still don't get it.<br>
<br>
How am I supposed to run code compiled with -target 1.7 on JDK6?<br>
This will throw UnsupportedClassVersionError.<br>
<br>
The only way how to test on both JDK6 and JDK7 is to have code compiled against<br>
target 1.6. And this would require source 1.6. So, if Vert.x (1.3.1 and<br>
2.0.0.beta3 targets JDK7) and Netty (4.0.0.CR3 targets JDK6) are compiled<br>
targeting JDK7, testing on JDK6 is out of scope.<br>
<span><font color="#888888"><br>
Karel<br>
</font></span><div><div><br>
On Wed, 29 May 2013 10:43:32 -0300<br>
Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>> wrote:<br>
<br>
> Security has dependency with other projects, so just in case I'm testing<br>
> it against both<br>
> <a href="https://github.com/aerogear/aerogear-security-picketlink/blob/master/.travis.yml#L3" target="_blank">https://github.com/aerogear/aerogear-security-picketlink/blob/master/.travis.yml#L3</a><br>
><br>
> Also OTP must support Android and the backend, testing both for the same<br>
> reason.<br>
><br>
> Matthias Wessendorf wrote:<br>
> ><br>
> ><br>
> ><br>
> > On Wed, May 29, 2013 at 3:39 PM, Bruno Oliveira <<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a><br>
> > <mailto:<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>>> wrote:<br>
> ><br>
> > Only for Android as Summers already mentioned.<br>
> ><br>
> ><br>
> > yeah - I ment for JDK7 on all other things, besides Android :)<br>
> ><br>
> ><br>
> > Matthias Wessendorf wrote:<br>
> > > Honestly, I don't see a huge issue with JDK 7....<br>
> > ><br>
> > ><br>
> > > On Wed, May 29, 2013 at 3:35 PM, Karel Piwko <<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a><br>
> > <mailto:<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>><br>
> > > <mailto:<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a> <mailto:<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>>>> wrote:<br>
> > ><br>
> > > Good to know. I haven't seen any enforcer plugin rule and<br>
> > compiler<br>
> > > plugin is set<br>
> > > to 1.6, so I though it is still on JDK6.<br>
> > ><br>
> > > Karel<br>
> > ><br>
> > ><br>
> > > On Wed, 29 May 2013 15:27:48 +0200<br>
> > > Daniel Bevenius <<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a><br>
> > <mailto:<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>><br>
> > > <mailto:<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a><br>
> > <mailto:<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>>>> wrote:<br>
> > ><br>
> > > > Hi,<br>
> > > ><br>
> > > > SimplePush Server uses Netty 4 and now also vert.x<br>
> > > (2.0.0-beta4-SNAPSHOT)<br>
> > > > which both require Java 7. So it's not only PushEE anymore that<br>
> > > has this<br>
> > > > requirement.<br>
> > > ><br>
> > > > cheers,<br>
> > > ><br>
> > > > /Dan<br>
> > > ><br>
> > > ><br>
> > > > On 29 May 2013 15:11, Karel Piwko <<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a><br>
> > <mailto:<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>><br>
> > > <mailto:<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a> <mailto:<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>>>> wrote:<br>
> > > ><br>
> > > > > Hi,<br>
> > > > ><br>
> > > > > Most of the code is JDK6, except PushEE which requires JDK 6.<br>
> > > Android<br>
> > > > > requires<br>
> > > > > JDK 6 API as well, thanks Summers for pointing that out. The<br>
> > > only component<br>
> > > > > that requires JDK7 is PushEE afaict.<br>
> > > > ><br>
> > > > > So, even if JDK 6 is officially EOLed (at least Oracle's one),<br>
> > > I'd prefer<br>
> > > > > to<br>
> > > > > limit our code to JDK6 features. Does it make sense?<br>
> > > > ><br>
> > > > > I can setup animal sniffer plugin to enforce JDK API<br>
> > > conformance and<br>
> > > > > send PRs if you will - btw, do you guys already have a common<br>
> > > parent with<br>
> > > > > plugin<br>
> > > > > configuration?<br>
> > > > ><br>
> > > > > The other question is default runtime. Would you guys recommend<br>
> > > JDK7 or<br>
> > > > > JDK6?<br>
> > > > > I'm biased here to decide myself.<br>
> > > > ><br>
> > > > > Thanks,<br>
> > > > ><br>
> > > > > Karel<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>
> > <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>><br>
> > <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> > <mailto:<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>
> > > > ><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>
> > <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>><br>
> > <mailto:<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
> > <mailto:<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>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > --<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><br>
> > ><br>
> > > _______________________________________________<br>
> > > aerogear-dev mailing list<br>
> > > <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a> <mailto:<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>
> > _______________________________________________<br>
> > aerogear-dev mailing list<br>
> > <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a> <mailto:<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>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<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><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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</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>
</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>