Optimizing mvn calls and make targets

• a separate mvn clean call should not be necessary (I left it in place for the setup target, in case this really make sense)
• mvn verify includes the compile and package phases (see Maven build lifecycle below)
• generate-spec target did point to install-yarn and validate-spec which also pointed to install-yarn

Maven build lifecycle: https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#a-build-lifecycle-is-made-up-of-phases

Makefile

 SHELL = /bin/bash
 setup: clean start-services;
 dev-start: setup;
-	(CONFIG_SECRET_PATH=$$PWD/config/application/secret.properties mvn compile quarkus:dev -Dconfig.secret.properties=$$PWD/config/application/secret.properties -Djava.net.preferIPv4Stack=true)
+	(CONFIG_SECRET_PATH=$$PWD/config/application/secret.properties mvn compile quarkus:dev -B -Dconfig.secret.properties=$$PWD/config/application/secret.properties -Djava.net.preferIPv4Stack=true)
 clean:;
 	mvn clean
 ## Compilation steps
 install-yarn:;
 	yarn install --frozen-lockfile --audit
-compile: clean compile-java;
-compile-quick: clean compile-java-quick;
+compile: compile-java;
+compile-quick: compile-java-quick;
 compile-java: generate-spec;
-	mvn compile package
+	mvn clean verify -B
 compile-java-quick: generate-spec;
-	mvn compile package -Dmaven.test.skip=true
-generate-spec: install-yarn validate-spec;
+	mvn clean verify -B -Dmaven.test.skip=true
+generate-spec: validate-spec;
 	yarn run generate-json-schema
 validate-spec: install-yarn;
 compile-start: compile-quick start;
@@ -42,4 +42,4 @@ test-post-git-eca:;
 test-dev-post-git-eca:;
 	curl http://api.eclipse.dev.docker:8080/git/eca -v -H 'Content-Type: application/json' -d @config/json/post-git-eca.json
 gitlab-root-pw-reset:;
-	docker exec -it $$(docker compose ps -q gitlab) gitlab-rake "gitlab:password:reset[root]"
\ No newline at end of file
+	docker exec -it $$(docker compose ps -q gitlab) gitlab-rake "gitlab:password:reset[root]"