Closed dragos closed 7 years ago
I don't like the user experience in Maven right now, where they have to use three version numbers: patched scala-maven-plugin, Hydra and MetricsService. If we could reduce that number it would be greaaat
I completely agree. The first thing that comes to mind is to append the the Hydra version to the Scala Maven plugin version and cut a release every time we release Hydra. It’s a bit more work on our side, but the user experience would be the same as in Sbt. After all, we should be ok trading a little inconvenience on our side for a clearly better uex. Just my $0.02 ;-)
-- Mirco
Sent from mobile
On 4 May 2018, at 21:02, Iulian Dragos notifications@github.com wrote:
I don't like the user experience in Maven right now, where they have to use three version numbers: patched scala-maven-plugin, Hydra and MetricsService. If we could reduce that number it would be greaaat
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.
I realized we will want to set the dashboard version to be 1.0.0 when we release hydra 1.0.0. The reason is that I believe it would send the wrong signal to see
hydraMetricsServiceVersion=0.0.1
in a maven build when using Hydra 1.0.0 :)After 1.0.0 the two versions may evolve independently.