Skip to content

Draft of Quality-oriented Move Method Refactoring Algorithm. Do not merge! #46

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

Open
wants to merge 15 commits into
base: master
Choose a base branch
from

Conversation

olgalupuleac
Copy link

@olgalupuleac olgalupuleac commented Apr 17, 2018

The algorithm is based on this article. The main idea -- code quality can be measured using 11 metrics, so we try to move method from one class to another and recalculate all metrics. The increase of metrics sum detects the refactoring.

The major problem was how to move the method from one class to another. Implementation of this algorithm for Eclipse uses libraries org.eclipse.jdt.internal.corext.refactoring.structure and org.eclipse.ltk.core.refactoring, but I didn't find analogues for Intellij Idea.

distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-2.10-bin.zip
distributionUrl=https\://services.gradle.org/distributions/gradle-2.10-all.zip
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need to change this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants