Yes, and my work projects uses SBT (http://www.scala-sbt.org/).
On Mon, Oct 3, 2016 at 4:52 PM, Matt Sicker <boa...@gmail.com> wrote:
> My work projects use gradle, and I like to test release candidates with
> work projects before voting. There's one use case that Mikael is alluding
> to.
>
> On 3 October 2016 at 09:42, Ralph Goers <ralph.go...@dslextreme.com>
> wrote:
>
>> Why would you be using those while you are testing the release?
>>
>> To be clear, the release process requires that we build the artifacts to
>> be released and as part of the release process they are deployed to the
>> Apache Nexus staging repository (which is in the link in the email). If the
>> release passes I click a button in Nexus and the artifacts are pushed to
>> Maven central, so they have to have the real release version in them. The
>> distribution artifacts (the source and binaries) are extracted from what is
>> in the staging repository and pushed to the ASF distribution directory. I
>> cannot rebuild them again and change the version as that would require a
>> new vote.
>>
>> Ralph
>>
>> On Oct 3, 2016, at 7:23 AM, Mikael Ståldal <mikael.stal...@magine.com>
>> wrote:
>>
>> But some build tools, such as Gradle, cache stuff in other places.
>>
>> On Mon, Oct 3, 2016 at 4:08 PM, Ralph Goers <ralph.go...@dslextreme.com>
>> wrote:
>>
>>> 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
>>>
>>> --
>>> [image: MagineTV]
>>>
>>> *Mikael Ståldal*
>>> Senior software developer
>>>
>>> *Magine TV*
>>> mikael.stal...@magine.com
>>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | 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.
>>>
>>>
>>>
>>
>>
>> --
>> [image: MagineTV]
>>
>> *Mikael Ståldal*
>> Senior software developer
>>
>> *Magine TV*
>> mikael.stal...@magine.com
>> Grev Turegatan 3 | 114 46 Stockholm, Sweden | 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.
>>
>>
>>
>
>
> --
> Matt Sicker <boa...@gmail.com>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.stal...@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | 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.
