LinkageError with 2024-09 staging release #116
Comments
|
@merks any ideas what's going on here? |
|
Some additional information from my side, as I've just tested it on two other machines: The problem seems to be exclusive to Windows 11 as I haven't been able to reproduce this on Linux. Very weird... |
|
II notice there are two versions of this library:
I also notice that if I remove mpc there is only one version:
And in that case there is no linkage exception. But I find the content of the ECF release strange:
Somehow the ECF release don't just contain content from the most recent Orbit release as I would have expected:
Looks like that needs to be revisited again too. 😢 In any case, it appears that MPC's use of an older library version is the cause of the problem or more certainly is contributing to the problem. |
|
My guess would be that because the target platform uses the 4.32 repository which has older ECF content that older ECF dependencies can creep in:
|
|
Thanks for reporting this problem and for bringing this to my attention! 💟 I hope that we can nip this problem in the bud before M1 roles out the door and that MPC can roll out these changes as soon as possible: |
|
@merks two questions:
|
|
There is nothing for ECF to do for this issue. I think it should be closed. I have the following PR to update ECFs dependencies properly: A snapshot build for that would be awesome... |
I will produce one today. Our ci instance seems very slow to respond today (ui), however: @merks do you know if this is a widespread problem...or just with our ci instance? |
|
The problems with ci instances seem widespread to me. Some instances are fine while others are slow and fail for strange reasons. I've had no end of problems for the last days... |
@merks: Please color our instance (link above) in the latter category. Our build typically takes less than 15 minutes total and it's not accepting any new jobs at all (pending state for last couple of hours). Until this instance accepts and processes new jobs I can't produce a snapshot. |
|
When in doubt, create an issue: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4800 The good news is that with MPC's M1 contribution, the linkage problem is fixed. |
|
Hi @merks Good news: Our ci instance is running ok now Here's the failed run https://ci.eclipse.org/ecf/job/ecf-github.master/112/ From the console output, it seems that this is the reason for failure...i.e. a dependency on jakarta.servlet that isn't in target platform? Thanksinadvance. [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-repository-plugin:4.0.7:assemble-repository (default-assemble-repository) on project org.eclipse.ecf.releng.repository: Cannot resolve dependencies of project org.eclipse.ecf:org.eclipse.ecf.releng.repository:eclipse-repository:3.15.2-SNAPSHOT |
|
I did successfully run the build locally. I’ll have a look tomorrow during the day. |
|
It's an odd problem. The target platform in the IDE shows this content:
The local build uses that version:
But the error message is about 6.0.0: But I look at what's build, and that's different from the above error
So as I write this, it screams out, this is an API baseline replacement problem. |
- This is needed so that baseline replacement doesn't try to replace the newly built feature which includes jakarta.servlet-api version 6.1.0 with the previous version that includes jakarta.servlet-api version 6.0.0. eclipse#116
|
Thanks @merks . Here is the 3.15.2 snapshot build |
|
Thanks. I've updated SimRel: eclipse-simrel/simrel.build#461 And the platform is in the works: |
This is something that I noticed a few days ago, when trying to check out a project using Oomph.
Stack trace:
To reproduce, use the Oomph installer and set "Staging (2024-09) as product version.
The setup fails halfway through, with the error mentioned above.
The error doesn't show up with the 2024-06 release, so something must have changed between those releases that's causing this issue. Perhaps a different project also migrated to the HttpClient5, causing the classes to be loaded somewhere else?
The text was updated successfully, but these errors were encountered: