-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
master fails to build due to a classworlds artifact not found #406
Comments
That's an odd error, and not one happening for the CI builds. I have seen something similar before on my machine but with a different jar:
So there is indeed something weird going on, but not deterministic and not affecting our build servers (internal at Netflix nor CloudBees). I'll post again if I learn more. |
I had this, too. Clearing the Maven cache fixes it. Sound like this. Some kind of Gradle/Maven interop problem, it seems. |
I had the same problem, too, and clearing the maven cache fixed it for me, thank you @jmhofer |
Yep, clearing .m2/repository away and building again solves this. A+ On Sep 23, 2013, at 7:58 PM, Ben Christensen notifications@github.com wrote:
|
Yep, I had this problem with a different dependency, which was actually in my ~/.m2/repository
Deleting the ~/.m2/repository/org/objenesis' directory and rerunning ./gradlew clean build resolved it too. |
…ctiveX#406) * take async retry to separate class and reduce retry waiting time * rate limiter aspect and other aspects fixes
./gradlew build
...
The text was updated successfully, but these errors were encountered: