-
-
Notifications
You must be signed in to change notification settings - Fork 180
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
Failed to execute goal on project chestshop: Could not resolve dependencies #582
Comments
Not sure why it failed like that for you, might be because you enforce checksum validation in maven or maybe it cached something weird. Try cleaning your local repo cache and check your maven settings regarding validation. Anyways: I don't think it's something that can be fixed in the build setup or do you have suggestions/ideas? |
Where? |
https://maven.apache.org/settings.html -> checksumPolicy might do the trick, not sure. More likely that your local cache is just borked so try removing the artöfact folder it has issues with. If you can reproduce on a fresh maven/OS install (e.g. in a docker container) then there might be more to it but beyond that I can't really help fix your system. (And please don't ping/post unnecessary, impatient comments...) |
Have mavn manually installed! And configure and rerunning do not change anything 🤷 |
I'm unsure why you tagged me without providing additional info. I already told you what I think might help. Btw. your original log is down, can you re-upload it directly in the GitHub issue or on gist so it stays present? (Or provide a new log with the current version, ideally on a fresh system e.g. with a linux vm or cleaned out CI workspace just to rule out anything on your existing system being the issue) |
|
What is happening?
See log here
What did you expect to happen?
The .jar file in
target
Plugin Version
SNAPSHOT (directly from the GutHub repo)
Plugin Config
Not given
Server Version
Not given
Server Log
Not given
What other plugins are you running?
Not needed
Agreements
Additional context
No response
The text was updated successfully, but these errors were encountered: