On 03/08/2011 10:23 AM, Andreas Kollegger wrote: > Interesting. I've never used the libraryDependencies approach for specifying > dependencies. What's the advantage? I'll have to read up about that. >
I think it ultimately does the same thing as specifying separate vals, so no advantage, just preference. I like the clarity of stating "this is a library dependency" rather than relying on val introspection. In any case, I contorted my build definition in a variety of ways, but no matter what I did, I never downloaded anything other than neo4j-kernel-tests.jar. Eventually I tried your working project below, and that failed too. So it doesn't appear to be my project definition. I'm also regularly removing ~/.ivy2, ~/.m2, lib_managed/ and target/. Not sure if I'm missing anything, though the SBT download process does state "16 artifacts copied, 0 already retrieved" so I think I'm getting them all. What Scala and SBT versions are you using? 2.8.1 and 0.7.5.RC0 here. Not sure where to go from here. I'll try a post to the SBT list later today. Thanks for the help. _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
