On Thu, 29 Sep 2016 13:40:08 +0300, Artem Barger wrote:
Hi,
What you are arguing here is that if "some-lib" is
upgraded, then the JDK must change version too!
Does that (extreme) comparison make the issue clearer?
I agree that the mixing of versions, even if allowed,
is not the best choice; that's why I've argued from the
outset that such loosely coupled modules must in fact
be different components!
The result will be that, indeed, users must choose from
compatible versions. Anything new under the Sun?
Can we please go away from the monolithic culture (and
look at what other libraries do, and at what IIUC the
JDK is going to do in the next major release)?
It seems like the number of components were a limited
resource. This kind of conversation is truly wasting
valuable time that could have been better spent in setting
up "rng-utils".
It seems like folks here are happy to make things more
complex than they intrinsically are.
Gilles
On Thu, Sep 29, 2016 at 1:06 PM, Emmanuel Bourg <ebo...@apache.org>
wrote:
>> Multi-module projects are quite common and the case you mention
isn't
>> unusual.
>
> Please show an example.
Spring, Jetty, Jackson, Log4j, Hadoop, Lucene, Maven, Hipparchus...
There is no lack of examples. Multi-module projects routinely
publish
new releases with some of their modules unmodified.
I think that I'd agree w/ Emmanuel here. It will be very strange
where
on change in rng-core from v1 to v2 one will have to update
rng-module1
from v1 to v2 (since I believe that rng-module1 will depend on
rng-core),
while
version update of rng-module1 will not cause reciprocal effect.
IMO it's much easier when user will be able to use one version for
all
rng-* modules,
rather than starting to struggle what version need to be taken for
what
module.
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>rng-core</artifactId>
<version>${rng.version}</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>rng-tools</artifactId>
<version>${rng.version}</version>
</dependency>
Looks better than
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>rng-core</artifactId>
<version>v1</version>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>rng-tools</artifactId>
<version>v99</version>
</dependency>
And it's much easier to support.
Best regards,
Artem Barger.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
