After failing to install Ozone manually, I decided to use the Gitpod button to see if it worked that way, but it still failed with the following error.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Ozone 1.0.0-SNAPSHOT:
[INFO]
[INFO] Ozone Maven Commons ................................ SUCCESS [ 4.253 s]
[INFO] Ozone Distribution ................................. SUCCESS [03:07 min]
[INFO] Ozone .............................................. FAILURE [ 5.345 s]
[INFO] Ozone Scripts ...................................... SKIPPED
[INFO] Ozone Maven Parent ................................. SKIPPED
[INFO] Ozone Implementation Archetype ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:19 min
[INFO] Finished at: 2024-03-17T02:43:09Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project ozone: Could not resolve dependencies for project com.ozonehis:ozone:pom:1.0.0-SNAPSHOT: The following artifacts could not be resolved: com.ozonehis:ozone-docker-compose:zip:1.0.0-SNAPSHOT (absent): Could not find artifact com.ozonehis:ozone-docker-compose:zip:1.0.0-SNAPSHOT in mks-nexus-public (https://nexus.mekomsolutions.net/repository/maven-public/) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :ozone
Thanks in advance! Jack