On Wed, May 29, 2013 at 3:39 PM, Bruno Oliveira <bruno@abstractj.org> wrote:
Only for Android as Summers already mentioned.

yeah - I ment for JDK7 on all other things, besides Android :)

 

Matthias Wessendorf wrote:
> Honestly, I don't see a huge issue with JDK 7....
>
>
> On Wed, May 29, 2013 at 3:35 PM, Karel Piwko <kpiwko@redhat.com
> <mailto:kpiwko@redhat.com>> wrote:
>
>     Good to know. I haven't seen any enforcer plugin rule and compiler
>     plugin is set
>     to 1.6, so I though it is still on JDK6.
>
>     Karel
>
>
>       On Wed, 29 May 2013 15:27:48 +0200
>     Daniel Bevenius <daniel.bevenius@gmail.com
>     <mailto:daniel.bevenius@gmail.com>> wrote:
>
>      > Hi,
>      >
>      > SimplePush Server uses Netty 4 and now also vert.x
>     (2.0.0-beta4-SNAPSHOT)
>      > which both require Java 7. So it's not only PushEE anymore that
>     has this
>      > requirement.
>      >
>      > cheers,
>      >
>      > /Dan
>      >
>      >
>      > On 29 May 2013 15:11, Karel Piwko <kpiwko@redhat.com
>     <mailto:kpiwko@redhat.com>> wrote:
>      >
>      > > Hi,
>      > >
>      > > Most of the code is JDK6, except PushEE which requires JDK 6.
>     Android
>      > > requires
>      > > JDK 6 API as well, thanks Summers for pointing that out. The
>     only component
>      > > that requires JDK7 is PushEE afaict.
>      > >
>      > > So, even if JDK 6 is officially EOLed (at least Oracle's one),
>     I'd prefer
>      > > to
>      > > limit our code to JDK6 features. Does it make sense?
>      > >
>      > > I can setup animal sniffer plugin to enforce JDK API
>     conformance and
>      > > send PRs if you will - btw, do you guys already have a common
>     parent with
>      > > plugin
>      > > configuration?
>      > >
>      > > The other question is default runtime. Would you guys recommend
>     JDK7 or
>      > > JDK6?
>      > > I'm biased here to decide myself.
>      > >
>      > > Thanks,
>      > >
>      > > Karel
>      > >
>      > >
>      > > _______________________________________________
>      > > aerogear-dev mailing list
>      > > aerogear-dev@lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
>      > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>      > >
>
>     _______________________________________________
>     aerogear-dev mailing list
>     aerogear-dev@lists.jboss.org <mailto:aerogear-dev@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@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev@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