Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Trouble specifying version ranges in Kobalt
See original GitHub issueI checked out and tried http://maven.apache.org/components/enforcer/enforcer-rules/versionRanges.html
postgres has very weird versioning, so I’m not surprised this didn’t work:
compile("org.postgresql:postgresql:[9.4,)")
Downloaded artifact org.postgresql:postgresql:pom:42.0.0-20170127.084917-23 from (http://repository.jetbrains.com/all/, default, releases+snapshots)
*****
***** ERROR Error: com.beust.kobalt.KobaltException: Couldn't resolve org.postgresql:postgresql:jar:42.0.0-SNAPSHOT
the exception seems to have come from within Aether
org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.postgresql:postgresql:jar:42.0.0-20170127.084917-23 in (https://jcenter.bintray.com/)
Note that, in gradle this did work (some people may care)
compile group: 'org.postgresql', name: 'postgresql', version: '9.4.+'
More surprising was that in Kobalt .917 this did not work:
"org.sql2o:sql2o:[1.5,)"
*****
***** ERROR Couldn't resolve range artifact org.sql2o:sql2o:jar:[1.5,)
*****
But this does:
"org.sql2o:sql2o:1.5.4"
Issue Analytics
- State:
- Created 7 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
“full success!” thanks
This should be fixed in 0.921, can you try again?