Maven build failure in 0.1.3-snapshot

[enozcan]

When running maven build using v0.1.3-SNAPSHOT with the configuration written on the readme of boost-maven, such an error raises:

[ERROR] Failed to execute goal boost:boost-maven-plugin:0.1.3-SNAPSHOT:package (default) on project some-project: No target Boost runtime was detected. Please add a runtime and restart the build. -> [Help 1]

What exactly does Boost runtime target mean?

Also, when I use docker-build goal as I've done using v0.1 and v0.1.2, I encounter another error:

Could not find goal 'docker-build' in plugin boost:boost-maven-plugin:0.1.3-SNAPSHOT among available goals debug, help, package, run, start, stop -> [Help 1]

Thanks in advance

[scottkurz]

Are you trying to target a SpringBoot app to OpenLiberty / WebSphere Liberty? Could you share a link to your POM (or a sample showing what you're trying to do)?

[enozcan]

Actually I'm trying to build the app here using the pom under finish directory. Only boost-maven-plugin is changed in the pom file according to the instructions on the readme of boost-maven

[scottkurz]

OK, welll, the Docker + SpringBoot function has been pulled out of the master branch. We are focusing on Microprofile use cases with Boost at the moment and have not yet decided in which vehicle (plugin) we will carry forward this function within.

You'll have to use one of the earlier releases (e..g v0.1.2) to use the 'docker-build' goal and/or SpringBoot support. Sorry for the confusion. We would never do something like this for mature function and had tried to indicate the early, "alpha" nature with the "0.1.x" version numbering.

Was there a specific reason you were trying to use a newer version of the plugin than the 0.1.2 release?

[enozcan]

Thanks for your help. The reason I tried to use this version is the failure seen here.

[scottkurz]

OK, I see. So until this fix is released you would have to workaround by either:

1. Building a local 0.1.3-SNAPSHOT of Boost before the SpringBoot support was removed. I just pushed tag 'before-spring-boot-removal' in case you find this approach helpful, as a starting point.

OR

2. Starting the project with Dockerfile already in your project root directory. You could just run the goal once save the Dockerfile, make the modification (adding --chown=1001:0) and then run again, in which case the plugin will NOT overwrite what you already have. (And if you do this you can probably save this for your next project since there's not much dynamic in the generation of Dockerfile except starting from the SpringBoot 1.x vs. 2.x base image.)