Skip to content

Commit 65f6f97

Browse files
committed
nitrite-bridge: depend on the released dbinspect-bridge 0.1.0
0.1.0 is released; `-SNAPSHOT` pointed at a coordinate that is now superseded. The module stays out of the parent's <modules>: 0.1.0 has not reached Maven Central yet, so a clean checkout still cannot resolve it and the reactor would fail. The comment now says that, and says to put the module back the day it appears — which is what nitrite-flutter and nitrite-rust already did once pub.dev and crates.io got the core. Bridge green: 76 tests over MVStore, RocksDB and in-memory.
1 parent c332891 commit 65f6f97

1 file changed

Lines changed: 6 additions & 3 deletions

File tree

‎nitrite-bridge/pom.xml‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,19 +20,22 @@
2020

2121
<!--
2222
NOT listed in the parent's <modules> on purpose, and it is a sequencing fact rather than
23-
an oversight: dbinspect-bridge is not on Maven Central until Fanlight M11, so a clean
23+
an oversight: dbinspect-bridge 0.1.0 is released but not yet on Maven Central, so a clean
2424
checkout of nitrite-java cannot resolve this module and the whole reactor would fail with
2525
it. Build it on its own:
2626
2727
mvn -f nitrite-bridge/pom.xml test
2828
2929
with dbinspect-bridge installed locally (mvn install in dbinspect/jvm/dbinspect-bridge).
30-
Exactly the situation nitrite-flutter's packages/nitrite_bridge is in, for the same reason.
30+
31+
Put this module back in <modules> the day 0.1.0 appears on Central — nitrite-flutter's
32+
packages/nitrite_bridge and nitrite-rust's nitrite-bridge were in exactly this situation
33+
and both rejoined their builds when pub.dev and crates.io got the core.
3134
-->
3235

3336
<properties>
3437
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
35-
<dbinspect.version>0.1.0-SNAPSHOT</dbinspect.version>
38+
<dbinspect.version>0.1.0</dbinspect.version>
3639

3740
<!--
3841
Pinned here rather than inherited, because this module is deliberately outside the

0 commit comments

Comments
 (0)