-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
gradlew eclipse
no longer works
#13638
Comments
Looks like this is caused by #13484 |
Theres also some minor issue: Since this commit, whenever I commit something to the repo it complains about line endings of
This happens after every time I execute Gradle. |
Hi Uwe. Sorry, I was away on holidays. The cr-lf warning is caused by normalization in .gitattributes:
Which git version are you using? I ask because I don't see this message. I'm also not sure how you ended up with crlfs in that file. I'll take a look at the eclipse issue. I don't think I've changed anything that could affect it - maybe it's something indirect. |
I will check what's wrong with my toml file. I have crlf handling completely switched off in my git config. It should not touch any line endings. |
Which git version are you using? I think tidy will "clean up" those toml files by reordering them - there is a plugin for doing this. This plugin may be writing crlfs... but I don't see the warning you're getting (on Windows), which is strange! |
It's the plugin that formats version catalog - versionCatalogFormatDeps task writes back the file with the default encoding/ platform line endings. I've added a post-processing step to normalize this. I'm still surprised your git version is showing a warning about it. |
I compared main with 8f50976. When you list the plugins applied to the root project, it'll give you this:
whereas after removing the palantir plugins, it'll give you this:
I think palantir's plugin has a side-effect of applying the java conventions to the root project [1], but it's not necessary - that's why I only apply it in the eclipse task, where it is required for the jdt. I've changed java-library to java-base though, it should have a minimal surface impact. |
I have the git version shipped with TortoiseGit (rather new one, can check later). Basically the warning was not the most annoying thing, it was more that the file was reported as changed in the GUI, so whole repository gets red in its explorer overlay icons. |
Description
Hi @dweiss,
since your last cleanup, when trying to run
gradlew eclipse
it complains because the task does not exist. Looks ike the reason is that the root project no longer is a Java project, so the plugin is not applied. When commenting out theplugins.withType(JavaPlugin)
it breaks with an NPE.No sure how to fix this. We need the eclipse plugin ONLY on root project because we use it to create a global project.
Version and environment details
No response
The text was updated successfully, but these errors were encountered: