openshift-vertx-examples / vertx-cache-example Goto Github PK

https://github.com/reactiverse/vertx-maven-plugin/releases

You get the following error:

[ERROR] No plugin found for prefix 'fabric8' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/Users/rruss/.m2/repository), redhat-ga (https://maven.repository.redhat.com/ga/), redhat-early-access (https://maven.repository.redhat.com/earlyaccess/all/), central (https://repo.maven.apache.org/maven2)] ->

Interestingly enough, this works fine when using test.sh as well as mvn clean verify -Popenshift,openshift-it

[ERROR] Failed to execute goal on project integration-tests: Could not resolve dependencies for project io.openshift.booster:integration-tests:jar:6-SNAPSHOT: The following artifacts could not be resolved: io.openshift.booster:cute-name-service:jar:6-SNAPSHOT, io.openshift.booster:greeting-service:jar:6-SNAPSHOT: Could not find artifact io.openshift.booster:cute-name-service:jar:6-SNAPSHOT in redhat-ga (https://maven.repository.redhat.com/ga/)

If you run mvn install from project root before running mvn verify from the integration-tests directory, then everything works.

The root directory and the integration-tests directrory contain .openshiftio/application.yaml files that don't make any sense. Processing them results in extraneous build configs and deployment configs in OpenShift, which obviously never materialize, they just fail.

Currently, the community based booster is leveraging the product image to start a cache service. Should a community based image be used instead?

As example:
https://github.com/snowdrop/spring-boot-cache-booster/blob/master/greeting-service/src/main/resources/static/index.html#L68-L75