zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norbert Kalmar <nkal...@cloudera.com.INVALID>
Subject Re: Mavenized Zookeeper Roadmap
Date Mon, 18 Mar 2019 09:13:19 GMT
Hi all,

When maven migration started, I created a google docs that planned the
migration (
). It was open for suggestions, and there are quite some comments on it.
Anyway, the idea was something like:
- To keep backports easy for 3.4, we migrate to maven, but keep ant for
- 3.5 is not stable yet, so moving to maven build should be OK (same for
master obviously)

So keep ant in 3.4 and drop it in 3.5 and master. The docs do state
somewhere that it might be a good idea to keep both for a while, but since
we have concluded it would be a nightmare, keeping them in sync.

What will change compared to ant build?
- Modularized artifacts in maven central - org.apache.zookeeper:zookeeper
should still work as a dependency, it will get everything - I will test
this before the 3.5 release, once release doc is finalized.
- Two tarballs: buildable source only, and a "convenience" tar, having the
runtime jars. I also tested these, of course I will test again after
finalized release. Plus, I will also double check for license files and
jars included, as we had some issues about that.

So, to summarize, +1 (non-binding) on:
- keep ant for 3.4, I don't think it's worth making the transition, soon
3.5 will be the active branch anyway
- drop ant and ivy on 3.5(.5) and onwards.


On Sun, Mar 17, 2019 at 10:29 PM Enrico Olivelli <eolivelli@gmail.com>

> Hi,
> It seems to me that we don't have a clear roadmap for the switch to Maven.
> Points:
> - will we ever drop Ant for branch-3.4 and branch-3.5? I assume that for
> master it is not a problem
> - the release with Maven will have different results than the Ant based
> one, at least I expect a more 'modularized' release of binaries to Maven
> central: is it only for master or will we switch all of the active
> branches? (Current 3.4.14 vote had been prepared with Ant, and Maven on
> branch-3.4 is not ready yet)
> - what is preventing us from dropping ant/Ivy stuff from master?
> On the CI side we only have to migrate the precommit job completely,
> current Maven job is doing a few checks but not all of the Ant based one.
> IMHO we should drop Ant stuff from 3.5 now that we releasing it as 'stable'
> and drop it from master as well.
> I would leave 3.4 as it is now, the code base has been refactored in order
> to be like 3.5 and master and this will help cherry-picks but we can keep
> Ant there and spend our efforts on master.
> Best regards
> Enrico

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message