-
Notifications
You must be signed in to change notification settings - Fork 126
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
mavenLocal() ignored when resolving dependencies #108
Comments
It means, that you may want to check the dependency declarations in your script for typos, version-mistakes, etc. To debug the issue you could run |
I had a similar problem because I defined a wildcard version...
which produced the following error message [kscript] Resolving dependencies...Failed to lookup dependencies. Maven reported the following error:
[ERROR] Failed to execute goal on project maven_template: Could not resolve dependencies for project kscript:maven_template:jar:1.0: Failure to find at.mikemitterer:builddart:jar:0.+ in http://jcenter.bintray.com/ was cached in the local repository, resolution will not be reattempted until the update interval of jcenter has elapsed or updates are forced -> [Help 1] After defining the full version |
Do you know if maven itself is able to resolve wildcards dependencies? |
Hmmm - I haven't used Maven since I moved to Gradle (x years ago) but I don't think they support wildcards. As far as I know they had just LATEST | RELEASE keywords and then they dropped those KW in 3.0 |
Maven seems to support version ranges, so maybe this would work? |
Duplicate of #166 |
What needs to be configured for searching mavenLocal first when resolving dependencies?
I've tried to specify a dependency which is only present in my local maven repo, but it didn't get resolved.
Error msg:
What does it mean (line 2 of error message):
Check dependency locators...
The text was updated successfully, but these errors were encountered: