You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, Gradle deploys the psk dependency to central as packaging=pom, and classifier=all to get the jar itself. This means that the deephaven-server dependency will not have the psk present at runtime as specfied, when loaded from maven central, though it will correctly have it when run from the deephaven-core project itself.
The text was updated successfully, but these errors were encountered:
The psk auth plugin is deployed to maven central, as a PUBLIC project, but doesn't appear in the bom
https://search.maven.org/artifact/io.deephaven/deephaven-bom/0.34.3/pom
The deephaven-server project explicitly depends on it in gradle, and the pom appears to depend on it:
https://search.maven.org/artifact/io.deephaven/deephaven-server/0.34.3/pom
However, Gradle deploys the psk dependency to central as packaging=pom, and classifier=all to get the jar itself. This means that the deephaven-server dependency will not have the psk present at runtime as specfied, when loaded from maven central, though it will correctly have it when run from the deephaven-core project itself.
The text was updated successfully, but these errors were encountered: