Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-14 Thread via GitHub
uschindler closed issue #13638: `gradlew eclipse` no longer works URL: https://github.com/apache/lucene/issues/13638 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscr

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-14 Thread via GitHub
uschindler commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2288112074 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 rep

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-14 Thread via GitHub
dweiss commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2288034567 I compared main with 8f50976c268. When you list the plugins applied to the root project, it'll give you this: ``` class org.gradle.api.plugins.HelpTasksPlugin$Inject class or

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-14 Thread via GitHub
dweiss commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2288013013 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

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-13 Thread via GitHub
dweiss commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2287035129 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

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-13 Thread via GitHub
uschindler commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2286541359 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. -- This is an automated messag

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-12 Thread via GitHub
dweiss commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2284748381 Hi Uwe. Sorry, I was away on holidays. The cr-lf warning is caused by normalization in .gitattributes: ``` # Ignore all differences in line endings for the lock file. version

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-09 Thread via GitHub
uschindler commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2277400477 Theres also some minor issue: Since this commit, whenever I commit something to the repo it complains about line endings of `versions.toml`: > warning: in the working copy

Re: [I] `gradlew eclipse` no longer works [lucene]

2024-08-08 Thread via GitHub
uschindler commented on issue #13638: URL: https://github.com/apache/lucene/issues/13638#issuecomment-2276279148 Looks like this is caused by #13484 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL a

[I] `gradlew eclipse` no longer works [lucene]

2024-08-08 Thread via GitHub
uschindler opened a new issue, #13638: URL: https://github.com/apache/lucene/issues/13638 ### 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