-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Start properties jetty.webapp.addServerClasses
and jetty.webapp.addSystemClasses
are not applied during ee8/ee9 deployments
#11514
Labels
Bug
For general bugs on Jetty side
Comments
joakime
changed the title
Start properties jetty.webapp.addServerClasses and jetty.webapp.addSystemClasses are not propagated to ee8/ee9 deployments
Start properties Mar 13, 2024
jetty.webapp.addServerClasses
and jetty.webapp.addSystemClasses
are not applied during ee8/ee9 deployments
gregw
added a commit
that referenced
this issue
Apr 12, 2024
…es in all environments (#11566) * Issue #11514 - Cleanup `jetty.webapp.addServerClasses` property behavior for ee10/ee9/ee8 * Fix test * Merging patterns (default -> env -> config) * Moved ClassMatcher to util * Adding more deprecations * Changing XML demos/tests to use new getter names * rollback xml changes in ee9/ee8 --------- Co-authored-by: Joakim Erdfelt <[email protected]> Co-authored-by: Jan Bartel <[email protected]>
Completed in PR #11566 |
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Jetty 12.0.9 - FROZEN
Apr 17, 2024
joakime
added a commit
that referenced
this issue
Apr 26, 2024
* Issue #11514 - Cleanup `jetty.webapp.addServerClasses` property behavior for ee10/ee9/ee8 * Merging patterns (default -> env -> config) * Moved ClassMatcher to util * System Server Classes * Renaming to Hidden/Protected * Updated for loss of dump.war * Update jetty-core/jetty-ee/src/main/java/org/eclipse/jetty/ee/WebappClassLoading.java * fixed OSGi tests * Ensure default hidden server and system classes. * Fixed ee9 OSGi to load jetty-ee * Adding more deprecations * Changing XML demos/tests to use new getter names * rollback xml changes in ee9/ee8 * Fix ee8 maven plugin * Make jetty-maven dependency optional in ee9 to match ee10 --------- Co-authored-by: Joakim Erdfelt <[email protected]> Co-authored-by: gregw <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version(s)
12.0.7
Jetty Environment
ee8 / ee9
Java version/vendor
(use: java -version)
Any
OS type/version
Any
Description
If you setup an jetty.base with a
jetty.webapp.addServerClasses
(orjetty.webapp.addSystemClasses
), then those properties do not get reflected in the ee9 / ee8 environments (it does work for the ee10 environments)How to reproduce?
Setup a fresh jetty.base with the
ee9-demos
...Notice that we have a
addServerClasses
with theorg.eclipse.jetty.logging.
entry.Now run with the server dump and look for the Serverclasses entries
If we do the same thing, but with ee10 ...
And run with server dump ...
You can see that the ee10 environment is working as expected with the
jetty.webapp.addServerClasses
The text was updated successfully, but these errors were encountered: