Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

FileBufferFunctions.testGetFileStoreAnnotationModel fails when ran from Eclipse

Abierto
#3,828 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
java
Área
testing

Línea de trabajo

Start with FileBufferFunctions.java at the failing assertion and inspect the MANIFEST.MF used by the filebuffers tests, along with the extending test classes named in the issue. Run FileBuffersForFilesInLinkedFolders from Eclipse and compare its bundle availability with the test setup; the issue reports that adding org.eclipse.ui.editors to the manifest makes the test pass. Check the linked PDE issues before deciding whether that is the complete fix.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Run e.g. org.eclipse.core.filebuffers.tests.FileBuffersForFilesInLinkedFolders, observe:

org.opentest4j.AssertionFailedError: expected: not <null>
	at org.eclipse.core.filebuffers.tests.FileBufferFunctions.testGetFileStoreAnnotationModel(FileBufferFunctions.java:1297)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.Optional.ifPresent(Optional.java:178)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
	at java.base/java.util.stream.IntPipeline$1$1.accept(IntPipeline.java:180)
	at java.base/java.util.stream.Streams$RangeIntSpliterator.forEachRemaining(Streams.java:108)
	at java.base/java.util.Spliterator$OfInt.forEachRemaining(Spliterator.java:712)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
	at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
	at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)

There is this code:

	@Override
	protected Class<IAnnotationModel> getAnnotationModelClass() throws Exception {
		Bundle bundle= Platform.getBundle("org.eclipse.ui.editors");
		return bundle != null ? IAnnotationModel.class : null;
	}

In several of the extending test cases:

tests/org.eclipse.core.filebuffers.tests/src/org/eclipse/core/filebuffers/tests/FileBuffersForFilesInLinkedFolders.java:                Bundle bundle= Platform.getBundle("org.eclipse.ui.editors");
tests/org.eclipse.core.filebuffers.tests/src/org/eclipse/core/filebuffers/tests/FileBuffersForLinkedFiles.java:         Bundle bundle= Platform.getBundle("org.eclipse.ui.editors");
tests/org.eclipse.core.filebuffers.tests/src/org/eclipse/core/filebuffers/tests/FileBuffersForWorkspaceFiles.java:              Bundle bundle= Platform.getBundle("org.eclipse.ui.editors");
tests/org.eclipse.core.filebuffers.tests/src/org/eclipse/core/filebuffers/tests/FileStoreFileBuffersForWorkspaceFiles.java:             Bundle bundle= Platform.getBundle("org.eclipse.ui.editors");

But the bundle org.eclipse.ui.editor is not in the MANIFEST.MF. Adding it there does make the test pass.

Considering the following, no idea how to fix such problems:

Likely related to: https://github.com/eclipse-pde/eclipse.pde/issues/1999, https://github.com/eclipse-pde/eclipse.pde/issues/2082

Lenguaje dominante
Java
Estrellas
124
Forks
269
Merge medio
1 d 19 h
PR fusionados (30 d)
60

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eclipse-platform/eclipse.platform.ui

Todos los issues de eclipse-platform/eclipse.platform.ui

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.