They have the same version because if the vote passes these are the artifacts
that will be released to Maven central. What we are doing is the correct
process. When you test the release build locally you should delete it from your
local repo if the build fails.
Ralph
> On Oct 3, 2016, at 5:45 AM, Mikael Ståldal <mikael.stal...@magine.com> wrote:
>
> Currently, the Release Candidate artifacts have the same version as the
> release will have ("2.7" currently). This can cause issues since Maven (and
> other similar build tools) cache non-snapshot artifacts quite aggressively,
> they are supposed to be immutable.
>
> Would it be possible to use another version, such as "2.7-rc1" or
> "2.7-SNAPSHOT"?
>
> We don't have to change this now, but for the next release after 2.7
>
> --
>
>
> Mikael Ståldal
> Senior software developer
>
> Magine TV
> mikael.stal...@magine.com <mailto:mikael.stal...@magine.com>
> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
> <http://www.magine.com/>
>
> Privileged and/or Confidential Information may be contained in this message.
> If you are not the addressee indicated in this message
> (or responsible for delivery of the message to such a person), you may not
> copy or deliver this message to anyone. In such case,
> you should destroy this message and kindly notify the sender by reply email.
>
