You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Missing required bundle and Missing required capability #2445
Ran into the same warnings on v7.0.4 and the solution given in #2089 worked for me. Made sure both mavenCentral() and gradlePluginPortal() were in my repositories list. Nuked the .gradle folder in my project workspace and re-ran Gradle. Issue went away.
@nicolasb29 Your sample project is not minimally reproducible. It errors due to a typo on line 20 in gradle-scripts/format.gradle. If I remove the trailing "garbage" characters from that line it does reproduce the issue.
Adding the suggested fix in #2089 to your sample repository does, indeed, remove the warnings.
Full .diff of the changes I made to your sample repository which both got it to reproduce the problem and fixed the warnings:
Locally, I have deleted the .gradle folder and run ./gradlew spotlessGroovyGradle --rerun-tasks but I still have the warning:
./gradlew spotlessGroovyGradle --rerun-tasks
Downloading https://services.gradle.org/distributions/gradle-8.12.1-bin.zip
.............10%.............20%.............30%.............40%.............50%.............60%.............70%.............80%.............90%.............100%
Welcome to Gradle 8.12.1!
Here are the highlights of this release:
- Enhanced error and warning reporting with the Problems API
- File-system watching support on Alpine Linux
- Build and test Swift 6 libraries and apps
For more details see https://docs.gradle.org/8.12.1/release-notes.html
Starting a Gradle Daemon, 1 stopped Daemon could not be reused, use --status for details
> Task :spotlessGroovyGradle
Missing required bundle org.eclipse.jdt.debug needed by [org.eclipse.jdt.launching, org.eclipse.jdt.launching.macosx]
Missing required capability osgi.extender:osgi.extender=osgi.serviceloader.processor needed by org.apache.commons.commons-logging
Missing required capability osgi.serviceloader:osgi.serviceloader=org.apache.commons.logging.LogFactory needed by org.apache.commons.commons-logging
Missing required capability osgi.serviceloader:osgi.serviceloader=org.apache.juli.logging.Log needed by org.mortbay.jasper.apache-jsp
Missing required capability osgi.extender:osgi.extender=osgi.serviceloader.processor needed by org.mortbay.jasper.apache-jsp
Recommend setting osgi.configuration.area to a directory, getDataFile will return null
Starting Groovy-Eclipse compiler resolver. Specified compiler level: unspecified
129 org.codehaus.groovy_5.0.0.v202406302347-e2406 RESOLVED
Activity
nedtwigg commentedon Mar 13, 2025
It's not good, but I believe these are just warnings. We should still fix it though :)
nicolasb29 commentedon Mar 13, 2025
The spotless is working fine, so I agree it's warning messages.
Is there a way to not display theses messages?
glektarssza commentedon Jun 11, 2025
Ran into the same warnings on v7.0.4 and the solution given in #2089 worked for me. Made sure both
mavenCentral()andgradlePluginPortal()were in myrepositorieslist. Nuked the.gradlefolder in my project workspace and re-ran Gradle. Issue went away.@nicolasb29 Your sample project is not minimally reproducible. It errors due to a typo on line 20 in gradle-scripts/format.gradle. If I remove the trailing "garbage" characters from that line it does reproduce the issue.
Adding the suggested fix in #2089 to your sample repository does, indeed, remove the warnings.
Full
.diffof the changes I made to your sample repository which both got it to reproduce the problem and fixed the warnings:nicolasb29 commentedon Jun 11, 2025
Thank for your response.
I add both mavenCentral and gradlePluginPortal, I fix the error in the file format.gradle but force no cache in gradle task and the warning is still here
Locally, I have deleted the .gradle folder and run
./gradlew spotlessGroovyGradle --rerun-tasksbut I still have the warning:glektarssza commentedon Jun 12, 2025
Interesting. I do see this behavior in your repository, yes, but only on the first build. All builds after the first do not have this problem.
If I kill off my Gradle daemons the problem comes back.
Fix GrEclipse initialization warnings