No worries. I would not fully agree with "Java becoming legacy"; the Java
programming language might, but the JVM ecosystem (especially with GraalVM)
and all the new and exciting languages is not.

Licensing IMHO is pretty straightforward: Use OpenJDK in its different
flavors (usually the RHEL/Ubuntu versions on Linux and AdoptOpenJDK or
Corretto anywhere else) or, if you have money to spend, license from Oracle.

JDK8 is obsolete, Java 11 is the standard LTS release so everything
*should* build with 11. 16 is around the corner (with full support of
Alpine as the most exciting thing in there at least for me). And 17 which
will arrive in September then wraps all of this into a nice LTS bundle and
build a strong new foundation for the next years.

Don't get me wrong; I am excited about Rust and its possibilities,
especially in connection with WebAssembly. But Java is far from "legacy".
It is still way younger than C++ and no one would call that "legacy". :-)

-h





On Wed, Mar 3, 2021 at 2:36 AM Claude Brisson <cla...@renegat.net.invalid>
wrote:

> Thanks for the review, Henning.
>
> I found a little bug myself, I was considering putting it aside for the
> next release, but working on all JDKs seems an important goal. Even if
> Oracle licensing went somehow rogue... By the way, I like how most open
> source projects decided that JDK 8 was the norm. Anyhow, Java itself is
> slowly becoming legacy.
>
> So let's go for an RC2.
>
> I don't know at all why you don't have the karma to merge your PR.
>
> On 21-03-02 21 h 16, Henning Schmiedehausen wrote:
> > Builds and passes all tests with AdoptOpenJDK 8 on MacOS 11.
> > Fails tests on Java 11 and 15 (3 failures, all related to internal
> changes
> > in the JDK and brittle tests)
> >
> > I am somewhat 0 on this release, I don't really want to hold it up or
> make
> > Claude do another round.
> >
> > All the fixes (that make this pass all the tests on JDK 11 and 15) are
> > here: https://github.com/apache/velocity-engine/pull/20
> >
> > I know that Apache is commit-then-review, but hey, github.
> >
> > -h
> >
> > (First PR to velocity in ages. :-) )
> >
> >
> >
> >
> > On Mon, Mar 1, 2021 at 8:06 AM Claude Brisson <cla...@renegat.net.invalid
> >
> > wrote:
> >
> >> The Velocity Engine 2.3 RC1 is available since February 27.
> >>
> >> Main changes in this release:
> >>
> >> + New spring-velocity-support module, containing Spring framework
> >> Velocity Engine integration classes.
> >> + Security fix: let SecureUberspector block methods on ClassLoader and
> >> subclasses.
> >>
> >> Release notes:
> >>
> >> *
> >>
> >>
> https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.3/release-notes.html
> >>
> >> Distribution:
> >>
> >>    *
> https://dist.apache.org/repos/dist/dev/velocity/velocity-engine/2.3/
> >>
> >> Maven 2 staging repository:
> >>
> >>    *
> >>
> https://repository.apache.org/content/repositories/orgapachevelocity-1036
> >>
> >> Documentation:
> >>
> >> * http://velocity.apache.org/engine/2.3/
> >>
> >> Sources:
> >>
> >>    * https://github.com/apache/velocity-engine/releases/tag/2.3-RC1
> >>
> >> Please note than when evaluating this module, you will need to also
> >> install velocity-master version 4 to your local maven repository, with
> >> commands like:
> >>
> >> $ git clone --branch velocity-master-4
> >> https://github.com/apache/velocity-master.git
> >> $ cd velocity-master
> >> $ mvn install
> >>
> >> If you have had a chance to review the test build, please respond with a
> >> vote on its quality:
> >>
> >>
> >>    [ ] Leave at test build
> >>    [ ] Alpha
> >>    [ ] Beta
> >>    [ ] General Availability (GA)
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
> >> For additional commands, e-mail: dev-h...@velocity.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
> For additional commands, e-mail: dev-h...@velocity.apache.org
>
>

Reply via email to