ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <br...@apache.org>
Subject Re: svn commit: r1669287 - /incubator/ignite/site/trunk/download-mirrors.html
Date Thu, 26 Mar 2015 21:30:56 GMT
On 26.03.2015 18:55, Valentin Kulichenko wrote:
> I think we should modify the build procedure of source package so that
> ignite.properties is augmented there as well. This way user will be able to
> build binary package from downloaded source zip.
>
> Actually it seems incorrect to ship source package with DEV version of
> ignite.properties, because it is based on specific revision.

I agree.


> On Thu, Mar 26, 2015 at 7:19 AM, Dmitriy Setrakyan <dsetrakyan@gridgain.com>
> wrote:
>
>> On Thu, Mar 26, 2015 at 4:28 AM, Branko ─îibej <brane@apache.org> wrote:
>>
>>> On 26.03.2015 08:47, dsetrakyan@apache.org wrote:
>>>> Author: dsetrakyan
>>>> Date: Thu Mar 26 07:47:28 2015
>>>> New Revision: 1669287
>>>>
>>>> URL: http://svn.apache.org/r1669287
>>>
>>> Well, in my opinion, the source download should be first on the page,
>>> not the binaries. Binaries are not official releases; the sources are.
>>> We should be encouraging people to use the sources.
>>>
>> Brane,
>>
>> Our release build procedure which builds the binary, requires that you must
>> be under the GIT root. The reason is that it automatically grabs the
>> version from the GIT server in order to imprint it into the release. So the
>> build you are suggesting does not even work. User would still be able to
>> build the maven modules, but user cannot build the actual binary release,
>> hence the -P-release option.
>>
>> I don't mind having a separate discussion about how useful it is for our
>> users to build a complete binary from the source zip (and not from GIT),
>> but in the mean time, I cannot call it the recommended way, because it is
>> not. Do you mind if I update the text?
>>
>> D.
>>
>>
>>
>>> -- Brane
>>>


Mime
View raw message