-
Notifications
You must be signed in to change notification settings - Fork 35
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
Support Edit Starters for gradle project #113
Comments
The README is wrong. The command is enabled only for pom.xml for the moment, see To enable Gradle support, we need to 1) parse If there's simple and concise |
I prefer gradle project to maven project. Please fix this issue asap. |
I think this is a needed feature, lets try to upvote this issue to get it implemented. |
Any plans on fixing this? |
Any help is welcome, PRs, ideas, etc. |
I'd like
Edit Starters
command to support gradle projects. It appears to only support maven projects (searches for pom.xml) files. It says it works by clicking on build.gradle and runningEdit Starters
, but I don't believe it works.I think the gradle language server could help in this regard. I posted a question to their repository to ask them about it. It seems like the parsing of gradle files is something that we wouldn't want to just do a search and replace on. It seems like it would be straightforward based upon the dependencies that it pulls down. i.e. we'd need to map runtime -> runtimeOnly, compile -> compileOnly, etc. and handle the toRemove and to Add by appropriately.
How should it decide to handle the maven or gradle project? Should we only look for build.gradle if pom.xml can't be found? We could change the error msg to cannot find pom.xml or build.gradle. If it finds build.gradle, we'll use the language server to remove unwanted dependencies and add needed ones.
Is this something we can implement?
The text was updated successfully, but these errors were encountered: