[ https://issues.apache.org/jira/browse/KARAF-7544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798690#comment-17798690 ]
ASF subversion and git services commented on KARAF-7544: -------------------------------------------------------- Commit d7e6477f316ed5f89ec17f32462f475b99906559 in karaf's branch refs/heads/main from Robert Varga [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=d7e6477f31 ] [KARAF-7544] Use properties to centralize jetty version and servlet api maven coordinates Signed-off-by: Robert Varga <robert.va...@pantheon.tech> > Upgrade to Jetty 10 and Pax Web 9 > --------------------------------- > > Key: KARAF-7544 > URL: https://issues.apache.org/jira/browse/KARAF-7544 > Project: Karaf > Issue Type: Story > Reporter: Grzegorz Grzybek > Assignee: Grzegorz Grzybek > Priority: Major > > I've prepared Pax Web branch to release Pax Web 9 with Jetty 10 upgrade > (JDK11+). (see: https://github.com/ops4j/org.ops4j.pax.web/issues/1743) > With few tweaks, Karaf 4.4.2-SNAPSHOT works well with the above dependencies, > with few restrictions: > * I've generally upgraded Servlet API jar/bundle used by Karaf to version 4 > * {{StandardFeaturesTest.installAriesBlueprintWebFeature}} and > {{RestExampleTest.testWhiteboard}} need a _compatibility bundle_ for Servlet > API, so {{javax.servlet}} package is exported with version 3.1.0 (for > blueprint.web and aries.jaxrs bundles) > * {{CamelExampleTest}} needs some polish, because I see that asm 5.0.4 bundle > is installed from Camel features and it doesn't work with JDK17 > * {{PaxCdiFeaturesTest}} should be removed (IMO), because Pax CDI is no > longer maintained - Pax Web works well with Aries CDI > * I've changed all {{<javase>}} elements of karaf-maven-plugin configuration > to {{<javase>11</javase>}} > * {{WebSocketExampleTest}} no longer works, as it uses > {{org.eclipse.jetty.websocket.api.annotations.WebSocket}} and > {{org.eclipse.jetty.websocket.servlet.WebSocketServlet}} which are not > available in Jetty 10 - however Pax Web 8+ itself fully works with JSR356 > compatible web sockets (using ServletContainerInitializers for Jetty, Tomcat > and Undertow) -- This message was sent by Atlassian Jira (v8.20.10#820010)