Skip to content
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

Enhanced IBuildSupport usage to support other build tools such as bazel #1674

Closed
wants to merge 3 commits into from
Closed

Conversation

dbushenko
Copy link

Removed hardcoded checks for maven and gradle build tools.
Removed implicit assumption that there only two build tools: maven and gradle.
Enhanced IBuildSupport usage so that we may add more build tools such as bazel.

Signed-off-by: Dmitry Bushenko d.bushenko@gmail.com

Signed-off-by: Dmitry Bushenko <d.bushenko@gmail.com>
@eclipse-ls-bot
Copy link

Can one of the admins verify this patch?

@@ -77,16 +77,8 @@ public static boolean isJavaProject(IProject project) {
return hasNature(project, JavaCore.NATURE_ID);
}

public static boolean isMavenProject(IProject project) {
Copy link
Contributor

Choose a reason for hiding this comment

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

i will be cautious to remove public helpers from the utility since it may be used by other extensions.

Copy link
Author

Choose a reason for hiding this comment

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

@testforstephen definitely cautious am I. The whole idea of improving IBuildSupport is to move the logic of working with particular build tool to the specific plugin. If we leave those methods in the utils class then we are leaving one more place for the maven/gradle logic. Which is bad, you know.
I understand that third-party plugins might rely on those methods. The will have to deal with the fact that they will need to improve their behavior and start relying on corresponding IBuildSupport.

Signed-off-by: Dmitry Bushenko <d.bushenko@gmail.com>
@rgrunber rgrunber self-requested a review March 10, 2021 14:15
Signed-off-by: Dmitry Bushenko <d.bushenko@gmail.com>
LeonovecSergey added a commit to LeonovecSergey/eclipse.jdt.ls that referenced this pull request Mar 16, 2021
Based on eclipse-jdtls#1674
Signed-off-by: Siarhei Leanavets <siarhei_leanavets1@epam.com>
@fbricon
Copy link
Contributor

fbricon commented Mar 18, 2021

superseded by #1694

@fbricon fbricon closed this Mar 18, 2021
LeonovecSergey added a commit to LeonovecSergey/eclipse.jdt.ls that referenced this pull request Mar 28, 2021
Based on eclipse-jdtls#1674
Signed-off-by: Siarhei Leanavets <siarhei_leanavets1@epam.com>
LeonovecSergey added a commit to LeonovecSergey/eclipse.jdt.ls that referenced this pull request Apr 13, 2021
Based on eclipse-jdtls#1674
Signed-off-by: Siarhei Leanavets <siarhei_leanavets1@epam.com>
fbricon pushed a commit that referenced this pull request Apr 14, 2021
…el (#1694)

Based on #1674

* Refactored ExtensionsExtractor
* Use the ProjectUtils static methods in cases where we know exactly which build support we want to check against the project.

Signed-off-by: Siarhei Leanavets <siarhei_leanavets1@epam.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants