Received-SPF: pass
 receiver=post.selbstdenker.com; client-ip=209.85.219.53; envelope-from=recurve@cocoanutstech.com
From: Aaron Rosenzweig <aaron@chatnbike.com>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Date: Fri, 9 Dec 2022 16:37:46 -0500
Subject: duplication in frameworks: ERExtensions, javaeoaccess
Message-Id: <F2DCF98B-D02A-461C-AC6A-0B80CEA350E6@chatnbike.com>
To: WebObjects & WOnder Development <webobjects-dev@wocommunity.org>

The package com.webobjects.eoaccess is defined in both: ERExtensions, =
javaeoaccess

javaeoaccess is a framework from NeXT/Apple.=20

I believe ERExtensions recreated a distinctly apple package name so that =
we could replace Apple's _EOExpressionArray with a new one from Wonder.=20=


This worked because if we load ERExtensions before =
JavaEOAccess.framework=E2=80=A6 in the class path, the first one wins. =
Old JVMs would happily take the first. While this is risky, it worked as =
long as we were careful (and sort of knew what Apple was doing). We did =
things like this because we didn=E2=80=99t own JavaEOAccess and =
basically =E2=80=9Cpatched it=E2=80=9D because we wanted an improvement =
that Apple didn=E2=80=99t provide. We could do better than Apple and =
this is how we did it, while letting the rest of the Apple plumbing =
continue working with particular object replacements.=20

This cannot work past Java 1.8 can it? If we are targeting Java 17 =
compliance, we are then using JPMS (Java Package Module System) aka =
=E2=80=9CJava Modules=E2=80=9D which won=E2=80=99t accept this type of =
patch.=20

In my application project, I created a module-info.java and placed these =
lines in it:

requires ERExtensions;
requires javaeoaccess;

We need both lines right? But this results in the the following =
unsurprising error:
The package com.webobjects.eoaccess is accessible from more than one =
module: ERExtensions, javaeoaccess

What am I missing? Are we stuck? Without being able to update the Apple =
jars directly, the old hacks cannot work in the new word of Java =
Modules. We=E2=80=99ve done this in many places including NSArray. Are =
we stuck living in Java 1.8 compliance with Java 17?=20=