New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[work/light] Build Failed #8
Comments
yep, ik
I am not at home, I can not publish kutil 1.14-1.15 on maven central (only 64 kbit internet hehe)
Am 29. August 2022 07:42:47 MESZ schrieb Gamom ***@***.***>:
…```
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------< de.bixilon:Minosoft >-------------------------
[INFO] Building Minosoft 0.1-pre
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for de.bixilon:kutil:jar:1.15 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.998 s
[INFO] Finished at: 2022-08-29T13:39:51+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project Minosoft: Could not resolve dependencies for project de.bixilon:Minosoft:jar:0.1-pre: de.bixilon:kutil:jar:1.15 was not found in https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced -> [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
```
--
Reply to this email directly or view it on GitHub:
#8
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: