I was following the Quick Start to add memind to a new project and hit a confusing mismatch.
README.md:25 shows the Maven badge as memind-0.1.0 and the dependency block a few lines down uses:
<dependency>
<groupId>com.openmemind</groupId>
<artifactId>memind-bom</artifactId>
<version>0.1.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
But pom.xml:41 has:
<revision>0.2.0-SNAPSHOT</revision>
A new contributor cloning the repo and following the README will import a BOM version that doesn't match the source they just cloned. If 0.1.0 is the last stable release that's fine, but the README should say so explicitly — something like "Latest stable: 0.1.0 | In development: 0.2.0-SNAPSHOT" — so it's clear which version to use for production vs. building from source.
Also noticed that the Plugin Architecture table at README.md:115 lists "Pluggable store (SQLite, MySQL)" but omits PostgreSQL, even though memind-plugin-jdbc-postgresql is a full module with its own migration scripts and is documented elsewhere in the same README. Small fix but worth catching before someone assumes PostgreSQL isn't supported.
I was following the Quick Start to add memind to a new project and hit a confusing mismatch.
README.md:25shows the Maven badge asmemind-0.1.0and the dependency block a few lines down uses:But
pom.xml:41has:A new contributor cloning the repo and following the README will import a BOM version that doesn't match the source they just cloned. If
0.1.0is the last stable release that's fine, but the README should say so explicitly — something like "Latest stable:0.1.0| In development:0.2.0-SNAPSHOT" — so it's clear which version to use for production vs. building from source.Also noticed that the Plugin Architecture table at
README.md:115lists "Pluggable store (SQLite, MySQL)" but omits PostgreSQL, even thoughmemind-plugin-jdbc-postgresqlis a full module with its own migration scripts and is documented elsewhere in the same README. Small fix but worth catching before someone assumes PostgreSQL isn't supported.