You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "rmuir (via GitHub)" <gi...@apache.org> on 2025/11/02 21:16:44 UTC
[I] build: make "gradlew eclipse" idempotent [lucene]
rmuir opened a new issue, #15394:
URL: https://github.com/apache/lucene/issues/15394
### Description
Currently you can't run `gradlew eclipse` twice, on the second invocation:
```
lucene[main]$ ./gradlew eclipse
Starting a Gradle Daemon (subsequent builds will be faster)
> Task :eclipseClasspath FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':eclipseClasspath'.
> Cannot parse file '/home/rmuir/workspace/lucene/.classpath'.
Perhaps this file was tinkered with? In that case try delete this file and then retry.
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to generate a Build Scan (Powered by Develocity).
> Get more help at https://help.gradle.org.
BUILD FAILED in 22s
5 actionable tasks: 5 executed
```
It only seems to "protect" `.classpath` and not `.settings` or the other output files, I think?
It is a minor annoyance to a human, but unfriendly to automation.
As a workaround you can do `rm -f .classpath && ./gradlew eclipse` for now. Have not dug into it, but the word `tinkered` does not exist in our codebase, so the problem is coming from somewhere else :)
--
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 unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
Re: [I] build: make "gradlew eclipse" idempotent [lucene]
Posted by "dweiss (via GitHub)" <gi...@apache.org>.
dweiss closed issue #15394: build: make "gradlew eclipse" idempotent
URL: https://github.com/apache/lucene/issues/15394
--
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 unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
Re: [I] build: make "gradlew eclipse" idempotent [lucene]
Posted by "dweiss (via GitHub)" <gi...@apache.org>.
dweiss commented on issue #15394:
URL: https://github.com/apache/lucene/issues/15394#issuecomment-3479265516
The root cause is from within the eclipse plugin:
```
Caused by: java.lang.IllegalArgumentException: URI scheme is not "file"
at org.gradle.plugins.ide.eclipse.model.internal.FileReferenceFactory.fromJarURI(FileReferenceFactory.java:90)
at org.gradle.plugins.ide.eclipse.model.AbstractLibrary.<init>(AbstractLibrary.java:42)
at org.gradle.plugins.ide.eclipse.model.Library.<init>(Library.java:27)
at org.gradle.plugins.ide.eclipse.model.Classpath.load(Classpath.java:84)
at org.gradle.plugins.ide.internal.generator.XmlPersistableConfigurationObject.load(XmlPersistableConfigurationObject.java:55)
at org.gradle.plugins.ide.internal.generator.AbstractPersistableConfigurationObject.load(AbstractPersistableConfigurationObject.java:37)
at org.gradle.plugins.ide.internal.generator.generator.PersistableConfigurationObjectGenerator.read(PersistableConfigurationObjectGenerator.java:32)
at org.gradle.plugins.ide.internal.generator.generator.PersistableConfigurationObjectGenerator.read(PersistableConfigurationObjectGenerator.java:28)
at org.gradle.plugins.ide.api.GeneratorTask.generate(GeneratorTask.java:88)
... 118 more
```
I guess it doesn't like that gradle's javadoc (that we add) being https, which is dumb if eclipse itself allows it.
We can try to remove those files beforehand but will this not wipe someones intentional changes?
--
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 unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
Re: [I] build: make "gradlew eclipse" idempotent [lucene]
Posted by "rmuir (via GitHub)" <gi...@apache.org>.
rmuir commented on issue #15394:
URL: https://github.com/apache/lucene/issues/15394#issuecomment-3480582641
> We can try to remove those files beforehand but will this not wipe someones intentional changes?
The user ran `gradlew eclipse` though. I see no reason to treat .classpath as precious but not .settings. Same goes for .class files that get generated when you compile the code?
--
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 unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org