-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Tomcat10 support latest master #4342
Draft
psavidis
wants to merge
18
commits into
master
Choose a base branch
from
tomcat10_support_latest_master
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
+2,339
−41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yanavasileva
added
ci:all-as
Runs the builds for all application servers.
ci:spring-boot
Runs the integration tests for the Spring Boot starter.
ci:webapp-integration
Runs the webapp integration builds.
labels
May 14, 2024
psavidis
added
ci:skipTests
Skips tests execution in Assembly and Distro-ee stages.
labels
May 15, 2024
yanavasileva
removed
ci:all-as
Runs the builds for all application servers.
ci:spring-boot
Runs the integration tests for the Spring Boot starter.
ci:skipTests
Skips tests execution in Assembly and Distro-ee stages.
labels
May 17, 2024
psavidis
added
the
ci:skipTests
Skips tests execution in Assembly and Distro-ee stages.
label
May 21, 2024
psavidis
force-pushed
the
tomcat10_support_latest_master
branch
4 times, most recently
from
May 23, 2024 15:09
52127f5
to
e64463e
Compare
psavidis
removed
ci:skipTests
Skips tests execution in Assembly and Distro-ee stages.
ci:webapp-integration
Runs the webapp integration builds.
labels
May 24, 2024
psavidis
force-pushed
the
tomcat10_support_latest_master
branch
from
May 29, 2024 06:20
487eddf
to
b7b7328
Compare
This was referenced May 29, 2024
Description: This commit can be broken down into the following changes: - Use version.tomcat9 for tomcat 9 and version.tomcat property for tomcat 10 respectively - Add tomcat assembly config to camunda-engine-rest-jakarta - Add new module `camunda-tomcat-assembly-jakarta` which produces a tomcat 10 configured with the jakarta namespace - Add configuration to produce a tomcat webapp based on the jakarta namespace - Add configuration to tomcat distro module to output both tomcat 9 & 10 distributions Related-to: #2471
Renames include: - References in tomcat 9 xml config - The runtime directory (to differentiate it from latest tomcat) - tomcat 9 maven profiles
- Tomcat 10 starts on QA Tests and then SLF4J clashes - Add Tomcat 10 (not finished) profile for shared-engine
Other noteable changes: - same resteasy version for jakarta webapp, engine-rest Resteasy starts during webapp-integration tests against tomcat 10 but tomcat logs of the engine do not appear. As a result, the engine does not start correctly and the tests get a timeout against the rest health check
The Servlet Parameter for registering the Application was wrong. Changed it to use the jakarta namespace.
- Replaces the weld-servlet-shaded with the core artifact and includes all the jakarta API dependencies in the shrinkwrap wars - see DeploymentHelper - The above fixes weld exception messages in the logs
- Add flag that skips the surefire unit tests of the integration-tests module - Use the flag upon calling the webapp integration tests for tomcat 10
psavidis
force-pushed
the
tomcat10_support_latest_master
branch
from
May 29, 2024 10:40
b7b7328
to
75af30a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related-to: #2471