transitive dependencies not resolved #523
Comments
@kgignatyev this works for me with the latest version (which was released with probably relevant fixes earlier today). Can you re-check? In case it works for you, feel free to close the issue. |
Just checked with 0.8.1, same - transitive dependencies are not resolved, please see the attached s3.scala file |
Weird, still works for me even after local cache clean. What do you mean by "we have only Maven repo"? |
I mean that there is no ivy dependency definitions there, just standard Nexus repository server (https://www.sonatype.com/download-oss-sonatype ) but now at home (no servers) it still does not work for me. Did you try to run file I have attached? |
Yes, I did and here's the log: https://gist.github.com/tkroman/6cfa9e9a1f0974e73cfdc7d32985ab7d Can you clean your ivy cache and try again? |
OK, found how to reproduce this bug: .ivy2 and .m2 caches need to be deleted in order for $ivy to start resolving transitive dependencies. When fully populated .m2 cache exists and .ivy2 does not then transitive resolution does not work. Steps:
|
Confirmed. I'll look into this when I'll have spare time, which would probably in a couple of days. |
I have the same problem, example:
Can not solve: |
@tkroman Could you hint what needs to be done to implement Maven resolver? I might have some time to look into it? |
@kgignatyev yeah, I was too optimistic about it. The problem is, Ammonite generates its own wrapper pom for dependencies and somewhere in there something gets lost. I spent some time debugging the hell out of ivy's internals, and even googled some similar problems, but their solutions didn't work and now I don't have enough time to do this. Even if I had, I think it won't be worth it seeing as there are plans to move from that |
Are you saying that it is too hard to implement dedicated Maven based resolver? I would be very happy if I could use only it to resolve dependencies and do not have any Ivy in sight ;) |
No, the problem is that there are some obscure resolver configuration flags (originally I thought that something like this can help: https://stackoverflow.com/questions/20799578/cant-get-ivy-to-resolve-transitive-dependencies-of-modules-in-my-local-reposito, but it didn't (or I did something wrong)), and the docs are really scarce I also tried some workarounds, but can't really remember if anything worked. Unfortunately, I don't think I can tell you anything useful :) |
OK, thanks for trying
…On Feb 9, 2017 14:03, "Roman Tkalenko" ***@***.***> wrote:
No, the problem is that there are some obscure resolver configuration
flags (originally I thought that something like this can help:
https://stackoverflow.com/questions/20799578/cant-get-
ivy-to-resolve-transitive-dependencies-of-modules-in-my-local-reposito,
but it didn't (or I did something wrong)), and the docs are really scarce
I also tried some workarounds, but can't really remember if anything
worked. Unfortunately, I don't think I can tell you anything useful :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#523 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA1BryfpP2ZSj9u9DdebGflAU2IuvrOVks5ra40jgaJpZM4LJKza>
.
|
I was experimenting a bit and it seems to be easy enough to maven resolver, please have look at the diff attache. basically I have modified trait LoadJar by adding maven() method that is 3 lines of code thanks to ShringWrap library https://github.com/shrinkwrap/resolver#introduction-to-shrinkwrap-resolvers Please have a look if that can be used, at least it seems like a good basis to address #524 |
Okay, here's a PR for @kgignatyev's solution, I also added a test. Please have a look and tell me if anything needs to be changed. Edit: Not sure why noLongLines test is failing, don't see this in my local environment. Any guidance would be appreciated. |
Okay, fixed up the long-line thing and added a merge strategy so aether works properly but not sure what the Scala 2.10.6 issue is. Would appreciate any comments. In case I haven't made it clear before, this change allows you to do: |
The switch to coursier happened here 662859f Hopefully this should fix it, but regardless, any contribution is going to have to be reworked. I'm still not exactly sure what the problem is, because the samples provided work out-of-the-box on my machine, so if it's still broken someone is going to have to explain it to me in a way I can understand... |
we have only Maven repo and dependencies do not get resolved
causes compile exception
maven resolves dependencies fine and script works if I import all the dependencies reported by
mvn dependency:list
individually
The text was updated successfully, but these errors were encountered: