Thanks for that, valid reasons are always appreciated :)
Sylvain
On 2014-07-09, 2:38 PM, "Yuki Morishita" wrote:
>see https://issues.apache.org/jira/browse/CASSANDRA-5838.
>We tried once.
>
>On Wed, Jul 9, 2014 at 1:37 PM, Boily, Sylvain
>wrote:
>> Sorry about that, I just realized that both 2
see https://issues.apache.org/jira/browse/CASSANDRA-5838.
We tried once.
On Wed, Jul 9, 2014 at 1:37 PM, Boily, Sylvain wrote:
> Sorry about that, I just realized that both 2.2.0 and 3.0.X have two
> different groupID hence the reason why maven allows them both to be
> present in my class path.
>
Sorry about that, I just realized that both 2.2.0 and 3.0.X have two
different groupID hence the reason why maven allows them both to be
present in my class path.
I guess we can live with this knowing that the the packages are also
different.
Thanks
Sylvain
On 2014-07-09, 2:30 PM, "Boily, Sylv
Typically, we don't update dependencies across minor revs (e.g.,
2.0.8->2.0.9), and instead waiting for major releases (2.0->2.1). Looking
at the 2.1.0 branch, we're still using metrics-core-2.2.0.jar. As I'm not
sure of the work involved in upgrading (it maybe a simple drop-in
replacement, it may
