commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <mt...@apache.org>
Subject Re: [VOTE] Release Apache Commons Daemon 1.0.15
Date Wed, 03 Apr 2013 05:56:04 GMT
On 04/03/2013 02:21 AM, sebb wrote:
> On 2 April 2013 16:25, Mladen Turk <mturk@apache.org> wrote:
>
>> On 04/02/2013 05:06 PM, Jörg Schaible wrote:
>>
>>> Mladen Turk wrote:
>>>
>>>> And BTW, build number can use multiple sources and its primary usage
>>>> is with continuous integration. Our release version is build number in
>>>> this case.
>>>>
>>>
>>> We configured the build to take it from the current svn number to reflect
>>> the unique state of the repository. An entry like
>>>
>>> =========== %< =============
>>> Implementation-Build: UNKNOWN_BRANCH@r??????; 2013-03-28 13:53:43+0100
>>> =========== %< =============
>>>
>>> will give the immediate impression, that something did go wrong with the
>>> build. I'd rather drop the entry completely.
>>>
>>>
>> I mean ASF is all about releasing sources. That's our primary product.
>>
>
> So building from the tag should be equivalent to building from the source
> archive.
>

Not necessary. Source distribution might have some pre-generated code.
Many projects work like that and some even require manual handcraft from
release manager.

>>
>> Perhaps we can just disable build-number plugin and have it enabled
>> for some continuous build profile. Or at least have some 'non-error' like
>> message in case the product is not build from SVN checkout.
>>
>
> What error message?
> The build is not halted if the code is built from source.
>

Yes but it produces a trash (or error) like content in manifest
unless build from svn checkout.


Regards
-- 
^TM

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message