[
https://issues.apache.org/jira/browse/IVY-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976148#comment-13976148
]
David Turner commented on IVY-1399:
-----------------------------------
I have another one of these: https://gist.github.com/anonymous/11159231
I've attached a log and the (probably useless, since it contains two
Twitter-internal deps) ivy XML file. The dependency chain that triggers the
problem is:
com.twitter.scalding_internal#job;0.0.2 requires org.slf4j#slf4j-api;1.6.1
while cascading#cascading-local;2.5.2
requires org.slf4j#slf4j-api;1.7.2. job depends on dal, and dal depends on
cascading-local.
Note that an ivy.xml file which contains just job doesn't trigger the bug. Not
sure why.
The ivy.xml file I was using, however, includes a second dependency,
com.twitter.scalding_internal#analytics-batch. Because
analytics-batch doesn't require any particular version of slf4j-api, and
because its dependencies include 1.7.2, 1.7.2 is chosen (I think).
However, at this point, it's too late. 1.7.2 has already been "evicted" and
thus its data never got loaded. So, we crash. We can
confirm that this is the issue by swapping the order of the two dependencies;
this fixes the crash.
Hope this helps.
> impossible to get artifacts when data has not been loaded.
> ----------------------------------------------------------
>
> Key: IVY-1399
> URL: https://issues.apache.org/jira/browse/IVY-1399
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.3.0-RC2
> Reporter: Carl Lerche
>
> I am getting the error "impossible to get artifacts when data has not been
> loaded. IvyNode = com.google.guava#guava;r08"
> This is happening with ivy 2.3.0-RC2.
> I am unsure what the best information to provide is, so here is the verbose
> output as well as ivy.xml
> https://gist.github.com/ebc2b325d333b739d0b1
--
This message was sent by Atlassian JIRA
(v6.2#6252)
