JSR-275 has been withdrawn more than one year ago, and we don't know yet if a
new JSR would be attempted (the ex-JSR-275 leader is still investigating
one year ago as a replacement, and is now implemented by 3 independent products
(including one commercial). In order to keep the "javax" space clean, Oracle is
investigating the possibilities to remove dead projects like JSR-275 from Maven
repositories. We don't know yet if JSR-275 would be removed from Maven Central,
since Maven maintainer are reluctant to removing anything from that repository.
Giving all the above, we have to move away from JSR-275 and I have been told
that org.unitsofmeasurement is the best target. If there is no objection, I plan
to perform the switch next weekend on GeoAPI trunk. This change would be part of
GeoAPI 3.1 release.
Note that this change was already announced in GeoAPI 3.0
So hopefully, users and implementors will not be too surprised...
For those we can not switch easily to GeoAPI 3.1, The
Geotoolkit.org project
will continue to provide GeoAPI 3.0.0 implementations (together with GeoAPI 3.1
implementations) for a while.
The release date and the exact content of GeoAPI 3.1 is not yet determined. The
roadmap will depend on feedback on this mailing list, feedback at OGC meetings,
and available resources.
Martin
Locked
