Incorrect resolution of dependencies that are not cross compiled
josephrkramer opened this issue · 2 comments
After adding custom resolvers, our internal Maven repo is able to be used for getting dependencies. The problem is that any dependency that uses Scala is given a cross compile Scala version number by the sbt-pom-reader for a resolution path but the dependencies are not actually cross compiled. This leads to the FAILED DOWNLOADS error message. When I look at the path generated by sbt I see the following:
https://internal.host.com/content/repositories/releases/foo/bar_2.10.3/1.0/bar-1.0.jar
but it should be
https://internal.host.com/content/repositories/releases/foo/bar/1.0/bar-1.0.jar
If I was just using pure sbt, I would just use % instead of %%. Is there a way to not add the Scala version to the dependency when using sbt-pom-reader?
it actually shouldn't be doing that, so I think you have a legitimate bug on your hands.
Huh....
I just updated sbt from 0.13.0 to 0.13.2 (still using sbt-pom-reader 1.0.1) and my internal dependencies were downloaded correctly.