Hi, I think this is a very bad trap now: - on content/group/snapshots 2.0.0-SNAPSHOT there are now 2.0.0 files - a dependency on 2.0.0-SNAPSHOT will download outdated modules!!: <metadata modelVersion="1.1.0"> <groupId>org.apache.deltaspike.modules</groupId> <artifactId>deltaspike-data-module-impl</artifactId> <version>2.0.0-SNAPSHOT</version> <versioning> <snapshot> <timestamp>20240112.111703</timestamp> <buildNumber>2</buildNumber> </snapshot> <lastUpdated>20240112111703</lastUpdated>
- 2.0.0 not available and not tagged - 2.0.1 build not generating project POM To be able to use _latest_ 2.0.0-SNAPSHOT (perfectly working!!): git checkout 48fbfea1ef93da80f2e8b620808332be4cef66f4 mvn -Drat.skip clean install -DskipTests Is it possible to trigger a similar build for public snapshots??? I have no idea how to do it :-/