In that case, it would be advantageous to complete the build tool migration first before going to Yetus. That way, we'll avoid wasted effort implementing a Yetus personality file targeted to the current ant build. Yetus can support either mvn or gradle.
We don't necessarily need to complete the git migration first. Yetus runs patches against the mirror on GitHub, which works the same whether the source repo on Apache infrastructure is svn or git. --Chris Nauroth On 12/14/15, 2:33 AM, "Ivan Kelly" <[email protected]> wrote: >> - We should move away from ant and start using either maven or gradle. >>There is a patch (ZOOKEEPER-1078) for maven by phunt, but hasn't been >>able to finish it. I'm very supportive of making this move. >+1000 for this. > >> - I'd rather be using git at this point, so someone would need to the >>process of requesting infra and such to make the change. >This would also be great. > >I think one of the things which scares off developers when they look >at ZK is the circa 2005 tech being used. I know every time I download >a branch, I need to try to figure out where I have ant installed. > >-Ivan >
