On Wed, Oct 22, 2014 at 12:38 PM, Matthias Wessendorf
<matzew(a)apache.org>
wrote:
> long term, on master, exclusively jsk8
but :-) initial steps would be to make it also Java8 compatible. Once that
is there, we will see how to move on.
I think in the past qmx has expressed interested in looking at JDK8, as he
already looked into the doclet issue a bit
Agree with initial steps. As for exclusively jdk8 - it would make more
sense to keep jdk7 if still supported by WF to me. So, if WF drops JDK7,
it's probably the right time to drop it as well in UPS but I don't see
any reason why to artificially limit users in runtime options.
-M
>
>
> On Wednesday, October 22, 2014, Karel Piwko <kpiwko(a)redhat.com> wrote:
>
>> Just a clarification, you mean making it *also* Java8 compatible, not
>> exclusively Java8, right?
>>
>> On Wed, 2014-10-22 at 10:35 +0200, Matthias Wessendorf wrote:
>> > On Wed, Oct 22, 2014 at 10:33 AM, Karel Piwko <kpiwko(a)redhat.com>
>> wrote:
>> >
>> > > If master is WF only, that should work.
>> > >
>> >
>> > yes, see original email :-)
>> >
>> >
>> > >
>> > > If you guys keep EAP there, you'd need to target 1.6 and also not
to
>> use
>> > > 1.8 for the runtime, see
https://access.redhat.com/articles/111663
>> for
>> > > EAP supported configurations.
>> > >
>> > > Karel
>> > >
>> > > On Wed, 2014-10-22 at 08:44 +0200, Matthias Wessendorf wrote:
>> > > > While at it :), as a follow-up thought on that, I am wondering
if,
>> on
>> > > > MASTER, we should look into making it Java8?
>> > > >
>> > > > -Matthias
>> > > >
>> > > > On Wed, Oct 22, 2014 at 8:43 AM, Matthias Wessendorf <
>> matzew(a)apache.org>
>> > > > wrote:
>> > > >
>> > > > > Hello,
>> > > > >
>> > > > > as said in the other email thread earlier this week ([1])
there
>> is a
>> > > bug
>> > > > > in the last JBoss AS 7.1 release (see [2]), that basically
means
>> the
>> > > server
>> > > > > works properly only on EAP6.x and WildFly.
>> > > > >
>> > > > > Because of that, I am wondering about removing the -as7
module
>> (see
>> > > [3]),
>> > > > > on our MASTER branch. For the 1.0.x branch, I'd like to
keep it,
>> for
>> > > EAP
>> > > > > usage reasons.
>> > > > >
>> > > > > What do you guys think?
>> > > > >
>> > > > > -Matthias
>> > > > >
>> > > > > [1]
>> > >
>>
http://lists.jboss.org/pipermail/aerogear-dev/2014-October/009435.html
>> > > > > [2]
https://issues.jboss.org/browse/AS7-4694
>> > > > > [3]
>> > > > >
>> > >
>>
https://github.com/aerogear/aerogear-unifiedpush-server/tree/master/serve...
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Matthias Wessendorf
>> > > > >
>> > > > > blog:
http://matthiaswessendorf.wordpress.com/
>> > > > > sessions:
http://www.slideshare.net/mwessendorf
>> > > > > twitter:
http://twitter.com/mwessendorf
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > _______________________________________________
>> > > > aerogear-dev mailing list
>> > > > aerogear-dev(a)lists.jboss.org
>> > > >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> > >
>> > > _______________________________________________
>> > > aerogear-dev mailing list
>> > > aerogear-dev(a)lists.jboss.org
>> > >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>> > >
>> >
>> >
>> >
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev(a)lists.jboss.org
>> >
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> --
> Sent from Gmail Mobile
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev