Jan Bartel
Jan Bartel
@cstamas heh heh, I wasn't expecting a problem as jetty xml configuration code has dealt with overloaded methods for 20+ years :wink:
> What really struggles me and makes the poms hard/confusing to read is those double interpolation > > ``` > ${ee9.jakarta.activation.api.version} > ${ee9.weld.version} > ``` > > we are in...
@gregw this PR makes the ee11 ErrorHandler a subclass of the core ErrorHandler to remove code duplication. I've left ee8/ee9/ee10 untouched. Thoughts?
>This has to be undone as it doesn't play nicely with any of the versioning tools (command line, maven, IDE, dependabot, rennovate, etc) or CVE tooling. Please provide a concrete...
> I find it a bit confusing to have in jetty-eexx/pom.xml something such. > > ``` > ${ee11.jakarta.activation.api.version} > ``` > > then later in the pom > > ```...
@joakime @vmassol it's been implemented in the jetty-12.1.x branch. I guess if there's interest it could be backported to jetty-12.0.x, but we will be switching to jetty-12.1.x in the nearish...
I forgot we already had an issue for backporting the new environment specific `jetty-web.xml` and `jetty-env.xml` files: https://github.com/jetty/jetty.project/issues/11774
@vmassol no, we're not backporting any changes like this to jetty-10, so you're correct that the way to go in jetty-12.0 and beyond is to use the features in https://github.com/jetty/jetty.project/pull/11966...
@lachlan-roberts we need this to pass the servlet 6.1 tck
@lachlan-roberts nudge