Description of problem: After adding the rest of JBoss Developer Tools 4.16.0 to a relatively clean eclipse get An internal error occurred during: "Repository registry initialization". loader constraint violation: when resolving interface method 'org.apache.maven.index.context.IndexingContext org.apache.maven.index.NexusIndexer.addIndexingContextForced(java.lang.String, java.lang.String, java.io.File, org.apache.lucene.store.Directory, java.lang.String, java.lang.String, java.util.List)' the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6 of the current class, org/eclipse/m2e/core/internal/index/nexus/NexusIndexManager, and the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5 for the method's defining class, org/apache/maven/index/NexusIndexer, have different Class objects for the type org/apache/lucene/store/Directory used in the signature (org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6, parent loader 'platform'; org.apache.maven.index.NexusIndexer is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5, parent loader 'platform') Version-Release number of selected component (if applicable): eclipse-emf-core-2.22.0-2.fc33.noarch eclipse-usage-4.16.0-2.fc33.noarch eclipse-swt-4.16-13.fc33.x86_64 eclipse-m2e-workspace-0.4.0-16.fc33.noarch eclipse-equinox-osgi-4.16-13.fc33.x86_64 eclipse-ecf-core-3.14.8-5.fc33.noarch eclipse-platform-4.16-13.fc33.x86_64 eclipse-jdt-4.16-13.fc33.noarch eclipse-emf-runtime-2.22.0-2.fc33.noarch eclipse-gef-3.11.0-13.fc33.noarch eclipse-webtools-common-3.18.0-5.fc33.noarch eclipse-p2-discovery-4.16-13.fc33.noarch eclipse-webtools-servertools-3.18.0-5.fc33.noarch eclipse-emf-xsd-2.22.0-2.fc33.noarch eclipse-webtools-sourceediting-3.18.0-5.fc33.noarch eclipse-m2e-core-1.16.1-2.fc33.noarch eclipse-mpc-1.8.3-2.fc33.noarch eclipse-pydev-7.7.0-1.fc33.x86_64 How reproducible: Always Steps to Reproduce: 1. Remove ~/.eclipse 2. Note: part of JBoss Developer Tools 4.16.0 comes installed 3. Got to Marketplace, install every feature of 4.16.0. Actual results: On restart the following mesage An internal error occurred during: "Repository registry initialization". loader constraint violation: when resolving interface method 'org.apache.maven.index.context.IndexingContext org.apache.maven.index.NexusIndexer.addIndexingContextForced(java.lang.String, java.lang.String, java.io.File, org.apache.lucene.store.Directory, java.lang.String, java.lang.String, java.util.List)' the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6 of the current class, org/eclipse/m2e/core/internal/index/nexus/NexusIndexManager, and the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5 for the method's defining class, org/apache/maven/index/NexusIndexer, have different Class objects for the type org/apache/lucene/store/Directory used in the signature (org.eclipse.m2e.core.internal.index.nexus.NexusIndexManager is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @ca944c6, parent loader 'platform'; org.apache.maven.index.NexusIndexer is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @34e347a5, parent loader 'platform') Expected results: Features are added with no errors Additional info:
java-11-openjdk-11.0.9.10-0.0.ea.fc33.x86_64
For comparison: when using upstream Eclipse 2020-09 JEE build and installing JBoss Tools 4.17.0 the error does not occur.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.