PR: https://github.com/OpenNMS/opennms/pull/2545

It looks like v 4.2.5+ of the karaf-maven-plugin has the desired behaviour by default. Upgrading to the latest Karaf should fix this issue.

Perhaps the next steps here are to determine how the maven repository is populated in the sentinel docker image and see if there is a way to configure it to not use the timestamped snapshots similar to the result I got when I pulled the artifacts directly with maven.

Documenting for myself how I was attempting to reproduce this:

• fetch artifacts for API

  • mvn org.apache.maven.plugins:maven-dependency-plugin:2.1:get -DrepoUrl=https://oss.sonatype.org/content/repositories/snapshots -Dartifact=org.opennms.integration.api:karaf-features:0.2.0-SNAPSHOT:xml

  • mvn org.apache.maven.plugins:maven-dependency-plugin:2.1:get -DrepoUrl=https://oss.sonatype.org/content/repositories/snapshots -Dartifact=org.opennms.integration.api:api:0.2.0-SNAPSHOT

  • mvn org.apache.maven.plugins:maven-dependency-plugin:2.1:get -DrepoUrl=https://oss.sonatype.org/content/repositories/snapshots -Dartifact=org.opennms.integration.api:common:0.2.0-SNAPSHOT

  • mvn org.apache.maven.plugins:maven-dependency-plugin:2.1:get -DrepoUrl=https://oss.sonatype.org/content/repositories/snapshots -Dartifact=org.opennms.integration.api:config:0.2.0-SNAPSHOT

• start up vanilla karaf container

• add api snapshot repo

  • feature:repo-add mvn:org.opennms.integration.api/karaf-features/0.2.0-SNAPSHOT/xml

• Install API snapshot version

  • feature:install opennms-integration-api/0.2.0-SNAPSHOT

As noted above by Markus this doesn't really reproduce the problem since this results in the non-timestamped snapshot artifacts being pulled into maven repo as well.

@Matthew Brooks, glad I could help