Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Fixed resolver pattern for local ivy #395
Addresses this bug: #300
Problem is that locally published jars in Ivy have a different pattern than they do in the remote repo. Specifically the Ivy.xml file, which lists the jar dependencies, is in a different subdirectory from the Jar. Annoyingly Ivy fails silently on this and just assumes you have no dependencies, and copies your local jar to the ivy cache with a default ivy.xml :/
I don't really grok Ivy that well, but I wonder if some of the other ivy issues are related (such as #387) to this. Maybe other patterns should be updated to include [type] and [classifier]?
Hmm, I assume those travis build fails are not related to my PR? I can't think how this change would result in some combinations of Scala and JDK not passing, but others passing fine.
Also I didn't include a unit test because I wasn't sure how you'd do it (you need another project to have "sbt publishLocal" first), but open to suggestions?