On Thu, 21 Feb 2019 at 05:33, Vladimir Sitnikov <sitnikov.vladi...@gmail.com> wrote: > > Philippe>If structure changes that can be harderI see. > > sebb>That was one of the major issues when we looked at moving to Maven a > few years back > > I'm sure the history would be fine in case we migrate to Git, and I see no > issues with migration either.
Moving code around always causes issues; not least it's harder for people used to the code to find things, at least initially. Why use a build system that all but forces a change on you? > It would be great if you could vote on SVN->Git thead. > > > sebb> Also Maven > > Sebb, what you say is true Maven story, however it is not applicable to > Gradle. > > Do you have concerns regarding Gradle? I have no experience of it. Whoever wants to switch should show that it can replace the current Ant build system without causing disruption. It needs to support all of the existing Ant targets. I assume it should be possible to do this in parallel; i.e. keep the existing Ant script(s) until the Gradle script(s) are shown to be equivalent (The Ant scripts don't change that often, so that should not be too difficult). Note that the current Ant build relies on some Beanshell scripting and Maven integration. I suggest dealing with these parts as early as possible as they are likely to be the hardest. The sooner any difficulties are found, the better. Less time wasted if they prove insoluble. > Vladimir
