pvillard31 opened a new pull request, #10249:
URL: https://github.com/apache/nifi/pull/10249
# Summary
NIFI-14910 NIFI-14911 NiFi - Upgrade Jetty to 12.1.0 and move to Jakarta EE11
**Important notes**:
- Given that Spring Boot 3.x still relies on Jetty 12.0.x, it is not
possible to upgrade NiFi Registry to use Jetty 12.1.0. This will be a separate
effort that is tracked by NIFI-14912 & NIFI-14913. In the meantime, the pom
dependencies have been adjusted to move NiFi to Jetty 12.1.0 and Jakarta EE11
while NiFi Registry remains on Jetty 12.0.25 and Jakarta EE10.
- This PR is currently as a draft to allow some time for reviewers. But also
because it is worth mentioning that:
- the Jersey dependency is currently set to `4.0.0-M3` that was released
earlier today. No clarity as to when the final `4.0.0` release is expected.
- the swagger codegen plugin in Toolkit API is still using Jersey 3 as the
configured library
(https://github.com/apache/nifi/blob/main/nifi-toolkit/nifi-toolkit-api/pom.xml#L89)
given that Jersey 4 is not an option yet - I do not believe however that this
is an issue
- I have not moved the JMS bundle from `javax.jms-api` to `jakarta.jms-api`
as this would be a breaking change for users with existing JMS components where
a specific JMS client is provided as part of the configuration. This is
something we can evaluate later.
- Jakarta EE11 brings support for Virtual Threads with Java 21. I have
changed the thread pool for the UI to use virtual threads. I have considered
doing the same for the cluster replication requests but I prefer to wait for
thoughts on this topic. This is something that could also be considered for
`ListenHTTP` and `HandleHTTPRequest/Response` components.
- Went through NOTICE files / docs to clean up references and make sure we
are aligned with latest. There is a lot of changes related to NOTICE files...
sorry to the reviewers, I tried to do my best to make sure we are back to a
good state
**Testing**:
- Beyond confirming that the full build with system tests is green, some
additional manual testing has been done to confirm proper behavior of the UI
with custom UIs, content viewer, documentation rendering, etc.
- Confirmed that NiFi Registry is working with Jetty 12.0.25/EE10
# Tracking
Please complete the following tracking steps prior to pull request creation.
### Issue Tracking
- [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue
created
### Pull Request Tracking
- [X] Pull Request title starts with Apache NiFi Jira issue number, such as
`NIFI-00000`
- [X] Pull Request commit message starts with Apache NiFi Jira issue number,
as such `NIFI-00000`
### Pull Request Formatting
- [X] Pull Request based on current revision of the `main` branch
- [X] Pull Request refers to a feature branch with one commit containing
changes
# Verification
Please indicate the verification steps performed prior to pull request
creation.
### Build
- [X] Build completed using `./mvnw clean install -P contrib-check`
- [X] JDK 21
### Licensing
- [X] New dependencies are compatible with the [Apache License
2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License
Policy](https://www.apache.org/legal/resolved.html)
- [X] New dependencies are documented in applicable `LICENSE` and `NOTICE`
files
### Documentation
- [X] Documentation formatting appears as expected in rendered files
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
