Closed DanStadlerNewRelic closed 5 years ago
Please refer to the trouble shooting tips in the build section:
The tests use some ports on the local machine. Make sure that no server runs in the background.
Skip the tests: ./mvnw clean package -Dmaven.test.skip=true or mvnw.cmd clean package -Dmaven.test.skip=true (Windows).
Please reopen the issue if this doesn't work.
can you please offer more detail on this part: "The tests use some ports on the local machine. Make sure that no server runs in the background."
Do you mean a kafka server? I am pretty sure I'm not running it at all on this laptop.
Just to help me understand, what is the exact test I should be executing to ensure that "no server runs in the background"?
Also, I did try to run without the tests, i.e.
./mvnw clean package -Dmaven.test.skip=true
. That succeeds. However I still fail at the docker stage, as listed in the other bug I opened.
thanks - Dan
I updated the documentation concerning the ports, see 8b7894a3985e441bb628b607131a26f6bf28a6e4 .
I reassured that in fact docker-compose build
does work once the maven build has completed successfully. So I am afraid I cannot reproduce your problem.
Hi, I wanted to try out your project, so cloned and tried out the how-to-run section. When the tests run after the build, there is a long period of getting these messages:
When the tests do end, this is the final output: