-
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
Issue #9396 - fixes to resolve WebSocket JPMS warnings #9915
Issue #9396 - fixes to resolve WebSocket JPMS warnings #9915
Conversation
Signed-off-by: Lachlan Roberts <[email protected]>
…9396-websocket-jpms-review
Signed-off-by: Lachlan Roberts <[email protected]>
I don't think the
The issue is that we must export the package of |
@janbartel help |
i think this could just be a surefire issue. I might needs something like: <plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<argLine>
@{argLine} ${jetty.surefire.argLine}
--add-modules org.eclipse.jetty.ee9.webapp
--add-reads org.eclipse.jetty.ee9.websocket.jetty.client=org.eclipse.jetty.ee9.webapp
</argLine>
</configuration>
</plugin> |
@lachlan-roberts that fixed it, so I've pushed to this branch. |
Signed-off-by: Olivier Lamy <[email protected]>
jetty-ee9/jetty-ee9-websocket/jetty-ee9-websocket-jetty-client/pom.xml
Outdated
Show resolved
Hide resolved
<argLine> | ||
@{argLine} ${jetty.surefire.argLine} | ||
--add-modules org.eclipse.jetty.ee8.webapp | ||
--add-reads org.eclipse.jetty.ee8.websocket.jetty.client=org.eclipse.jetty.ee8.webapp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You do not need the read
line. That is only used where we cannot declare an outright requires
in the module-info.java
, eg for test-only dependencies. Your module-info.java
has declared a requires static
and that must be sufficient and should not need to be forcibly overridden in this way.
...y-ee10/jetty-ee10-websocket/jetty-ee10-websocket-jetty-client/src/main/java/module-info.java
Outdated
Show resolved
Hide resolved
jetty-ee9/jetty-ee9-websocket/jetty-ee9-websocket-jetty-client/pom.xml
Outdated
Show resolved
Hide resolved
Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
Signed-off-by: Lachlan Roberts <[email protected]>
…-webapp/pom.xml Co-authored-by: Jan Bartel <[email protected]>
…lient-webapp/pom.xml Co-authored-by: Jan Bartel <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wot @janbartel said!
I think that was my original mistake and I went from "Try A" to "Try A and B" without actually doing "Try B".
These |
Signed-off-by: Lachlan Roberts <[email protected]>
…ent-webapp Split websocket client modules for webapp configuration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look OK to me
@jmcc0nn3ll @joakime This has not actually been built in CI? |
Signed-off-by: Lachlan Roberts <[email protected]>
This needs to push a notification to the build servers, I updated DNS but perhaps there's something else that we need to do to fix that connection. |
Issue #9396
DistributionTests
WebSocketShutdownContainer
s publicly exported in module-info files.WebSocketShutdownContainer
andJettyWebSocketClientConfiguration
should berequires static transitive
as they are in public signatures but also optional.