You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem features module at the moment is using scala-graph 1.11.2 library, which has transitive dependency on scalacheck testing library, but not in the test or optional scope. Probably it was a minor mistake in the early days of scala-graph development, which was fixed quite long ago. From the end-user perspective this might be suspicious at minimum, e.g. my first question during dependency troubleshooting and spark job assembly building was: what this test dependency is doing in the runtime?
Solution
The aforementioned fix is available since 1.11.4, while the last version in the 1.11 branch is 1.11.5.
Solution might be as simple as bumping the scalaGraphVersion, thus reducing dependency tree a bit and simplifying the assembly building for the users.
The text was updated successfully, but these errors were encountered:
Problem
features
module at the moment is usingscala-graph 1.11.2
library, which has transitive dependency onscalacheck
testing library, but not in thetest
oroptional
scope. Probably it was a minor mistake in the early days ofscala-graph
development, which was fixed quite long ago. From the end-user perspective this might be suspicious at minimum, e.g. my first question during dependency troubleshooting and spark job assembly building was: what this test dependency is doing in the runtime?Solution
The aforementioned fix is available since
1.11.4
, while the last version in the1.11
branch is1.11.5
.Solution might be as simple as bumping the
scalaGraphVersion
, thus reducing dependency tree a bit and simplifying the assembly building for the users.The text was updated successfully, but these errors were encountered: