Skip to content

Commit 66b0612

Browse files
gselzerclaude
andcommitted
code-lsp: explain why Gson's version is pinned
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 405bd4c commit 66b0612

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

‎code-lsp/pom.xml‎

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,8 +100,13 @@
100100
<version>${lsp4j.version}</version>
101101
</dependency>
102102
<!--
103-
NB: lsp4j asks for a range of Gson versions; fix one, so that projects
104-
without Gson's version managed do not resolve the range themselves.
103+
NB: lsp4j asks for a range of Gson versions ([2.9.1,3.0)), as is usual
104+
for OSGi bundles. Maven resolves a range to the newest matching release
105+
in the remote repositories: a network lookup, and a result that changes
106+
as Gson releases. Declaring Gson here (its version managed by
107+
pom-scijava) fixes one version in our published POM, which wins over
108+
lsp4j's range for anyone depending on us (nearest wins), whether or not
109+
their build manages Gson's version.
105110
-->
106111
<dependency>
107112
<groupId>com.google.code.gson</groupId>

0 commit comments

Comments
 (0)