I know About both JSF and
JSONP, that for „convenience“ or dependency Resolution the
API and implementation are often bundled into the same JAR
(something I would hope to see changed if Jigsaw was
properly applied in Jakarta EE 9+) but they’re not really
tied together.
It may be the case for
really old ones like JAF or JavaMail.
I know most certainly, that
on the Java SE side java.time (JSR 310) API is inseparable
from its implementation because some of the „rump API“
elements like TemporalUnit has an even circular(!) reference
to an implementation class Duration which implements
TemporalAmount that again references TemporalUnit,…
There's a few cases where the API is not
separate from the implementation
and can't easily be separated. What do we
want to do for these cases?
The prototypical split would be:
Spec Project: spec document repo; TCK repo
(eventually); API repo
Impl Project: impl repo
The choices for these hard to split cases
seem to be:
Spec Project: spec document repo; TCK repo
(eventually)
API+Impl Project: API+impl repo
or
Spec Project: spec document repo; TCK repo
(eventually); API+impl repo
Which is better?
I prefer the latter, although we could
choose on a case by case basis.
If I remember right, this is an issue for
JavaMail, JAF, JSONP, and JSF.
I know that JavaMail and JAF will never be
split.
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve
your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee