RANGER-5131: remove finalize from policy engine #531
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.
What changes were proposed in this pull request?
Removal of finalize() method from PolicyEngine class
As part of our efforts to ensure compatibility with future JDK versions, this code change removes the deprecated finalize() method from the PolicyEngine class. The finalize() method has been deprecated since JDK 9 and is slated for removal in future JDK versions.
Impact Analysis
A thorough analysis was conducted to assess the impact of removing the finalize() method. The results indicate that there is no adverse impact on the functionality of the PolicyEngine class.
Existing Cleanup Mechanisms
It's worth noting that we already have a cleanup() method in the RangerBasePlugin class, which allows users to release resources held by the PolicyEngine. This method provides a manual way to perform cleanup operations, ensuring that resources are properly released when needed.
How was this patch tested?
mvn clean install