Dependency Updates

[eclipse-releng-bot]

The content of the target eclipse-sdk-prereqs.target was updated

Please review the changes and merge if appropriate, or cherry pick individual updates.

The following maven artifacts have been updated:

• org.eclipse.jetty.toolchain:jetty-servlet-api:jar:4.0.6 has been updated to version 4.0.8
  • additionally requires java.package; java.io 0.0.0 compared to the previous version
  • additionally requires java.package; java.lang 0.0.0 compared to the previous version
  • additionally requires java.package; java.lang.annotation 0.0.0 compared to the previous version
  • additionally requires java.package; java.lang.invoke 0.0.0 compared to the previous version
  • additionally requires java.package; java.lang.reflect 0.0.0 compared to the previous version
  • additionally requires java.package; java.net 0.0.0 compared to the previous version
  • additionally requires java.package; java.security 0.0.0 compared to the previous version
  • additionally requires java.package; java.text 0.0.0 compared to the previous version
  • additionally requires java.package; java.util 0.0.0 compared to the previous version
  • additionally requires java.package; java.util.function 0.0.0 compared to the previous version

[merks]

/request-license-review

[github-actions]

/request-license-review

License review requests:

• maven/mavencentral/biz.aQute.bnd/biz.aQute.tester.junit-platform/7.2.1
• maven/mavencentral/org.bndtools/org.bndtools.templating/7.2.1

After all reviews have concluded, re-run the license-vetting check from the Github Actions web-interface to update its status.

Workflow run (with attached summary files):
https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/actions/runs/20948159246

[merks]

FYI, I left a comment on https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/25569 that will hopefull get it approve quickly.

[laeubi]

It looks like the filtering for unwanted versions is broken, might be a regression from suing the Tycho snapshot.

[laeubi]

I have checked this locally now with Tycho 5.0.1 I get:

update Dependency {groupId=org.eclipse.jetty.toolchain, artifactId=jetty-servlet-api, version=4.0.6, type=jar} to version 4.0.8

with 5.0.2-SNAPSHOT I get:

update Dependency {groupId=org.slf4j, artifactId=slf4j-api, version=2.0.17, type=jar} to version 2.1.0-alpha1
update Dependency {groupId=org.slf4j, artifactId=slf4j-simple, version=2.0.17, type=jar} to version 2.1.0-alpha1
update Dependency {groupId=org.junit.jupiter, artifactId=junit-jupiter-api, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.jupiter, artifactId=junit-jupiter-engine, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.jupiter, artifactId=junit-jupiter-migrationsupport, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.jupiter, artifactId=junit-jupiter-params, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.platform, artifactId=junit-platform-commons, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.platform, artifactId=junit-platform-engine, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.platform, artifactId=junit-platform-launcher, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.platform, artifactId=junit-platform-suite-api, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.platform, artifactId=junit-platform-suite-engine, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=org.junit.vintage, artifactId=junit-vintage-engine, version=6.0.2, type=jar} to version 6.1.0-M1
update Dependency {groupId=jakarta.activation, artifactId=jakarta.activation-api, version=2.1.4, type=jar} to version 2.2.0-M1
update Dependency {groupId=jakarta.inject, artifactId=jakarta.inject-api, version=2.0.1, type=jar} to version 2.0.1.MR

So it seems a regression in Tycho 5.0.2 that somehow the filter file is no longer evaluated.

[laeubi]

@akurtakov the problematic change seems to be this one that makes the version rules no longer be applied:

• eclipse-tycho/tycho@dfbbd43

I'm currently looking into a fix...

[laeubi]

Now everything is back to expected state!

[laeubi]

The actual issue is a bit nasty, the source bundle itself has the same OSGi data as the original bundle:

• Source JAR contains full OSGi manifest causing P2 resolution conflicts jetty/jetty-servlet-api#40

this causes P2 to resolve the source bundle for the classpath what obviously will not work!

I currently try to implement a workaround for Tycho ...