servlet profile added, covers javax.servlet only #57
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
For my application I'd like to migrate javax.servlet only. Other packages, such as javax.mail are part of my web application, thus no affected by the tomcat upgrade.
|
Would be nice if there was any feedback on this issue. |
|
This looks okay to me. I'll give it a test. |
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.
The profile TOMCAT does not work for me. For instance it converts javax.mail, which is provided by my web application, not Tomcat. So it is not affected by the upgrade of Tomcat 9 -> 10.1 at all. Migrating javax.mail breaks my application.
Of course I will upgrade javax.mail to jakarta.mail (and other packages) as well. But I'd like to do this step by step.