Re: Apache Tapestry for Java 11
Paul Stanton <[email protected]> Sat, 26 Oct 2019 08:55:09 +1100
| Newsgroups | gmane.comp.java.tapestry.user |
|---|---|
| Message-ID | <[email protected]> |
"We can push a new 5.5 beta for early testers." ^-- is this available? if not, any eta? On 11/09/2019 4:43 am, Thiago H. de Paula Figueiredo wrote: > On Tue, Sep 10, 2019 at 4:31 AM Chris Poulsen <[email protected]> > wrote: > >> I did roll an "internal" 5.5-beta version based on the code from 12th July >> as there are some fixes in HEAD that are not in the beta-2 and that bastard >> build is what we currently are using without problems. >> > We can push a new 5.5 beta for early testers. > > >> If 5.5 isn't 100% ready for release yet, it seems to be really close and it >> would be good to get it finalized IMO. >> > Yes, we're close. I'd just want to finish the support for running without > Bootstrap (or with Bootstrap 4) before releasing 5.5. I don't see any other > blockers or nice-to-haves. Other people may have their own, of course. :) > > And yes, 5.5 supports Java 11 bytecode, and that's exactly the issue that > most probably took the team the longer to develop. > > >> -- >> Chris >> >> On Mon, Sep 9, 2019 at 9:11 PM Charles Roth <[email protected]> wrote: >> >>> Sounds good to me. We'd be very happy to test a 5.5-beta. (Large >>> application that has about 1M LOC, including unit-tests, TML, etc.) >>> >>> On 9/9/2019 3:08 PM, Dmitry Gusev wrote: >>>> Hi Charles, >>>> >>>> Current state of the master branch should run just fine on Java 11; >>> there's >>>> no release you can download though. >>>> >>>> We should probably start a vote on another Tapestry 5.5-beta soon to >>>> release current state of the master branch, >>>> and maybe make a first 5.5.0 release right after we get some feedback >>> from >>>> community. >>>> >>>> >>>> On Mon, Sep 9, 2019 at 9:54 PM Charles Roth <[email protected]> >> wrote: >>>>> Is there any new(ish) word on Tapestry 5.5 or any other release that >>>>> will run under Java 9, 10, and maybe 11? >>>>> >>>>> Thanks! >>>>> >>>>> On 10/8/2018 12:54 PM, Bob Harner wrote: >>>>>> Yes. The unreleased 5.5 version passses all tests with the Java 9+ >>>>>> compatible version of ASM (which was the obstacle for running >> Tapestry >>>>> 5.4 >>>>>> under Java 9+) and should be usable for Java 9 and 10 now (once >>>>> released), >>>>>> although it hasn't been tested enough by others. I haven't checked it >>>>> with >>>>>> Java 11 yet. The Tapestry nightly snapshot process is broken >> currently, >>>>> and >>>>>> that's the principal obstacle to the 5.5 release. >>>>>> >>>>>> >> https://issues.apache.org/jira/plugins/servlet/mobile#issue/TAP5-2588 >>>>>> My weekends have been occupied by other projects the last few weeks >>> but I >>>>>> hope to get back on it next weekend. >>>>>> >>>>>> On Mon, Oct 8, 2018, 9:49 AM gard sæbø <[email protected] >>>>>> wrote: >>>>>> >>>>>>> Hi! >>>>>>> >>>>>>> We are upgrading all our Java applications, which currently runs on >>> Java >>>>>>> 8, to Java 11. >>>>>>> >>>>>>> Our web applications use Apache Tapestry as the frontend framework, >>> but >>>>> it >>>>>>> seems a bit quite on the Tapestry commit log in comparison with >> other >>>>>>> frontend frameworks. >>>>>>> >>>>>>> Will there be any upgrade which will support Java 11 and future Java >>>>>>> versions? >>>>>>> >>>>>>> Best regards, >>>>>>> Gard Sæbø >>>>>>> >> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [email protected] >>>>>>> For additional commands, e-mail: [email protected] >>>>>>> >>>>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]