Many thanks Serkan for take the time to respond here :) El vie., 27 mar. 2020 a las 10:50, serkan (<[email protected]>) escribió:
> Hi, > > For over years I used ant for build and release in many of my projects > than tried maven after. I spent time on gradle also - liked its > architecture. I can say hat it is moving simple to complex in terms of > usage through ant-maven-gradle way. > > Ant is really simple in terms of usage and to understand what is going on > but you have to do lots of thing manually while maven has lots of build in > features that makes life easier but bringing complexity. > > Especially artifact generation, central management of released artifacts > and referenced library downloads are time and disk space consuming heavy > tasks but you do not have to think about the nested references of libraries > on the other side which in ant you have to consider. > > So as the result I think if the scheduling and the dependency management > is not the issue, and if it is necessary I am not against mixed release > cycle with ant and maven. > > If not than it is better to leave the decision to RM. > > The shortest way the one that you know I believe. > > for nice comparison : https://www.baeldung.com/ant-maven-gradle > > Thanks, > Serkan > > 25.03.2020 20:31 tarihinde Carlos Rovira yazdı: > > Hi all, > > if you care about this project, the PMC will need your help to know what's > important to you about the "Release Process". > > Chris Dutz and I was working these days on release a new version. We > finally give up due to the complexity of the process. > The process involves to build in a CI Server with 13 steps and each one > with some manual commands in CI server and in local machine. The process > involves use Ant and Maven build systems, and that's what makes it so > complicated. > > Maven is the the most widest and used build system for release as this > statistics clearly states [1] and is perfectly prepared for CI servers and > all the tooling needed nowadays for release process. > > Chris and I thinks that just using Maven can reduce the process to 2-3 > steps and release without much problem, and even release often (each month > or each 2 months). > > So we're asking to not require Ant to be part of the release process, > since we think is not needed. > > (This does NOT means remove Ant, we are talking just about release, and > people using Ant will be able to continue using it as a build system, so > don't be afraid about Ant support in the future!). > > We're afraid for this project due to this problem, so for this reason is > important that you express what's important from your point of view as an > Apache Royale user. So please express yourself in this thread and let us > know what path should we take. It's important. > > We want to hear from you! > > Thanks community :) > > [1] https://twitter.com/ChristoferDutz/status/1240219399551934473 > > -- > > http://about.me/carlosrovira > > > -- Carlos Rovira http://about.me/carlosrovira
