Missing required bundle and Missing required capability
- Lenguaje dominante
- Java
- Estrellas
- 5.7k
- Forks
- 561
- Merge medio
- 1 d 14 h
- PR fusionados (30 d)
- 43
Descripción
Hi,
I'm working on an upgrade of the spotless plugin gradle from 5.16.0 to the latest (7.0.2).
I have this error when running the `spotlessGroovyGradle` task:
```bash
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
```
I have made a sample project from a fresh spring boot project, [the source code can be found here](https://github.com/nicolasb29/spotlestest) and the [error in this output](https://github.com/nicolasb29/spotlestest/actions/runs/13759762141/job/38473222042#step:5:32). I also made test on Ubuntu and MacOS and the problem is the same.
I have check there issues but it didn't work:
- #2089
- #1860
i.e.: the format.gradle file is on a separate file because in my case it's hosted on a central repository.
Guía de contribución
Línea de trabajo
Comienza con el proyecto de ejemplo y su archivo format.gradle independiente; después, ejecuta la tarea spotlessGroovyGradle usando la actualización de Spotless de 5.16.0 a 7.0.2. Compara la salida de GitHub Actions en Ubuntu y macOS, y revisa los issues #2089 y #1860. Se considera terminado cuando la tarea se ejecuta sin errores por falta de bundle, capability o configuración.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- groovy, java, spring-boot
- Área
- build-system
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100