Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CXF-8671: Support Jakarta EE 10 #1201

Merged
merged 28 commits into from
Nov 6, 2023
Merged

CXF-8671: Support Jakarta EE 10 #1201

merged 28 commits into from
Nov 6, 2023

Conversation

karlvr
Copy link
Contributor

@karlvr karlvr commented Mar 22, 2023

Work in progress on supporting Jakarta EE 10.

I have chosen to use the Jakarta EE BOM to manage the versions of all of the Jakarta EE 10 API dependencies in one fell swoop, and to hopefully ensure that CXF is compatible with the specification.

Remaining

  • Jakarta RESTful Web Services 3.1 support in RuntimeDelegateImpl and ResponseImplTest requires actually implementing the bootstrap APIs
  • EntityPartImpl and EntityPartBuilderImpl need proper integration with registered MessageBodyReader and MessageBodyWriter
  • While a straight mvn package succeeds (with the two above classes with stub implementations) the mvn -Pfastinstall,everything fails with some missing dependencies (WIP).
  • mvn -Pfastinstall,everything succeeds
  • Test failures.

@karlvr
Copy link
Contributor Author

karlvr commented Mar 22, 2023

Current test failures:

[INFO] Running org.apache.cxf.jaxrs.utils.ResourceUtilsTest
[INFO] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 s - in org.apache.cxf.jaxrs.utils.ResourceUtilsTest
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR] org.apache.cxf.jaxrs.impl.RetryAfterHeaderProviderTest.test[retry after Sun Nov 03 08:49:37 2002 is duration of PT24884H49M37S from 2000-01-01 00:00:00.000]
[ERROR]   Run 1: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[ERROR]   Run 2: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[ERROR]   Run 3: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[ERROR]   Run 4: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[INFO] 
[ERROR] org.apache.cxf.jaxrs.impl.RetryAfterHeaderProviderTest.test[retry after Sun Nov 3 08:49:37 2002 is duration of PT24884H49M37S from 2000-01-01 00:00:00.000]
[ERROR]   Run 1: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[ERROR]   Run 2: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[ERROR]   Run 3: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[ERROR]   Run 4: RetryAfterHeaderProviderTest.test:73 
Expected: is <PT24884H49M37S>
     but: was <PT24883H49M37S>
[INFO] 
[INFO] 
[ERROR] Tests run: 1084, Failures: 2, Errors: 0, Skipped: 1

I wonder if this could be because of my GMT+13 timezone.

@amarkevich
Copy link
Contributor

Apache CXF Code Generation Maven2 Plugins .......... FAILURE
https://github.com/apache/cxf/actions/runs/4485519042

@karlvr
Copy link
Contributor Author

karlvr commented Mar 23, 2023

@amarkevich thank you, that particular problem was resolved in dd20aee. This PR still won't compile due to the RuntimeDelegateImpl and ResponseImplTest pieces not being done yet. Locally I've implemented with TODOs :-) WIP.

@karlvr
Copy link
Contributor Author

karlvr commented Mar 23, 2023

The org.apache.cxf.jaxrs.impl.RetryAfterHeaderProviderTest test failure I referenced above was because the test did not correctly account for daylight time. I've pushed a fix for that test, which would have broken in the main branch.

@karlvr
Copy link
Contributor Author

karlvr commented Mar 23, 2023

Current test failures that I'm struggling with... I believe all of these failures are related to xml schemas with out a target namespace. It seems that we're not finding the complex type when there's no namespace, but we find it fine when there is. Is anyone able to help understand this?

[ERROR] Tests run: 41, Failures: 0, Errors: 12, Skipped: 0, Time elapsed: 3.612 s <<< FAILURE! - in org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest
[ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testNoTargetNamespace  Time elapsed: 0.283 s  <<< ERROR!
java.lang.RuntimeException: Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
	at org.apache.cxf.tools.wadlto.jaxrs.SourceGenerator$InnerErrorListener.error(SourceGenerator.java:2081)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at org.apache.cxf.common.util.ReflectionInvokationHandler.invoke(ReflectionInvokationHandler.java:88)
	at jdk.proxy2/jdk.proxy2.$Proxy12.error(Unknown Source)
	at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.error(SchemaCompilerImpl.java:303)
	at com.sun.tools.xjc.util.ErrorReceiverFilter.error(ErrorReceiverFilter.java:55)
	at com.sun.xml.xsom.impl.parser.ParserContext$2.error(ParserContext.java:176)
	at com.sun.xml.xsom.impl.parser.ParserContext$1.reportError(ParserContext.java:154)
	at com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.reportError(NGCCRuntimeEx.java:149)
	at com.sun.xml.xsom.impl.parser.DelayedRef.resolve(DelayedRef.java:80)
...
[ERROR] Errors: 
[ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testCodeGenDigit
[ERROR]   Run 1: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 2: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 3: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 4: JAXRSContainerTest.testCodeGenDigit:843 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[INFO] 
[ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testCodeGenHyphen
[ERROR]   Run 1: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 2: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 3: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 4: JAXRSContainerTest.testCodeGenHyphen:821 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[INFO] 
[ERROR] org.apache.cxf.tools.wadlto.jaxrs.JAXRSContainerTest.testNoTargetNamespace
[ERROR]   Run 1: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 2: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 3: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'
[ERROR]   Run 4: JAXRSContainerTest.testNoTargetNamespace:70 » Runtime Error compiling schema from WADL : undefined simple or complex type 'testCompositeObject'

@reta
Copy link
Member

reta commented Mar 26, 2023

@karlvr apologies I do not have time right now to look at the issue, but I just glance through the changes and the first thing I run into is that dependencies part needs some work, for example saaj-impl needs a bump 3.0.0, probably there are few others too.

[1] https://github.com/apache/cxf/pull/1201/files#diff-b5a06276719e759fe07dfe6f75d781be5f83d2215179d82bdb195ad035348214L179

@karlvr karlvr force-pushed the jakartaee10 branch 4 times, most recently from 91c837e to 7ba7011 Compare April 2, 2023 21:51
@karlvr
Copy link
Contributor Author

karlvr commented Apr 3, 2023

@reta thank you, I've upgraded a few more dependencies ... I still have the namespace issues, and the implementation for RuntimeDelegateImpl is still required. I don't think I'm able to proceed from this point as the test failures / implementation required is beyond my knowledge of CXF. When you or someone else gets a chance to take a look it will be great to get past this point and I'll help where I can!

@karlvr
Copy link
Contributor Author

karlvr commented Apr 12, 2023

Another few wee code contributions... I implemented a basic SeBootstrap.Configuration and builder, and I've added stub implementations for the bootstrap APIs in RuntimeDelegate... maybe CXF doesn't need to support the bootstrapping immediately, or someone else is definitely better positioned to implement that!

I've taken a stab at the EntityPart implementation and builder. The missing piece for me is how to get access to registered MessageBodyReader and Writer implementations in the context of the EntityPart.Builder... I've used ProviderFactory with a null Message for the moment. I am also guessing that somewhere elsewhere in CXF we will need support for EntityPart...

@reta
Copy link
Member

reta commented Apr 12, 2023

Another few wee code contributions...

Thanks @karlvr , I think it would have unblocked you a bit on the compilation side, but is it now difficult to track what we need to implement, it would be helpful (to be fair) to get rid of the stubs if possible (we would have to implement the spec to be compliant).

@karlvr
Copy link
Contributor Author

karlvr commented Apr 12, 2023

@reta yes, I agree. I was holding off on committing them for that reason. It is limited to the RuntimeDelegateImpl class. I have listed this issue in the (newly convert to a) checklist in the PR description. Is that enough to keep track of it at this stage? There's also the case of the EntityPartBuilderImpl where I've implemented something that I'm pretty sure needs improvements that I'm not sure how to proceed on... I could comment that code out. It's only those two bits that are not just changing versions and search-replace things!

@reta
Copy link
Member

reta commented Apr 12, 2023

@reta yes, I agree. I was holding off on committing them for that reason. It is limited to the RuntimeDelegateImpl class. I have listed this issue in the (newly convert to a) checklist in the PR description. Is that enough to keep track of it at this stage?

I was going through the spec and was sketching some very basic implementation (it is very likely some work is repeated and is in conflict now). Let's keep it like that but I would be curious to know if you are planning to implement this part of the specification in full so we won't be duplicating the effort. Thank you.

bom/pom.xml Outdated
@@ -20,7 +20,7 @@
<parent>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf</artifactId>
<version>4.0.1-SNAPSHOT</version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@karlvr I've bumped the version to 4.1.0 to simplify branch switches, it expanded the changeset quite a bit, apologies for that

@karlvr
Copy link
Contributor Author

karlvr commented Apr 22, 2023

@reta I've been on a brief holiday! I don't believe I know enough about the ins-and-outs of CXF to contribute to this stage of the PR I think... your implementations look great, and I am really looking forward to seeing it all come together. This is the final piece of my puzzle, or the final so far.

@karlvr
Copy link
Contributor Author

karlvr commented Oct 26, 2023

@reta Hi, how are you getting on! Is there anything more I can do to help out?

I received a PR on my original branch; it looks good to me but I think you'd be best to consider it as it's more of a behaviour change than the other EE10 conversions I've looked at.

@reta
Copy link
Member

reta commented Oct 26, 2023

@reta Hi, how are you getting on! Is there anything more I can do to help out?

Thanks a lot @karlvr , I sadly haven't gotten the support to streamline Jakarta EE 10 development, but it is increasingly difficult to maintain such a large pull request open for long. I was thinking about creating a separate feature branch so we could work on the migration, merge changes incrementally and have CI running.

[1] https://www.mail-archive.com/dev@cxf.apache.org/msg19805.html

@karlvr
Copy link
Contributor Author

karlvr commented Oct 28, 2023

@reta I’m totally happy with whatever you need to do to make it easy. I’m happy to rebase on top of HEAD if that’s useful. I fear it’s pretty small. I’m unclear on what is required to continue… I’d be happy to help with a plan and perhaps to execute on it if that seems useful and fun.

@reta reta changed the base branch from main to CXF-8671 October 31, 2023 00:27
It didn’t respect the Jakarta EE 10 BOM for some reason, and it doesn’t (yet?) appear to be necessary
@reta
Copy link
Member

reta commented Oct 31, 2023

@reta I’m totally happy with whatever you need to do to make it easy. I’m happy to rebase on top of HEAD if that’s useful. I fear it’s pretty small. I’m unclear on what is required to continue… I’d be happy to help with a plan and perhaps to execute on it if that seems useful and fun.

Thanks a lot @karlvr ! So what I've done:

  • created a branch called CXF-8671 where I just bumped the version to 4.1.0-SNAPSHOT (so all unrelated changes are gone from this pull request)
  • retargeted pull request to CXF-8671 instead of main so we could actually merge it and continue to work iteratively

There are few leftovers on my side (related to JAX-RS) but there is only one thing I wanted to change: the usage of Jakarta EE BOM simplifies a few things but really complicates dependency updates, especially with respect to security fixes. I think we should be better of continuing to manage individual component versions instead (it happens all the time that we need to update components, without need to wait for BOM release which usually takes much longer).

@reta
Copy link
Member

reta commented Nov 1, 2023

@karlvr I think we are in good shape to merge it into integration branch (and continue work), any objections from your side? thank you!

@ffang
Copy link
Contributor

ffang commented Nov 3, 2023

Hi @karlvr @reta ,

Thanks for what you have done here, very nice!

And for the Servlet API 6.0 support of EE10, we need to upgrade to use Jetty 12 and Undertow 2.3.x, and I've been working on it. The working on Jetty12 upgrade took me a while as the Jetty12 API changed a lot. I think I've got most issues resolved for Servlet API 6.0 upgrade, and I just pushed my working branch here
https://github.com/apache/cxf/tree/servlet-6

I rebased this branch against branch CXF-8671 you guys have worked on, and I am gonna polish servlet-6 branch a little bit and then send a PR against CXF-8671.

Best Regards
Freeman

@reta
Copy link
Member

reta commented Nov 3, 2023

Thanks for what you have done here, very nice!

Thanks @ffang ! I think we got Undertow 2.3.x working already (but not Jetty 12), waiting for @karlvr to give a green light to merge into integration branch so we could move forward!

@karlvr
Copy link
Contributor Author

karlvr commented Nov 6, 2023

@karlvr I think we are in good shape to merge it into integration branch (and continue work), any objections from your side? thank you!

@reta absolutely none, I'm excited :-)

@reta reta marked this pull request as ready for review November 6, 2023 20:03
@reta reta merged commit 283f69e into apache:CXF-8671 Nov 6, 2023
@rzo1
Copy link
Contributor

rzo1 commented Nov 8, 2023

Thank you all ;-) - we are also excited to test with a SNAPSHOT ;-)

reta added a commit that referenced this pull request Apr 15, 2024
* CXF-8671: Support Jakarta EE 10. Initial commit to prepare the Jakarta EE integration branch

* CXF-8671: Support Jakarta EE 10 (#1201)

* Update dependencies to Jakarta EE 10

* Remove unnecessary dependency on jakarta.xml.bind-api

It didn’t respect the Jakarta EE 10 BOM for some reason, and it doesn’t (yet?) appear to be necessary

* Servlet API 6.0.0

* Jakarta XML Binding 4.0

* Jakarta Context Dependency Injection 4.0

* Fix Maven dependencies

* Jakarta RESTful Web Services 3.1

* Update Jakarta EE dependencies for codegen-plugins integration tests

* Add missing jakarta.xml.bind-api dependencies for codegen-plugin maven-invoker-plugin

* Correct RetryAfterHeaderProviderTest not accounting for host daylight time

getRawOffset() returns the offset for standard time, which means these tests fail when the default timezone is observing daylight time.

* Upgrade saaj-impl

* Upgrade undertow

* Upgrade istack

* Placeholders for bootstrap API

* EntityPart

* Implement RuntimeDelegateImpl

* Partially implement TLS/SSL in SE bootstrap (needs some work on CXF engines)

* Fix cxf-tools-wadlto-jaxrs test cases

* Update Spring Boot to 3.1.0, Spring LDAP to 3.1.0, Spring Security to 6.1.0

* docs: Fix BUILDING.txt fastinstall line

* Fix compilation and checkstyle issues

* Update Hibernate to 6.2.9.Final

* Update Hibernate to 6.3.1.Final

* Refactor EntityPartBuilderImpl & EntityPartImpl

* Replace JakarteEE 10 BOM with indvidual component versions to simplify patching and minor updates

* Fixed CDI and Security test cases

* Update Weld to 5.1.2.Final

* Switch JSON-P/JSON-B implementation and fix test cases

---------

Co-authored-by: Andriy Redko <drreta@gmail.com>

* Update Arquillian to 1.8.0.Final

* Update Apache Camel to 4.1.0

* Move to Spring Boot 3.2.0 baseline (#1534)

* Update Hibernate to 6.4.0.Final

* Update Apache Camel to 4.2.0

* Update JAXB Runtime (Glassfish) to 4.0.0

* Update SAAJ impl to 3.0.3

* Bump com.sun.xml.ws:jaxws-rt from 3.0.2 to 4.0.2 (#1568)

Bumps com.sun.xml.ws:jaxws-rt from 3.0.2 to 4.0.2.

---
updated-dependencies:
- dependency-name: com.sun.xml.ws:jaxws-rt
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump com.sun.istack:istack-commons-tools from 4.1.1 to 4.2.0 (#1576)

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update Netty to 4.1.104.Final

* Update Spring LDAP to 3.2.1

* Dependency updates

* Bump org.eclipse.persistence:org.eclipse.persistence.moxy (#1583)

Bumps [org.eclipse.persistence:org.eclipse.persistence.moxy](https://github.com/eclipse-ee4j/eclipselink) from 2.7.6 to 4.0.2.
- [Release notes](https://github.com/eclipse-ee4j/eclipselink/releases)
- [Commits](eclipse-ee4j/eclipselink@2.7.6...4.0.2)

---
updated-dependencies:
- dependency-name: org.eclipse.persistence:org.eclipse.persistence.moxy
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump cxf.zipkin-reporter.version from 2.17.0 to 2.17.1 (#1587)

Bumps `cxf.zipkin-reporter.version` from 2.17.0 to 2.17.1.

Updates `io.zipkin.reporter2:zipkin-reporter-brave` from 2.17.0 to 2.17.1
- [Release notes](https://github.com/openzipkin/zipkin-reporter-java/releases)
- [Changelog](https://github.com/openzipkin/zipkin-reporter-java/blob/master/RELEASE.md)
- [Commits](openzipkin/zipkin-reporter-java@2.17.0...2.17.1)

Updates `io.zipkin.reporter2:zipkin-sender-urlconnection` from 2.17.0 to 2.17.1
- [Release notes](https://github.com/openzipkin/zipkin-reporter-java/releases)
- [Changelog](https://github.com/openzipkin/zipkin-reporter-java/blob/master/RELEASE.md)
- [Commits](openzipkin/zipkin-reporter-java@2.17.0...2.17.1)

---
updated-dependencies:
- dependency-name: io.zipkin.reporter2:zipkin-reporter-brave
  dependency-type: direct:development
  update-type: version-update:semver-patch
- dependency-name: io.zipkin.reporter2:zipkin-sender-urlconnection
  dependency-type: direct:development
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump cxf.brave.version from 5.16.0 to 5.17.0 (#1584)

Bumps `cxf.brave.version` from 5.16.0 to 5.17.0.

Updates `io.zipkin.brave:brave-context-slf4j` from 5.16.0 to 5.17.0

Updates `io.zipkin.brave:brave-instrumentation-httpclient` from 5.16.0 to 5.17.0

Updates `io.zipkin.brave:brave-instrumentation-httpasyncclient` from 5.16.0 to 5.17.0

Updates `io.zipkin.brave:brave-instrumentation-okhttp3` from 5.16.0 to 5.17.0

---
updated-dependencies:
- dependency-name: io.zipkin.brave:brave-context-slf4j
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: io.zipkin.brave:brave-instrumentation-httpclient
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: io.zipkin.brave:brave-instrumentation-httpasyncclient
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: io.zipkin.brave:brave-instrumentation-okhttp3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump org.apache.maven.plugins:maven-compiler-plugin (#1589)

Bumps [org.apache.maven.plugins:maven-compiler-plugin](https://github.com/apache/maven-compiler-plugin) from 3.11.0 to 3.12.0.
- [Release notes](https://github.com/apache/maven-compiler-plugin/releases)
- [Commits](apache/maven-compiler-plugin@maven-compiler-plugin-3.11.0...maven-compiler-plugin-3.12.0)

---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-compiler-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update Apache Camel to 4.3.0

* Bump cxf.olingo.server.version from 4.10.0 to 5.0.0 (#1597)

Bumps `cxf.olingo.server.version` from 4.10.0 to 5.0.0.

Updates `org.apache.olingo:odata-commons-api` from 4.10.0 to 5.0.0

Updates `org.apache.olingo:odata-commons-core` from 4.10.0 to 5.0.0

Updates `org.apache.olingo:odata-server-api` from 4.10.0 to 5.0.0

Updates `org.apache.olingo:odata-server-core` from 4.10.0 to 5.0.0

---
updated-dependencies:
- dependency-name: org.apache.olingo:odata-commons-api
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.apache.olingo:odata-commons-core
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.apache.olingo:odata-server-api
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: org.apache.olingo:odata-server-core
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update Spring Boot to 3.2.1

* Update Microprofile Config to 3.1

* Update Arquillian Weld Container to 3.0.2.Final

* Update Hibernate to 6.4.2.Final

* Update Spring Boot to 3.2.2

* Update to Jetty 12 (#1633)

* Update to Jetty 12

* Fix parent version of IT projects (#1663)

* Fix multiple compilation issues

* Fix javadoc generation (post Jetty 12 update)

* Update Hibernate to 6.4.3.Final

* Update Hibernate to 6.4.4.Final

* Update Micrometer to 1.12.3 and Micrometer Tracing to 1.2.3

* Update Spring LDAP to 3.2.2

* Update to Spring Boot 3.2.3

* Update UnboundID LDAP SDK for Java to 7.0.0

* Update Apache Camel to 4.4.1

* Update Apache Camel to 4.5.0

* Update Spring Cloud Eureka to 4.1.1

* Switched from wiremock-standalone to wiremock-jetty12

* Update JDK baseline to JDK-17

* Update Jetty to 12.0.8

* CXF-8993: Migrate from net.sf.cglib (cglib) to org.springframework.cglib (spring) (#1779)

* Revamped io.opentelemetry.semconv:* dependencies since Micrometer Tracing brings conflicting ones

* Adapt JAXWSServicesListingTest test cases to jetty 12.0.8+ changes

* Adapt JAXRSServicesListingTest test cases to jetty 12.0.8+ changes

* Update jakarta.json.bind-api to 3.0.1

* Bump org.jvnet.jaxb:jaxb-plugins from 3.0.1 to 4.0.6 (#1800)

Bumps org.jvnet.jaxb:jaxb-plugins from 3.0.1 to 4.0.6.

---
updated-dependencies:
- dependency-name: org.jvnet.jaxb:jaxb-plugins
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Andriy Redko <drreta@gmail.com>

* Update Project Reactor to 3.6.5

* Update Micrometer to 1.12.5

* Update Micrometer Tracing to 1.2.5

* Minor pom.xml cleanups before merging to main

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Karl von Randow <karl@xk72.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Freeman(Yue) Fang <freeman.fang@gmail.com>
Co-authored-by: Andreas Kuhtz <andreas.kuhtz@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants