Obsolete modules proposal - deegree/deegree3 GitHub Wiki
Implemented change
The changes are implemented in pull request https://github.com/deegree/deegree3/pull/94 , except that the 3D modules have not been moved as discussed in the TMC. The unmaintained modules are now in uncoupled/orphaned-after-3.2/
. There is a root pom.xml
which can be used to build all these, and the versions have all been set to 3.2.0
.
Here's a copy of the original proposal:
This is a discussion page to discuss how we can clean up the deegree modules a little bit.
Current situation:
- we have
uncoupled
, where a couple of non-maintained modules reside - we have modules in the main tree which are unmaintained
Proposal:
uncoupled
Cleaning up Let's clean up the uncoupled
directory, then move more unmaintained modules to uncoupled
.
I believe almost everything can be deleted from uncoupled
:
deegree-demos
- we have proper workspaces as demos nowdeegree-maven-plugin
- it's been extracted into a separate GitHub projectdeegree-wfs-cite110-postgis-blob/relational
- completely out of date, were never running anywaydeegree-workspace-sos
- nobody seems to know the statusresources
,scripts
seems like some directories made it from the pre-maven-phase
Anybody knows the state of the deegree-mdeditor
?
uncoupled
Modules to be moved to The following modules are marked as unmaintained in the stability status page and should be uncoupled
IMHO:
deegree-api-examples
deegree-core-3d
deegree-core-observation
deegree-services-sos
deegree-services-wpvs
deegree-sos-webclient
deegree-tools-3d
deegree-workspace-wpvs
A couple of modules I'm not sure about:
deegree-processprovider-sextante
- should we keep it? It pulls a lot of dependencies and is not maintained.deegree-featurestore-geocouch
- as long as there's no interest from the community, we should move this touncoupled
I'd propose to move these modules to uncoupled
and add a proper building process there, then fix the dependency versions to the other deegree modules to 3.2.0
.