GeoAPI provides a set of interfaces in programming languages (currently Java and Python) for geospatial applications. The GeoAPI interfaces closely follow OGC specifications, adaptated to match the expectations of programmers.
The GeoAPI 3.1/4.0 development branches tentatively provided a Swing application for running the conformance tests. That application was not mandatory for running the tests, it was provided only as a convenience. However it depends on relatively advanced JUnit 4 API, and its existence is making more difficult to upgrade to JUnit 5. Consequently we propose to delete the following from geoapi-conformance module:
The whole org.opengis.test.runner package.
The JUnit 4 @Rule inside the org.opengis.test.TestCase class.
The TestListener and TestEvent classes, which now have replacements in JUnit 5.
The TestSuite class.
@Rule, TestListener, TestEvent and TestSuite were used mostly by the graphical runner and their existences were a problem for JUnit 5 upgrade, because JUnit 4 Rule and Suite for instance are not supported in JUnit 5 (or at least not directly). Removing those classes do not prevent the execution of conformance tests in the traditional JUnit way.
All features targeted for removal in this issue were new development on GeoAPI 3.1/4.0 branches. None of them were part of GeoAPI 3.0.x standard releases. Consequently this issue has no compatibility impact on users of current GeoAPI standards.
The graphical runner may be bring back latter if the SWG wish so. It has already been ported and upgraded to JUnit 5 in a separated project, namely GeoAPI GIGS, and is used by PROJ-JNI for instance. This work can be bring back to GeoAPI when the project completed its own migration to JUnit 5 and if the SWG wishes.
The GeoAPI 3.1/4.0 development branches tentatively provided a Swing application for running the conformance tests. That application was not mandatory for running the tests, it was provided only as a convenience. However it depends on relatively advanced JUnit 4 API, and its existence is making more difficult to upgrade to JUnit 5. Consequently we propose to delete the following from
geoapi-conformancemodule:org.opengis.test.runnerpackage.@Ruleinside theorg.opengis.test.TestCaseclass.TestListenerandTestEventclasses, which now have replacements in JUnit 5.TestSuiteclass.@Rule,TestListener,TestEventandTestSuitewere used mostly by the graphical runner and their existences were a problem for JUnit 5 upgrade, because JUnit 4RuleandSuitefor instance are not supported in JUnit 5 (or at least not directly). Removing those classes do not prevent the execution of conformance tests in the traditional JUnit way.All features targeted for removal in this issue were new development on GeoAPI 3.1/4.0 branches. None of them were part of GeoAPI 3.0.x standard releases. Consequently this issue has no compatibility impact on users of current GeoAPI standards.
The graphical runner may be bring back latter if the SWG wish so. It has already been ported and upgraded to JUnit 5 in a separated project, namely GeoAPI GIGS, and is used by PROJ-JNI for instance. This work can be bring back to GeoAPI when the project completed its own migration to JUnit 5 and if the SWG wishes.