Separate out websocket client and server components from websocket-core #4881
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #2173 - Move server classes and dependencies out from websocket-core
Closes #2174 - Move client classes and dependencies out from websocket-core
WebSocket core now has 4 separate modules, the same as what has been done for both the jetty and javax websocket modules.
websocket-core-server
websocket-core-client
websocket-core-common
websocket-core-tests
Previously websocket-core had server dependencies even when only the client was needed.
Output from
mvn dependency:tree
in current jetty-10.0.x for the websocket-jetty-client:(there are server dependencies for jetty-server and jetty-servlet-api)
Output from
mvn dependency:tree
in this branch after splitting up websocket-core: