Closed aj-stein-gsa closed 1 month ago
Sigh, disregard, something has fixed it since release in develop:
% git checkout --track metaschema-framework/develop
% git rev-parse HEAD
7c8f72422205f3c529c80b97f1c4b86cc26bd3a2
% mvn clean compile exec:java
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------< gov.nist.secauto.oscal.tools:server >-----------------
[INFO] Building server 1.0.0-SNAPSHOT
[INFO] from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ server ---
[INFO] Deleting /Users/alexanderjstein/Code/oscal-server/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ server ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ server ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- kotlin-maven-plugin:1.7.21:compile (compile) @ server ---
[INFO]
[INFO] --- exec-maven-plugin:3.0.0:java (default-cli) @ server ---
2024-10-07T22:12:38.900219Z io.vertx.core.Launcher.main() ERROR Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
Describe the bug
I was unable to wrong the
mvn clean compile exec:java
command after runningmvn clean install
or other analogous commands without encountering an error.Who is the bug affecting
Running a local developer instance of the compiled server from dev.
How do we replicate this issue
See command steps below:
Expected behavior (i.e. solution)
Local service runs after successfully compiling.
Other comments
No response