Hi Hugo, being possibly one of the biggest Maven advocats here, I think I could respond to this.
You are right, you can get the job of building a Royale application done with both tools. Having been working as an IT consultant for about 16 years now and having come across a lot of companies, there is definitely a tendency to move towards Maven for larger projects. Actually, I haven't come across an ANT project for quite some time now. I do however know that a lot of the people of the Royale community like Ant and uses that as primary build tool. For me personally I like the standardization of Maven ... so if I'm a newcomer and want to get started with a new project and that's built with Maven, usually it's a simple: Clone repo, build repo type of thing. Ant is a lot more flexible, but also far less standardized. I think even we demonstrate this nicely ... the simple task of cleaning up is not handled the same way for all of our repos. So we are maintaining both build systems and both should stay supported. Adding new stuff that doesn't build with Maven is just as bad as adding stuff that just builds with Maven. So If you need help with the Maven part, just ping me. Chris Am 21.10.20, 10:09 schrieb "Hugo Ferreira" <[email protected]>: Hi, For test fix and possibility new features, I apply the code in Royale source code and build with ANT but Royale also support build with Maven. I never use Maven before, so, what is the advantage in Royale to build with ANT or Maven. I searched a lot and seems to be only a metter of personal preference.
