Community
Participate
Working Groups
Hello, I received today an update to Eclipse 2022-12 M1 from 2022-09 before the official release date which was not expected. I am receiving now lot of issues like java.lang.NoClassDefFoundError: org/eclipse/jface/databinding/swt/SWTObservables or java.lang.NoClassDefFoundError: org/eclipse/core/databinding/beans/PojoProperties Please fix the unwanted update issue. Regards, Catalin Chiuaru
This is really strange, but it looks like https://download.eclipse.org/releases/latest/ is no longer just 2022-09, the compositeContent.jar and compositeArtifacts.jar both direct to the 2022-12 site in progress.
@Ed - It looks like the update to https://download.eclipse.org/releases/latest/ went wrong somewhere. The "latest" release now points at 2022-12: <?compositeArtifactRepository version='1.0.0'?> <repository name="Eclipse Repository" type="org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository" version="1.0.0"> <properties size="3"> <property name="p2.timestamp" value="1663162492016"/> <property name="p2.compressed" value="true"/> <property name="p2.atomic.composite.loading" value="true"/> </properties> <children size="1"> <child location="https://download.eclipse.org/releases/2022-12/"/> </children> </repository>
It looks like the error happened when the 2022-09 release was made. The latest was set to point to 2022-12[1]. But until 2022-12 M1 was released the 2022-12 repo pointed back to 2022-09 so no one noticed the discrepency. [1] https://ci.eclipse.org/simrel/view/Releng%20jobs/job/simrel.releng.update_latest_repo/21/parameters/
I ran [2] so the latest now points to 2022-09. @Ed if you have a chance can you look at this to make sure my fix was correct and that there is nothing else to do here? Note the caching on download.eclipse.org will mean it may take a few minutes for the change to be visible. [2] https://ci.eclipse.org/simrel/view/Releng%20jobs/job/simrel.releng.update_latest_repo/22/
Thank you Catalin for taking the time to file the bug report! I think it is now resolved. Please reach out if you need any further help.
BTW the update to 2022-12 M1 shouldn't have happened, but the errors reported should not be happening in 2022-12 M1 and I have requested some more information from Catalin Chiuaru to see if we can reproduce to make sure that 2022-12 does not ship with NoClassDefFoundError problems.
Sorry about that!!