tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Dodunski" <ChrisFromTapes...@christopher.net.nz>
Subject Re: Upgrade Tapestry build to Java 11
Date Tue, 27 Aug 2019 01:03:43 GMT
Hi all,

Just a heads up.  A linux exploit named 'watchbog' has been doing the
rounds, and several have reported that they've discovered the
vulnerability to be with Apache Lucene/SOLR.  If Tapestry comes bundled
with Lucene (I think it does), does it include the latest patches?

Regards,

Chris.


> Hi all,
>
> I managed to run a green build on my local machine on Java 11 as part of
> https://issues.apache.org/jira/browse/TAP5-2613, PR is here:
>
> https://github.com/apache/tapestry-5/pull/26
>
> I haven't tried Java 12 or above, not sure it's worth supporting any
> intermediate releases prior to Java 17 at this stage
> as that would be the next long term support (LTS) release as Java 11
> currently is.
> All major fixes should be back ported to 11.x.
>
> It would be nice to get a green build on Jenkins for it while we're
> waiting
> for the stable 5.5.x.
>
> I'll try to look at it next week, but won't mind if anyone can do it :)
>
> Thiago, do you have a hint where I could read about Jenkins upgrade?
> Or maybe we could try Travis CI on GitHub. JIRA & GitHub have got a nice
> integration: JIRA ticket automatically referenced this PR.
>
>
> On Thu, Jun 27, 2019 at 9:47 PM Thiago H. de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
>> On Sat, Jun 22, 2019 at 6:56 PM Dmitry Gusev <dmitry.gusev@gmail.com>
>> wrote:
>>
>> > Hi everyone!
>> >
>>
>> Hello, everyone!
>>
>>
>> > I tried to upgrade the build to Java 11 before I found discussion in
>> > TAP5-2588, and I even upgraded most of it while experimenting and got
>> all
>> > the tests green, except tapestry-javadoc module, which at first glance
>> > requires code rewrite and not just library upgrades and minor fixes as
>> it
>> > was with core modules.
>> >
>>
>> Indeed, before we build Tapestry with Java 11, we'll need to rewrite at
>> least tapestry-javadoc, but I guess that's mostly it. If we want to
>> provide
>> proper Java 9 modules too, we'll need to move some classes between
>> packages, since each package can only be in one module, and now we have
>> some packages with classes in more than one subproject/artifact/JAR. Far
>> from trivial.
>>
>>
>> > So I would suggest to go straight to Java 11 after we release current
>> state
>> > of master (5.5.x).
>> >
>>
>> Agreed.
>>
>> What about Java 12? It was released last March. I haven't checked what
>> are
>> the differences to 11, though.
>>
>>
>> > Starting from 5.6 all releases can remain binary compatible with java
>> 8,
>> > but the build itself may leverage the java 11 compiler to start
>> testing
>> > java 8+ compatibility, as required by TAP5-2611, for example.
>> >
>>
>> Agreed too.
>>
>> And thanks Dmitry for starting this important discussion!
>>
>> --
>> Thiago
>>
>
>
> --
> Dmitry Gusev
>
> AnjLab Team
> http://anjlab.com
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message