Java 9 and beyond can be handled with version specific code in META-INF.
That’s what we’re doing in Log4j for now. Based on how the new LTS schedule
works, it’s better to keep updated with each new release as it comes out
due to how deprecated APIs are removed now. Version specific overrides of
cod
Thanks for prompt reply and all pointers. idReferences seem to have no
connection to references that addBeans use.
I am under impression that things were somewhat different with Ant 1.6
(-ish), but the manual did not change since then
so it probably needs an update with a reference to macrodef and
It will be good to be on the same page with major dependencies (and
hopefully fix that old nut listTokenValues() :-)
Please consider Java 11 for TLSv1.3 when time comes (or the next LTS
version, Java 17 when it's out --
by then, pack200 will surely be gone...)
Gintas
On Wed, 30 Oct 2019 at 20:26,
twogee opened a new pull request #90: Java 8
URL: https://github.com/apache/ant-ivy/pull/90
Yay for Java 8!
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use t
Sounds good. Similar to Ant, on branch for maintaining the version for the old
Java version and master for the new(er) one.
And as suggested we shoundn't go farer than Ant itself, so Java8 is fine with
me (no Java 13).
So: +1
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto
Now that Ivy 2.5.0 has been released, I would like to propose the
following ideas for the next goals for the project:
1. I would like to wait and watch for any bug reports for 2.5.0 and do
some relatively frequent bug fix releases for that version. So
essentially 2.5.x versions which are solely bu
