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
Usability friction with <featureManager><feature> and Jakarta EE 8 -> 10 upgrade. #7227
Comments
Thanks for opening this issue @edburns - although our doc isn't set up for the exact solution you've proposed, I've updated the Features overview page to hopefully provide better guidance determining which feature versions are attached to which MP or EE platform spec versions. @jhanders34 would you review the updated section? |
Discussed with Jared via slack and revised per his input- he approved the revision.
|
Describe the bug
I was requested to upgrade a simple EE 8 liberty app to EE 10 in this issue. Along the way, I ran into a little friction which I think a modest doc improvement could reduce.
I had to iterate through a series of error messages such as
To finally arrive at the working set of features:
All the while, I was looking to this documentation to help me. I judge a well-placed reference to a definitive guide such as "Differences between Jakarta EE N and N-1" would have helped. Here is a suggested placement and text.
Steps to Reproduce
2c8bf374c473236367beec4165ac8d951494b0e9
cd java-app
mvn clean install
Expected behavior
The Feature overview page would have helped me answer the question: "I'm using EE 10, what is the exact set of
featureName-M.m
values I need to move to given the app was at 8 beforehand?"Diagnostic information:
https://github.com/Azure-Samples/open-liberty-on-aks/blob/2c8bf374c473236367beec4165ac8d951494b0e9/java-app/src/main/liberty/config/server.xml
The text was updated successfully, but these errors were encountered: