Maven build failure

[mghildiy]

I took latest of the project, and performed 'mvn clean install'. I get following error:

[INFO] Reactor Summary:
[INFO]
[INFO] lagom-java-chirper ................................. SUCCESS [ 1.404 s]
[INFO] friend-api ......................................... SUCCESS [ 2.364 s]
[INFO] friend-impl ........................................ SUCCESS [04:09 min]
[INFO] chirp-api .......................................... SUCCESS [ 1.377 s]
[INFO] chirp-impl ......................................... SUCCESS [ 42.104 s]
[INFO] activity-stream-api ................................ SUCCESS [ 0.446 s]
[INFO] activity-stream-impl ............................... SUCCESS [ 16.528 s]
[INFO] load-test-api ...................................... SUCCESS [ 0.365 s]
[INFO] load-test-impl ..................................... SUCCESS [ 7.104 s]
[INFO] front-end .......................................... FAILURE [ 29.443 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:51 min
[INFO] Finished at: 2018-10-27T08:21:10+05:30
[INFO] Final Memory: 112M/1127M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.lightbend.rp:reactive-app-maven-plugin:0.3.0:build (build-docker) on project front-end: Execution build-docker of goal com.lightbend.rp:reactive-app-maven-plugin:0.3.0:build failed: java.lang.reflect.InvocationTargetException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

Am I missing something here?

[TimMoore]

Hard to say without the complete output, but do you have Docker installed?

[mghildiy]

Yes, I have docker installed.

[mghildiy]

There is another thread on this, it seems.

https://discuss.lightbend.com/t/lagom-java-maven-chirper-example-fails-with-no-implementation-for-com-lightbend-lagom-javadsl-server-lagomservicerouter-was-bound/2129

[TimMoore]

That looks like a different issue, which has since been fixed. If you're still having this problem, I'd suggest posting more details in a new thread on discuss.lightbend.com.