The Javapocalypse is Monday

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I've just been looking through my packager-dashboard page.  A
depressingly large chunk of my packages are going to become
unbuildable on Monday when a bunch of orphaned Java packages are
retired.  I think a lot of us are going to be affected.  In my case,
there are quite a few non-Java packages involved (due to the parser
generators antlr3 and antlr4-project), primarily OCaml and python
packages.  Mikolaj has a huge pile of work on his shoulders, so don't
take this as criticism of him.

Here are some of the pain points:
- log4j will be retired, which will break ant.
- hamcrest2 will be retired, which will break apache-commons-lang3,
which will break bcel, which will also break ant.
- google-gson and javassist will be retired, which will break
reflections, which will break jna, which is used by about a dozen
packages, including bcel.
- maven-install-plugin will be retired, which will break tycho, which
will break eclipse.
- args4j will be retired, which will break jacoco and jgit.
- maven-invoker-plugin and several of its dependencies
(maven-doxia-sitetools, plexus-velocity, maven-reporting-api,
maven-script-interpreter, and maven-reporting-impl) will be retired,
which will break xml-maven-plugin, which is used by eclipse.
- jakarta-el and jakarta-server-pages will be retired, which will break eclipse.
- aopalliance will be retired, which will break maven-native.
- jdependency will be retired, which will break maven-shade-plugin,
which is used by openjfx8, a dependency of java-1.8.0-openjdk.
- apache-ivy will be retired, which will break javapackages-tools.

I have packages that depend directly on the following, so I am willing
to adopt them if nobody more competent shows up (although there is no
point in taking ant-contrib if ant is going to be broken anyway):
- ant-contrib
- jakarta-common-httpclient
- jakarta-ws-rs
- maven-invoker-plugin
- spec-version-maven-plugin

I introduced the jansi1 and jline2 packages so that jansi could be
moved to 2.x and jline to 3.x, but I don't actually maintain any
packages that need the old versions.  I would like to give them away
to someone who needs them, but note that you will need to grab
jansi-native as well, before Monday!

Has anybody already done something about any of these packages (and my
packager-dashboard page just hasn't caught up yet)?  Is anybody
planning to do something about any of these packages before they are
retired on Monday?
-- 
Jerry James
http://www.jamezone.org/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux