You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Ulrich Stärk <ul...@spielviel.de> on 2014/05/01 18:38:03 UTC
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Historically I have been a strong opponent to Java version upgrades for Tapestry because IMO the
disadvantages outweighed the advantages by far.
Now that we have lambda expressions, default methods, Nashorn and many other useful features I'm
leaning towards making a radical break and switch to Java 8.
We should have a formal vote for such a radical change and a discussion firstin order to gather
comments and opinions from the community.
Uli
On 2014-04-30 12:57, Jochen Kemnade wrote:
> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
>
> Which is much harder than I thought it was. I managed to find old rt.jar and jce.jar files and to
> make Gradle use them.
> Now I'm getting compile errors, e.g. in VirtualResource:88, MacOutputStream:45 and others. Mostly,
> it's Java 6 methods being used.
> First of all, do we still want to stick with Java 5 now that Java 8 is out and even Java 6 is EOL?
> Second, I wonder why it builds in Jenkins. What JDK is used there?
>
> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Jochen Kemnade <ke...@gmail.com>.
Am 01.05.2014 18:38, schrieb Ulrich Stärk:
> Now that we have lambda expressions, default methods, Nashorn and many other useful features I'm
> leaning towards making a radical break and switch to Java 8.
I second that. The changes in Java 6 and 7 wouldn't have justified the
switch in my opinion. But lambdas and Nashorn are definitely something
we would benefit from.
I also thought of releasing 5.5 based on Java 8 short after 5.4. I
actually like the idea but I fear that what was supposed to be "short
after" will eventually become another year or two.
But I'm definitely in favor of stepping away from 1.5, especially
because nobody seems to use a Java 1.5 compiler anymore and some of us
(*cough*) might even push changes that would break the build on a JDK5.
That last issue makes me think that it would be best to switch to Java 6
at least.
Jochen
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Jochen Kemnade <jo...@eddyson.de>.
Well then, since Uli had some reservations wrt. updading to Java 6, we
probably do need a vote. I'll start one in a new thread.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Howard Lewis Ship <hl...@gmail.com>.
I'm with Kalle as well, 1.6 is more than reasonable, and maybe 1.8 for 5.5
(which I really hope will be very quick, just clearing out deprecated code
and upgrading to JDK 1.7 or 1.8).
On Wed, May 14, 2014 at 7:27 AM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Fri, 02 May 2014 04:45:42 -0300, Ulrich Stärk <ul...@spielviel.de> wrote:
>
> Do you expect any problems if we just switched to Java 8/Servlet 3.1
>> without modifying anything else?
>>
>
> Yep. Lots of people and companies that won't or can't upgrade to a Java
> version which was just released, at least not in the near future. Not to
> mention that Java 8-only features will be only actually known and used by
> most people in the not near future. Unless we start using Java 8-only
> features in Tapestry, there's no reason IMHO to make such a long jump. The
> Tapestry image still has some problems with radical changes.
>
> I agree with Kalle: "A common sense approach would be to require 1.6 for
> T5.4 and then require 1.8 in a future version."
>
> There's also another possibility: when we do actually use Java 8-only
> stuff, for some time, to do it on a branch and release trunk as
> tapestry-core without Maven/Gradle qualifiers and this branch with a
> "-java8" qualifier.
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
@hlship
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Fri, 02 May 2014 04:45:42 -0300, Ulrich Stärk <ul...@spielviel.de> wrote:
> Do you expect any problems if we just switched to Java 8/Servlet 3.1
> without modifying anything else?
Yep. Lots of people and companies that won't or can't upgrade to a Java
version which was just released, at least not in the near future. Not to
mention that Java 8-only features will be only actually known and used by
most people in the not near future. Unless we start using Java 8-only
features in Tapestry, there's no reason IMHO to make such a long jump. The
Tapestry image still has some problems with radical changes.
I agree with Kalle: "A common sense approach would be to require 1.6 for
T5.4 and then require 1.8 in a future version."
There's also another possibility: when we do actually use Java 8-only
stuff, for some time, to do it on a branch and release trunk as
tapestry-core without Maven/Gradle qualifiers and this branch with a
"-java8" qualifier.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Ulrich Stärk <ul...@spielviel.de>.
Do you expect any problems if we just switched to Java 8/Servlet 3.1 without modifying anything else?
Uli
On 2014-05-01 18:54, Robert Zeigler wrote:
> Not opposed to an upgrade to Java 8, but not sure 5.4 is the right time for it. 5.4 has been
> long-enough in coming that I feel it would be better to release 5.4, and use 5.5 as the java8
> upgrade, possibly with a fairly short release time between 5.4 and 5.5. Basically, 5.5 could be
> “5.4 with java 8 compatibility” (and whatever new features (like the httpOnly cookie flag ticket
> you commented on recently) that would need > java 1.5 to support).
>
> Robert
>
> On May 1, 2014, at 5/111:38 AM , Ulrich Stärk <ul...@spielviel.de> wrote:
>
>> Historically I have been a strong opponent to Java version upgrades for Tapestry because IMO
>> the disadvantages outweighed the advantages by far.
>>
>> Now that we have lambda expressions, default methods, Nashorn and many other useful features
>> I'm leaning towards making a radical break and switch to Java 8.
>>
>> We should have a formal vote for such a radical change and a discussion firstin order to
>> gather comments and opinions from the community.
>>
>> Uli
>>
>> On 2014-04-30 12:57, Jochen Kemnade wrote:
>>> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
>>>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
>>>
>>> Which is much harder than I thought it was. I managed to find old rt.jar and jce.jar files
>>> and to make Gradle use them. Now I'm getting compile errors, e.g. in VirtualResource:88,
>>> MacOutputStream:45 and others. Mostly, it's Java 6 methods being used. First of all, do we
>>> still want to stick with Java 5 now that Java 8 is out and even Java 6 is EOL? Second, I
>>> wonder why it builds in Jenkins. What JDK is used there?
>>>
>>> Jochen
>>>
>>> --------------------------------------------------------------------- To unsubscribe, e-mail:
>>> dev-unsubscribe@tapestry.apache.org For additional commands, e-mail:
>>> dev-help@tapestry.apache.org
>>>
>>
>> --------------------------------------------------------------------- To unsubscribe, e-mail:
>> dev-unsubscribe@tapestry.apache.org For additional commands, e-mail:
>> dev-help@tapestry.apache.org
>>
>
>
> --------------------------------------------------------------------- To unsubscribe, e-mail:
> dev-unsubscribe@tapestry.apache.org For additional commands, e-mail:
> dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Jochen Kemnade <jo...@eddyson.de>.
Hi,
Am 14.05.2014 02:18, schrieb Kalle Korhonen:
> We could simply take a vote on this - case like this is exactly what the
> voting procedures at Apache were originally designed for.
I also thing that a vote is probably the way to go, but I'd like to make
sure that everyone is clear on the implications before the vote. I'm
pretty sure that there are still some of us who haven't completely made
up their minds in that regard (which is easy to say because I'm one of
them).
> We'd need to vote on a clearly defined issue, like "do we want to require Java 6 for T5.4 so
> we can upgrade dependencies that require Java 6, such as the newer closure
> compiler".
The recent closure compiler even requires Java 7.
Some people have already stated that we wouldn't benefit much from
switching only to Java 6. I think that's only partly true. While Java 6
doesn't bring too many useful new features language-wise, I'd see it as
a great benefit not having to support Java 5 anymore. And what's even
more important in my opinion is that we currently claim to support Java
5 but build and test on Java 6 minimum.
If we ditched support for Java 5, we could at least build/test with an
OpenJDK 6 (which is easily apt-gettable) and make sure that everything
works there.
I think, we should have one vote for dropping Java 5 support and, if
that succeeds, another one about Java 6.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Kalle Korhonen <ka...@gmail.com>.
We could simply take a vote on this - case like this is exactly what the
voting procedures at Apache were originally designed for. We'd need to vote
on a clearly defined issue, like "do we want to require Java 6 for T5.4 so
we can upgrade dependencies that require Java 6, such as the newer closure
compiler".
Kalle
On Tue, May 13, 2014 at 8:31 AM, Jochen Kemnade
<jo...@eddyson.de>wrote:
> Any new insights on this one? The current master will still FTBFS on Java
> 5.
>
> Am 02.05.2014 18:18, schrieb Kalle Korhonen:
>
> On Fri, May 2, 2014 at 12:57 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
>>
>> I don't see the benefits in this. As I said earlier, Java 6 and 7 IMO
>>> don't provide enough benefits
>>> to justify the change.
>>>
>>>
>> A newer Java version is required if we want to update the closure
>> compiler.
>>
>> Kalle
>>
>>
>> On 2014-05-01 19:01, Kalle Korhonen wrote:
>>
>>> I agree with Rob. A common sense approach would be to require 1.6 for
>>>>
>>> T5.4
>>>
>>>> and then require 1.8 in a future version.
>>>>
>>>> Kalle
>>>>
>>>>
>>>> On Thu, May 1, 2014 at 9:54 AM, Robert Zeigler
>>>> <ro...@roxanemy.com>wrote:
>>>>
>>>> Not opposed to an upgrade to Java 8, but not sure 5.4 is the right time
>>>>> for it. 5.4 has been long-enough in coming that I feel it would be
>>>>>
>>>> better
>>>
>>>> to release 5.4, and use 5.5 as the java8 upgrade, possibly with a fairly
>>>>> short release time between 5.4 and 5.5. Basically, 5.5 could be “5.4
>>>>>
>>>> with
>>>
>>>> java 8 compatibility” (and whatever new features (like the httpOnly
>>>>>
>>>> cookie
>>>
>>>> flag ticket you commented on recently) that would need > java 1.5 to
>>>>> support).
>>>>>
>>>>> Robert
>>>>>
>>>>> On May 1, 2014, at 5/111:38 AM , Ulrich Stärk <ul...@spielviel.de>
>>>>> wrote:
>>>>>
>>>>> Historically I have been a strong opponent to Java version upgrades
>>>>>> for
>>>>>>
>>>>> Tapestry because IMO the
>>>>>
>>>>>> disadvantages outweighed the advantages by far.
>>>>>>
>>>>>> Now that we have lambda expressions, default methods, Nashorn and many
>>>>>>
>>>>> other useful features I'm
>>>>>
>>>>>> leaning towards making a radical break and switch to Java 8.
>>>>>>
>>>>>> We should have a formal vote for such a radical change and a
>>>>>> discussion
>>>>>>
>>>>> firstin order to gather
>>>>>
>>>>>> comments and opinions from the community.
>>>>>>
>>>>>> Uli
>>>>>>
>>>>>> On 2014-04-30 12:57, Jochen Kemnade wrote:
>>>>>>
>>>>>>> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
>>>>>>>
>>>>>>>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
>>>>>>>>
>>>>>>>
>>>>>>> Which is much harder than I thought it was. I managed to find old
>>>>>>>
>>>>>> rt.jar and jce.jar files and to
>>>>>
>>>>>> make Gradle use them.
>>>>>>> Now I'm getting compile errors, e.g. in VirtualResource:88,
>>>>>>>
>>>>>> MacOutputStream:45 and others. Mostly,
>>>>>
>>>>>> it's Java 6 methods being used.
>>>>>>> First of all, do we still want to stick with Java 5 now that Java 8
>>>>>>> is
>>>>>>>
>>>>>> out and even Java 6 is EOL?
>>>>>
>>>>>> Second, I wonder why it builds in Jenkins. What JDK is used there?
>>>>>>>
>>>>>>> Jochen
>>>>>>>
>>>>>>> ------------------------------------------------------------
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Jochen Kemnade <jo...@eddyson.de>.
Any new insights on this one? The current master will still FTBFS on Java 5.
Am 02.05.2014 18:18, schrieb Kalle Korhonen:
> On Fri, May 2, 2014 at 12:57 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
>
>> I don't see the benefits in this. As I said earlier, Java 6 and 7 IMO
>> don't provide enough benefits
>> to justify the change.
>>
>
> A newer Java version is required if we want to update the closure compiler.
>
> Kalle
>
>
> On 2014-05-01 19:01, Kalle Korhonen wrote:
>>> I agree with Rob. A common sense approach would be to require 1.6 for
>> T5.4
>>> and then require 1.8 in a future version.
>>>
>>> Kalle
>>>
>>>
>>> On Thu, May 1, 2014 at 9:54 AM, Robert Zeigler
>>> <ro...@roxanemy.com>wrote:
>>>
>>>> Not opposed to an upgrade to Java 8, but not sure 5.4 is the right time
>>>> for it. 5.4 has been long-enough in coming that I feel it would be
>> better
>>>> to release 5.4, and use 5.5 as the java8 upgrade, possibly with a fairly
>>>> short release time between 5.4 and 5.5. Basically, 5.5 could be “5.4
>> with
>>>> java 8 compatibility” (and whatever new features (like the httpOnly
>> cookie
>>>> flag ticket you commented on recently) that would need > java 1.5 to
>>>> support).
>>>>
>>>> Robert
>>>>
>>>> On May 1, 2014, at 5/111:38 AM , Ulrich Stärk <ul...@spielviel.de> wrote:
>>>>
>>>>> Historically I have been a strong opponent to Java version upgrades for
>>>> Tapestry because IMO the
>>>>> disadvantages outweighed the advantages by far.
>>>>>
>>>>> Now that we have lambda expressions, default methods, Nashorn and many
>>>> other useful features I'm
>>>>> leaning towards making a radical break and switch to Java 8.
>>>>>
>>>>> We should have a formal vote for such a radical change and a discussion
>>>> firstin order to gather
>>>>> comments and opinions from the community.
>>>>>
>>>>> Uli
>>>>>
>>>>> On 2014-04-30 12:57, Jochen Kemnade wrote:
>>>>>> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
>>>>>>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
>>>>>>
>>>>>> Which is much harder than I thought it was. I managed to find old
>>>> rt.jar and jce.jar files and to
>>>>>> make Gradle use them.
>>>>>> Now I'm getting compile errors, e.g. in VirtualResource:88,
>>>> MacOutputStream:45 and others. Mostly,
>>>>>> it's Java 6 methods being used.
>>>>>> First of all, do we still want to stick with Java 5 now that Java 8 is
>>>> out and even Java 6 is EOL?
>>>>>> Second, I wonder why it builds in Jenkins. What JDK is used there?
>>>>>>
>>>>>> Jochen
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Kalle Korhonen <ka...@gmail.com>.
On Fri, May 2, 2014 at 12:57 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> I don't see the benefits in this. As I said earlier, Java 6 and 7 IMO
> don't provide enough benefits
> to justify the change.
>
A newer Java version is required if we want to update the closure compiler.
Kalle
On 2014-05-01 19:01, Kalle Korhonen wrote:
> > I agree with Rob. A common sense approach would be to require 1.6 for
> T5.4
> > and then require 1.8 in a future version.
> >
> > Kalle
> >
> >
> > On Thu, May 1, 2014 at 9:54 AM, Robert Zeigler
> > <ro...@roxanemy.com>wrote:
> >
> >> Not opposed to an upgrade to Java 8, but not sure 5.4 is the right time
> >> for it. 5.4 has been long-enough in coming that I feel it would be
> better
> >> to release 5.4, and use 5.5 as the java8 upgrade, possibly with a fairly
> >> short release time between 5.4 and 5.5. Basically, 5.5 could be “5.4
> with
> >> java 8 compatibility” (and whatever new features (like the httpOnly
> cookie
> >> flag ticket you commented on recently) that would need > java 1.5 to
> >> support).
> >>
> >> Robert
> >>
> >> On May 1, 2014, at 5/111:38 AM , Ulrich Stärk <ul...@spielviel.de> wrote:
> >>
> >>> Historically I have been a strong opponent to Java version upgrades for
> >> Tapestry because IMO the
> >>> disadvantages outweighed the advantages by far.
> >>>
> >>> Now that we have lambda expressions, default methods, Nashorn and many
> >> other useful features I'm
> >>> leaning towards making a radical break and switch to Java 8.
> >>>
> >>> We should have a formal vote for such a radical change and a discussion
> >> firstin order to gather
> >>> comments and opinions from the community.
> >>>
> >>> Uli
> >>>
> >>> On 2014-04-30 12:57, Jochen Kemnade wrote:
> >>>> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
> >>>>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
> >>>>
> >>>> Which is much harder than I thought it was. I managed to find old
> >> rt.jar and jce.jar files and to
> >>>> make Gradle use them.
> >>>> Now I'm getting compile errors, e.g. in VirtualResource:88,
> >> MacOutputStream:45 and others. Mostly,
> >>>> it's Java 6 methods being used.
> >>>> First of all, do we still want to stick with Java 5 now that Java 8 is
> >> out and even Java 6 is EOL?
> >>>> Second, I wonder why it builds in Jenkins. What JDK is used there?
> >>>>
> >>>> Jochen
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Ulrich Stärk <ul...@spielviel.de>.
I don't see the benefits in this. As I said earlier, Java 6 and 7 IMO don't provide enough benefits
to justify the change.
Uli
On 2014-05-01 19:01, Kalle Korhonen wrote:
> I agree with Rob. A common sense approach would be to require 1.6 for T5.4
> and then require 1.8 in a future version.
>
> Kalle
>
>
> On Thu, May 1, 2014 at 9:54 AM, Robert Zeigler
> <ro...@roxanemy.com>wrote:
>
>> Not opposed to an upgrade to Java 8, but not sure 5.4 is the right time
>> for it. 5.4 has been long-enough in coming that I feel it would be better
>> to release 5.4, and use 5.5 as the java8 upgrade, possibly with a fairly
>> short release time between 5.4 and 5.5. Basically, 5.5 could be “5.4 with
>> java 8 compatibility” (and whatever new features (like the httpOnly cookie
>> flag ticket you commented on recently) that would need > java 1.5 to
>> support).
>>
>> Robert
>>
>> On May 1, 2014, at 5/111:38 AM , Ulrich Stärk <ul...@spielviel.de> wrote:
>>
>>> Historically I have been a strong opponent to Java version upgrades for
>> Tapestry because IMO the
>>> disadvantages outweighed the advantages by far.
>>>
>>> Now that we have lambda expressions, default methods, Nashorn and many
>> other useful features I'm
>>> leaning towards making a radical break and switch to Java 8.
>>>
>>> We should have a formal vote for such a radical change and a discussion
>> firstin order to gather
>>> comments and opinions from the community.
>>>
>>> Uli
>>>
>>> On 2014-04-30 12:57, Jochen Kemnade wrote:
>>>> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
>>>>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
>>>>
>>>> Which is much harder than I thought it was. I managed to find old
>> rt.jar and jce.jar files and to
>>>> make Gradle use them.
>>>> Now I'm getting compile errors, e.g. in VirtualResource:88,
>> MacOutputStream:45 and others. Mostly,
>>>> it's Java 6 methods being used.
>>>> First of all, do we still want to stick with Java 5 now that Java 8 is
>> out and even Java 6 is EOL?
>>>> Second, I wonder why it builds in Jenkins. What JDK is used there?
>>>>
>>>> Jochen
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Kalle Korhonen <ka...@gmail.com>.
I agree with Rob. A common sense approach would be to require 1.6 for T5.4
and then require 1.8 in a future version.
Kalle
On Thu, May 1, 2014 at 9:54 AM, Robert Zeigler
<ro...@roxanemy.com>wrote:
> Not opposed to an upgrade to Java 8, but not sure 5.4 is the right time
> for it. 5.4 has been long-enough in coming that I feel it would be better
> to release 5.4, and use 5.5 as the java8 upgrade, possibly with a fairly
> short release time between 5.4 and 5.5. Basically, 5.5 could be “5.4 with
> java 8 compatibility” (and whatever new features (like the httpOnly cookie
> flag ticket you commented on recently) that would need > java 1.5 to
> support).
>
> Robert
>
> On May 1, 2014, at 5/111:38 AM , Ulrich Stärk <ul...@spielviel.de> wrote:
>
> > Historically I have been a strong opponent to Java version upgrades for
> Tapestry because IMO the
> > disadvantages outweighed the advantages by far.
> >
> > Now that we have lambda expressions, default methods, Nashorn and many
> other useful features I'm
> > leaning towards making a radical break and switch to Java 8.
> >
> > We should have a formal vote for such a radical change and a discussion
> firstin order to gather
> > comments and opinions from the community.
> >
> > Uli
> >
> > On 2014-04-30 12:57, Jochen Kemnade wrote:
> >> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
> >>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
> >>
> >> Which is much harder than I thought it was. I managed to find old
> rt.jar and jce.jar files and to
> >> make Gradle use them.
> >> Now I'm getting compile errors, e.g. in VirtualResource:88,
> MacOutputStream:45 and others. Mostly,
> >> it's Java 6 methods being used.
> >> First of all, do we still want to stick with Java 5 now that Java 8 is
> out and even Java 6 is EOL?
> >> Second, I wonder why it builds in Jenkins. What JDK is used there?
> >>
> >> Jochen
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: dev-help@tapestry.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@tapestry.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
Re: Build failed in Jenkins: tapestry-trunk-freestyle #1204
Posted by Robert Zeigler <ro...@roxanemy.com>.
Not opposed to an upgrade to Java 8, but not sure 5.4 is the right time for it. 5.4 has been long-enough in coming that I feel it would be better to release 5.4, and use 5.5 as the java8 upgrade, possibly with a fairly short release time between 5.4 and 5.5. Basically, 5.5 could be “5.4 with java 8 compatibility” (and whatever new features (like the httpOnly cookie flag ticket you commented on recently) that would need > java 1.5 to support).
Robert
On May 1, 2014, at 5/111:38 AM , Ulrich Stärk <ul...@spielviel.de> wrote:
> Historically I have been a strong opponent to Java version upgrades for Tapestry because IMO the
> disadvantages outweighed the advantages by far.
>
> Now that we have lambda expressions, default methods, Nashorn and many other useful features I'm
> leaning towards making a radical break and switch to Java 8.
>
> We should have a formal vote for such a radical change and a discussion firstin order to gather
> comments and opinions from the community.
>
> Uli
>
> On 2014-04-30 12:57, Jochen Kemnade wrote:
>> Am 29.04.2014 21:07, schrieb Jochen Kemnade:
>>> I'll downgrade it tomorrow and get myself a Java 1.5 compiler...
>>
>> Which is much harder than I thought it was. I managed to find old rt.jar and jce.jar files and to
>> make Gradle use them.
>> Now I'm getting compile errors, e.g. in VirtualResource:88, MacOutputStream:45 and others. Mostly,
>> it's Java 6 methods being used.
>> First of all, do we still want to stick with Java 5 now that Java 8 is out and even Java 6 is EOL?
>> Second, I wonder why it builds in Jenkins. What JDK is used there?
>>
>> Jochen
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org