Split artifacts into a bsp4j.protocol and a bsp4j.server
#668
Comments
lefou
changed the title
bsp4j.api and a bsp4j.server bsp4j.protocol and a bsp4j.server
|
This is also an opportunity, to have each BSP extension in it's own namespace (Java package), e.g. |
|
Bump |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is the outcome of discussion #651.
the
bsp4jartifact currently contains lots of heavyweight transitive dependencies. This makes it unsuitable to be used by foreign APIs, e.g. in build tool plugins to provide additional BSP suport. For example amill-rustplugin.What's needed is a
bsp4j.protocolartifact without any heavyweight transitive dependencies, which can be easily used in various build tools plugins.Therefore, we should split the current
bsp4jartifact into a leightweightbsp4j.protocoland absp4j.server, which may contain whatever transitive dependency is needed to launch a BSP server.The text was updated successfully, but these errors were encountered: