You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The use of the Java Stream leads to failures in 'Move Method' refactoring. #4289
When using a tool to detect Feature Envy and perform automated refactoring, if the refactored code contains syntax errors, should I attempt to fix them manually?
Before Refactoring:
From the example you gave, if you move the processData method to TargetClass, where TargetClass is in another file, the boolean isPositive(Integer number) method's visibility in SourceClass is changed from private to package protected, which makes it visible to TargetClass. Code compiles fine.
Maybe record a screencast of your workflow so we get a better understanding of your issue.
Activity
fbricon commentedon Dec 19, 2025
From the example you gave, if you move the processData method to TargetClass, where TargetClass is in another file, the
boolean isPositive(Integer number)method's visibility in SourceClass is changed from private to package protected, which makes it visible to TargetClass. Code compiles fine.Maybe record a screencast of your workflow so we get a better understanding of your issue.