Remove as much legacy components as possible #22
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
review
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#21 Serveral CDI-related warnings when starting master branch
LibreCCM/libreccm
Reference: LibreCCM/libreccm#22
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
At the moment, the code base contains a large number of old classes in the
com.arsdigitaandcom.redhatpackages. Due to migration of the UI to Jakarta MVC many of these classes are no longer needed. Removing these classes will most likely speedup the build process, and remove the potential for bugs caused by side effects caused by incompatibilities between these legacy classes and modern Jakarta EE.Before removing any of these components, a branch containing the legacy components should be created, to preserve these components.
The main focus of these components is the old Bebop based UI, together with the classes required for processing XSL. Removing these classes would also allow us to remove several dependencies. Some of them are quite old, but can't be updated because the classes in the
com.arsdigitaandcom.redhatpackages depend on the specific behaviour of these classes. For some of the dependencies not updates are available, despite several known issues because these libraries are not longer maintained.