New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
METHOD_RETURN_TYPE_CHANGED
reported for package-private
method promoted to public
that changes return type
#384
Comments
METHOD_RETURN_TYPE_CHANGED
reported for package-private
method promoted to public
But the method return type changed, didn't it? The change of the access modifier is not the problem. |
Yes, it changed, but it shouldn't be a problem as it was originally Or do you have in mind split-package usage? |
This seems to duplicate #265 |
@garydgregory the only reason I didn't mention it as a duplicate of #265 is the potential split-package usage of an existing package-private method (my case), while a private one (your case) wouldn't be affected. |
OK. It is helpful to know that these two issues are related though. |
METHOD_RETURN_TYPE_CHANGED
reported for package-private
method promoted to public
METHOD_RETURN_TYPE_CHANGED
reported for package-private
method promoted to public
that changes return type
It is a difficult decision. |
A separate error that I can exclude in my config would work for me 👍 If there are split-package users that are impacted by this change, it means they are already dancing on the edge of brokenness and we don't provide support for such usage 😉 |
Re-reading your last message, how is I set it to |
I thought about an implementation and as it looks, it might introduce a new concept. The point is that currently the relation between type of change (like e.g. |
My rough idea was to approach it in a way similar to #311. I haven't looked at the code in detail yet, but I trust you can spot better than me whether this is feasible with such a strategy. |
Unfortunately it is not that easy, because we need to change the incompatibility for each occurrence. I think we need to change the list of incompatibilities from a pure |
…e of JApiCompatibilityChange to reflect that METHOD_RETURN_TYPE_CHANGED is not incompatible in case the method's visibility increased
Committed the changes mentioned above to a new branch. Will have to sleep a night, before I merge it. |
Thanks a lot for looking into it! |
Fixed with 0.19.0. |
Thank you! |
This reverts commit d6cb373.
The following
package-private
method:has been promoted to
public
and changed to:and japicmp reports it as binary incompatible:
Is it a false positive? If yes, I'm happy to submit a fix.
Commit: assertj/assertj@ff01677
CI result: https://github.com/assertj/assertj/actions/runs/8037768330/job/21952981201#step:4:202
The text was updated successfully, but these errors were encountered: