netbeans-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Vieiro <anto...@vieiro.net>
Subject Re: Centralized external-binary versions?
Date Mon, 30 Oct 2017 10:04:40 GMT
Thanks for this, Yaroslav.

This is exactly the kind of explanation I was looking for.

>From my point of view this is a very important architectural decision
and it is important to a) state it clearly, b) adhere  to it and c)
make sure everybody adheres to it.

Cheers,
Antonio

2017-10-30 9:53 GMT+01:00 Jaroslav Tulach <jaroslav.tulach@gmail.com>:
> 2017-10-29 10:48 GMT+01:00 Antonio <antonio@vieiro.net>:
>
>> Hi all,
>>
>> Currently NetBeans modules define themselves the exact version of
>> third-party binaries, for instance:
>>
>> netbinox depends on org.eclipse.osgi_3.9.1.v20140110-1610
>> and
>> o.eclipse.core.runtime depends on org.eclipse.core.runtime-3.7.0
>>
>> Would it be a good idea to specify the exact versions of these in a
>> separate, centralized, release-specific version file?
>>
>
> -1
>
> I think this is a  bad idea as NetBeans and its build system is designed to
> be modular. Having a single centralized location to specify something which
> is not essential for the whole project goes against the modularity. Each
> external library is wrapped in its module. It is responsibility of the
> module to provide proper version of the library. It is responsibility of
> the module to evolve its own version in correspondence with changes in the
> library it wraps.
>
> The consistency of the whole system is kept by versioning of the individual
> modules. Not by a central configuration file which keeps all the versions.
> -jt

Mime
View raw message