Filter try-with-resources before filtering inlined code again #1219
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.
Due to the changes in 1ceafb3, the issue in #681 that was fixed in #683 is back.
As the order of filters is no longer defined by the service loader file order,
but by name, the try-with-resources filter was put last and thus after the inlined code filter again.
This made the same issue reappear.
This PR adds an explicit order setting for features on which they are compared first and only for equal ones by name.
Standard value is 100 for all features, to prevent the psychologically bad necessity to use a negative order.
The try-with-resources filter gets 50, so it is executed before the inlined code filter which is the important part.