+ versions not handled

[Sciss]

First of all, cool plugin! I just tried it out. I have the habit to use + for the minor (binary compatible) versions; this seems to be ignored by the plugin. For example:

[info] Found 4 dependency updates for machinaecoelestis
[info]   de.sciss:mellite             : 0.5.+               -> 0.5.0
[info]   de.sciss:pdflitz             : 1.0.+               -> 1.0.1
[info]   de.sciss:play-json-sealed    : 0.1.+               -> 0.1.0
[info]   org.scala-lang:scala-library : 2.10.3 -> 2.11.0-M5         

Obviously 0.5.+ is already using 0.5.0, also 1.0.+ -> 1.0.1 is debatable. Finally, is there a switch to disable RC and milestone releases, like the last item?

[rtimush]

Thanks for pointing out the + versions issue, will fix. RC and milestone releases are fixed in #6.

[laughedelic]

Sorry for an offtopic question, but I couldn't find it anywhere: how do people do people publish these artifacts with + versions? When I publish my artifacts (ivy- or maven-style to an S3 bucket), then I can resolve them only with exact versions. What is the trick?

[Sciss]

You publish them with a fully qualified version. When defining dependencies, you can use + to allow for example the updates of minor versions. For example, this artifact has versions 2.2.0 and 2.2.1. If I have a dependent project I can require version 2.2.0+ or short 2.2.+ so at the time the binary compatible bugfix only release 2.2.1 is done, I can simply update that depending project without changing the dependency declaration.

[laughedelic]

Thanks, I understand how to use it. I asked, how to publish it, so that it works for my artifacts too.

[jedesah]

👍

[omervk]

+1 to this issue 👍
Hope it leaves the icebox someday...

[kiranbayram]

I've started to give this a shot but I can't move it in project board. Could you please do that for me @rtimush ?

[kiranbayram]

Opened #104 for this

[rtimush]

Fixed in #104