Using ivy2local in an integration test

[daddykotex]

Hi, thanks for your project, love it.

Recently, I had the following issue: I have a module that I test with this project, and it depends on a library that had published locally. The integration test was not able to find it.

I believe that's because the run overrides the ivy.home to a local repository. I found a workaround which requires me to add the following at the top of my test build.sc:

import $repo.`ivy:file:///path/to/home/.ivy2/local/[organisation]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext]`

This is fine by me because I was just testing to see if everything worked locally before issuing official releases, but I was wondering if there was a shorthand like import $repo.ivy2Local that I could use or something like that.

Thanks

[daddykotex]

In the best case, there is such a short hand.

In the worst case, there is not and people can just find this issue if they have a similar issue and we can close this.

[lefou]

Maybe, I can avoid re-setting the ivy-home property and instead add a import $repo to the already generated plugins.sc file.