Why SBT custom plugin resolution is slow

Question

I have my custom SBT plugin and I use it in my project. In case of any change of the plugin I make publish-local and then I build my project and sbt writes in console Resolving <my-plugin-name>;0.2-SNAPSHOT .... This resolution takes long time(about minute).

Why it takes so much time to resolve a custom sbt plugin from local repository and how to fix this ?

Update

Please note, that I have slow network connection via proxy-server. So probably it's the issue. But in this case I wonder why sbt needs network if I have my plugin published-local. And if it's the issue how to eliminate network round trip ?

It would be well worth while setting up a local repository proxy like Nexus. This would optimize your network traffic. — Mark O'Connor, Jun 21 '13 at 20:13

score 2 · Accepted Answer · edited May 23 '17 at 11:56

2

If the dependency is a SNAPSHOT, then sbt will try to resolve it from the remote repository in case it has been updated.

See also Re-download a SNAPSHOT version of a dependency using SBT

edited May 23 '17 at 11:56

Community

1
1

answered Jun 21 '13 at 14:00

Garrett Hall

29,524
10
61
76

Why SBT custom plugin resolution is slow

1 Answers1