Remove support for FB360 and VISR plugins #289
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Last release warned these plugin suites would no longer be supported in an upcoming release. This is that change. The reason for this is that it add a lot of development overhead when implementing new features in the EPS and makes the code less manageable and more cluttered than it needs be. Both plugin suites are no longer in development or have any ongoing support these days anyway.
Works towards #41 - This is less of an issue now that we don't have to support multiple plugin suites. There are however some ADM features even the EAR plugins don't support yet, and that should be warned.
Works towards #122 - Again, much easier with just one plugin suite to support
Closes #150 - becomes irrelevant