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
[info] Found 1 dependency update for chavrusa-backend
[info] org.scala-lang:scala-library : 2.11.8 -> 2.12.0
What it really means to me however is that a new scala version is on maven. But that's useless if my dependencies aren't published for it.
Suggestion: Don't show dependency update for scala-library. Instead, it should separately say "new scala version available," and show which libraries have been published for it. The library for the new scala may not have the same version as for the current scala.
There are a few cases, I don't know if they can be identified reliably.
Java libraries don't care about the scala version and are always fine
Most scala libraries only care about the scala binary version (2.11.x is one scala); they must be available with the right suffix (e.g. _2.11)
A few are versioned with the full scala version (scala-library, scala-reflect, etc.) They typically have no suffix and match by their own artifact version (e.g. 2.11.8 for scala 2.11.8)
The text was updated successfully, but these errors were encountered:
Right now it shows output like
What it really means to me however is that a new scala version is on maven. But that's useless if my dependencies aren't published for it.
Suggestion: Don't show dependency update for scala-library. Instead, it should separately say "new scala version available," and show which libraries have been published for it. The library for the new scala may not have the same version as for the current scala.
There are a few cases, I don't know if they can be identified reliably.
_2.11
)The text was updated successfully, but these errors were encountered: