Eclipse configuration doesn't work

[dweiss]

Description

Fix it.

[dweiss]

I know what's causing it but I'm thinking of a way to fix it since gradle API doesn't seem to provide lazy providers here.

[dweiss]

@breskeby would you have any clue how to fix this? We currently collect all configurations from subprojects to create a single top-level eclipse config. I have no idea how to collect those configurations in a different way.

https://github.com/apache/lucene/blob/main/build-tools/build-infra/src/main/java/org/apache/lucene/gradle/plugins/ide/EclipseSupportPlugin.java#L184-L190

[uschindler]

Can we delay this to be executed during task action? I think we did something similar in the past!

[uschindler]

Ah, this is generally disallowed:

Gemini AI says:

Configuration Access: This error happens when a task tries to resolve a configuration (like a dependency classpath) that belongs to another project, or in a way that isn't synchronized with the Gradle daemon's internal state.

So we can't resolve the configuration of anothe rproject anymore in Gradle 9. Can we use a lock as suggested by the error message? Normally a lock won't hurt, because you won't call eclipse task as part of a larger build.

Uwe

[dweiss]

I don't think you do this explicitly - it's some internal gradle machinery. Still thinking.

[uschindler]

It looks like this was already discovered by the Eclipse plugin itsself but fixed there in Gradle 9.0. I skimmed through this patch, but I did not figure out where there is a "lock" involved. The term "lock" does not appear in the PR's source code.

gradle/gradle#34064 with this PR: gradle/gradle#34098

But it may be helpful. The code looks like spaghetti with beer-sauce to me.

[uschindler]

FYI, after reading the comments around the issue above, I tried:

C:\....> gradlew --no-parallel eclipse
Starting a Gradle Daemon (subsequent builds will be faster)

> Task :luceneEclipseJdt
Eclipse config for Java 25 written with ECJ errors configured as 'warning'. Change by altering the build option 'eclipse.errors' to ignore/warning/error: -Peclipse.errors=ignore
To edit classes of MR-JARs for a specific Java version, regenerate Eclipse options using: -Peclipse.javaVersion=24

BUILD SUCCESSFUL in 33s
10 actionable tasks: 3 executed, 7 up-to-date

So this is a good workaround for now.

[uschindler]

It looks like this is the magic: bar = ((ProjectInternal) p).getOwner().fromMutableState(project -> { dosomething and return foo with beer sauce }

[dweiss]

Can you see if this PR works, Uwe? #15252