Migrate kaffe dependents to Java portgroup

[chrstphrchvz (Christopher Chavez)]

Since OpenJDK became available in MacPorts only somewhat recently, many ports still specify Kaffe as a fallback Java runtime. However the kaffe port has been deprecated, since the upstream Kaffe project is dormant, and the kaffe port is outdated and somewhat broken (see #45198 and ​https://ports.macports.org/port/kaffe/builds).

Some of these ports continue to work as long as a compatible Java installation is already present. However many ports may be old, outdated, no longer maintained upstream, and might have difficulty working with more recent supported Java versions. Some will not compile under recent Java versions, even though their binary distributions might work fine. Certain ports are for libraries which aren't too useful on their own, but were needed by ports like tomcat5/6 and struts which have since been removed. Newer upstream versions of these ports might have introduced incompatibilities with/are not drop-in replacements for the versions still in MacPorts. In cases like these, a decision should be made to either keep and update the port, or remove it.

For the ports that are to be kept, the Java portgroup should be used to declare a dependency on Java (rather than depends_build/depends_lib/depends_run), specify what Java versions are compatible (after researching which ones each port works with), and control which fallback Java version that MacPorts will install if needed (preferably openjdk8 or openjdk11 as those are LTS releases).

The ports might have other outdated dependencies to clean up (e.g. jikes, gnu-classpath, and older versions of maven).

port	maintainer	status
beanshell 2.0b4_0		#60201
castor 0.9.9_0		#60202
cglib 2.2.2_0		#60197
checkstyle 4.3_0		#32187, #51731
cobertura 1.6_0		#59683
commons-beanutils 1.8.2_0		[0551cdaeab/macports-ports]
commons-cli 1.1_1		???
commons-codec 1.4_0		???
commons-collections 3.2.1_0		[ef8c2c5ad6/macports-ports]
commons-fileupload 1.2.2_0		[4a41f36903/macports-ports]
commons-io 1.4_0		???
commons-lang 2.4_0		???
commons-pool 1.5.4_0		???
daisydiff 1.2_0		???
derby 10.9.1.0_0		#54838
derby-server 10.5.3.0_0		???
dom4j 1.6.1_1		#60218
ehcache 1.1_0		#60219 [3ae6f98778/macports-ports]
fantom 1.0.61_0	hum.ph:m	#60213
flyway 6.3.1_0	@emcrisostomo	[fae2ad3a13/macports-ports]
google-guava 13.0.1_0		???
itext 1.1_0		#19385
jakarta-log4j 1.2.16_0		#53458
java_memcached 2.0.1_0		???
jdom 1.1.1_0		???
jfreechart 1.0.0-pre2_0		#60200
jgoodies-common 1.4.0_0		???
jgoodies-forms 1.6.0_0		???
jgoodies-looks 2.5.2_0		???
jmock1 1.2.0_0		???
jmock2 2.5.1_0		???
jmol 14.29.51_0	@p-bro	[0c0be707b3/macports-ports]
jna 3.2.7_0		???
jsch 0.1.54_0		[cfaa086942/macports-ports]
jtidy 04aug2000r7_0		#60198
libsvm 3.20_2		???
log4jdbc 1.1_0		???
mars 4.4_0		???
msv 20081113_1		???
mysql-connector-java 5.1.12_0		#58685
nds2-client-java 0.16.3_0	@emaros	???
objenesis 1.1_0		???
pdfbox 0.7.1_0		???
plantuml 1.2019.11_0		[24d7ce203ef/macports-ports]
plovr 0.0-20120503103549_0		???
postgresql7 7.4.24_5 (+java variant)		???
proguard 6.2.0_0		???
pulse 1.2.18_0	redhillconsulting.com.au:simon	???
relames 20060319_0		???
rhino 1.7R2_1		???
saxon 9.5.1.1_0		???
saxpath 1.0_0		???
sbt-0.7 0.7.7_0		???
scala-migrations 1.0.1_0	@blair	#60617
servlet23-api 1_0		#58389
servlet24-api 5.5.28_0		#58389
slf4j 1.5.6_0		???
sphinx4 1.0beta5_1		#60199
spring-framework25 2.5.6.SEC01_0		???
spring-framework30 3.0.7_0		???
spring-framework31 3.1.2_0		???
spring-javaconfig 0.2.1.0.0.M4_1		???
spymemcached 2.8.4_0		???
statcvs 0.2.2_0		[06e1ee97a3/macports-ports]
swig-java 4.0.1_0	@michaelld	[4c8bbb8a4f/macports-ports]
swig3-java 3.0.12_0	@michaelld	[4c8bbb8a4f/macports-ports]
unicodeconverter-java 2.0_0		???
xalanj 2.7.1_0		???
xercesj 2.11.0_0		???
xml-commons-resolver 1.1_0		#58671
xmlenc 0.52_0		???
xmlpull 1.1.3.4c_0		???
xom 1.2.10_0		???
zanata-cli 4.6.2_0	@l2dy	???

[p-bro]

jmol is still maintained and developed upstream. I occasionally upgrade the port. And I'd like to keep it that way.

How can I check which java version is compatible? Could not find any information on the upstream website.

Side note: On my machine it uses a JRE in /usr/bin, linking to /System/Library/Frameworks/JavaVM.framework/Versions/A/Commands/java.

$java -version
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

[chrstphrchvz (Christopher Chavez)]

Replying to p-bro:

jmol is still maintained and developed upstream. I occasionally upgrade the port. And I'd like to keep it that way.

How can I check which java version is compatible? Could not find any information on the upstream website.

Side note: On my machine it uses a JRE in /usr/bin, linking to /System/Library/Frameworks/JavaVM.framework/Versions/A/Commands/java.

$java -version
java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

Thanks for the quick response.

I found the FAQ page specifies a minimum Java version (assuming it's not outdated): ​http://jmol.sourceforge.net/faqs/

Application system requirements

What platforms does the Jmol application run on?

The Jmol application should run on any system that supports Java 1.4. Previous versions of Java are not supported.

This would suggest specifying Java 1.4 or higher in the port.

There is the possibility of a maximum compatible Java version, but have not confirmed this is the case. I briefly looked for discussions of issues with more recent Java versions on the project's mailing list and issue tracker, and so far only came across issues building jmol from source with Java 9 or later: ​https://sourceforge.net/p/jmol/bugs/608/ ​https://sourceforge.net/p/jmol/mailman/message/34860374/ . Since the port uses the binary distribution rather than builds from source, this shouldn't be an issue.

If jmol appears to work with the Java 8 on your system, then using Java 8 LTS as the fallback should be fine for now, and I believe is less likely to cause disruption than using Java 11 LTS. To clarify, the fallback version is what will be used if no other Java (version 1.4 or later) installation is already present.

I have opened a pull request on GitHub with the changes I suggest making: ​https://github.com/macports/macports-ports/pull/6636

[chrstphrchvz (Christopher Chavez)]

In fae2ad3a137866fe6c7c5dc439f888daab20745b/macports-ports (master):

flyway: use Java portgroup

Use latest Java LTS (Java 11) as fallback

Remove fallback dependency on deprecated port kaffe
See: #60206

[chrstphrchvz (Christopher Chavez)]

In 303bccd31cc7523a4561d9347af7b612d8fd241c/macports-ports (master):

fantom: drop maintainer

Maintainer responded via email: they no longer use
nor are interested in maintaining this port.

See: #60206
See: #60213
Closes: #60214

[chrstphrchvz (Christopher Chavez)]

In 0c0be707b3389ad1d466ce3c3b32cd745f3a2ef7/macports-ports (master):

jmol: use Java portgroup (​https://github.com/macports/macports-ports/pull/6636)

Remove fallback dependency on deprecated port kaffe
See: #60206

[chrstphrchvz (Christopher Chavez)]

In 06e1ee97a3bc2169f32a5abdbea9e4b4a7936b4f/macports-ports (master):

statcvs: delete port (​https://github.com/macports/macports-ports/pull/6605)

Port has never been updated since submitted in 2004;
has been outdated since release of 0.2.3 in 2006;
latest version is 0.7.0, released 2010

Has fallback dependency on deprecated port kaffe
See: #60206

Has indirect dependency on EOL port servlet24-api
(via dependency on outdated port jfreechart)
See: #58389

No dependents.

[chrstphrchvz (Christopher Chavez)]

In cfaa086942fb9b19a81307866aa7e50587a703ff/macports-ports (master):

jsch: update to 0.1.55

Use Java portgroup + LTS OpenJDK fallback
instead of kaffe (deprecated)
See: #60206

Add size to checksums

[neverpanic (Clemens Lang)]

In 24d7ce203ef58e34aa861ee14bcbb547bf05fa38/macports-ports (master):

plantuml: Update to 1.2020.11

Switch to the java 1.0 PortGroup.

See: #60206

[chrstphrchvz (Christopher Chavez)]

In 0551cdaeabba19854dcbe16d60019be451a8ba71/macports-ports (master):

commons-beanutils: delete port

Port has been outdated since release of 1.8.3 in 2010.
Port has no dependents; was needed by tomcat5, tomcat6, and struts, which were deleted.

Indirectly depends on EOL port servlet23-api
See: #58389

Has fallback dependency on kaffe
See: #60206

[chrstphrchvz (Christopher Chavez)]

In 4a41f369033e9381a7d14771522b868e746b9146/macports-ports (master):

commons-fileupload: delete port

Port is outdated. Port has no dependents; was needed by
tomcat5, tomcat6, and struts, which have been deleted.

Depends on EOL port servlet23-api
See: #58389

Has fallback dependency on kaffe
See: #60206

[chrstphrchvz (Christopher Chavez)]

In ef8c2c5ad6e919ddc1ae641e7d2dbeadac502675/macports-ports (master):

commons-collections: delete port

Was needed primarily for tomcat5, tomcat6, and struts, which were removed.
Was never updated to 3.2.2 (released 2015).

Closes: #53939

Has fallback dependency on kaffe
See: #60206

[chrstphrchvz (Christopher Chavez)]

In 4c8bbb8a4f386dc922dc0ccfef7dad9e47e47261/macports-ports (master):

swig-java, swig3-java: migrate to Java portgroup

Set fallback to an LTS Java version

Avoid fallback dependency on kaffe
See: #60206