Issue deploying cache booster to OpenShift about cache-example HOT 8 CLOSED

I always do mvn clean fabric8:deploy -Popenshift. (Technically, I either always add the clean goal or remove all the target directories manually before running Maven. Because Maven just can't be trusted otherwise.)

from cache-example.

@geoand @Ladicek thank you for all the feedback.

I can confirm this works when adding clean.

I have updated here: https://github.com/fabric8-launcher/launcher-documentation/pull/1061/files#diff-dff07e55f4fc1b833e1853819d1ba1a2

from cache-example.

from cache-example.

@geoand I cloned this project and used the following instructions to deploy it to minishift (ver 1.15.0) and OpenShift online (us-east-1):
https://github.com/fabric8-launcher/launcher-documentation/pull/1061/files#diff-dff07e55f4fc1b833e1853819d1ba1a2

from cache-example.

from cache-example.

I can confirm that I am seeing the same error. I do know what's going on but the strange thing is that I haven't seen it before in this context...

from cache-example.

Turns out that this is easy enough to fix :)

The command to deploy using fmp should be mvn clean fabric8:deploy -Popenshift (note the addition of clean)
The error we saw due to the fact that you had built a previous version (probably 1.5.10-.x) before building the latest version (1.5.12-1), which meant that there were 2 Spring Boot uber jars in the target directory and Openshift didn't know which one to choose.
So the addition of the maven clean phase makes the process a lot safer (albeit to the expense of deployment speed)

from cache-example.

@rhoads-zach If you can confirm that the fix works for you, then it's probably best to update the docs and close this issue

from cache-example.