My personal feelings of course. :) Ant is also good, but it all depends how scripts are written, I know that I have no idea what is inside scripts after a week, with Maven when I get back to scripts after months I know what is happening - this is the advantage of having some specific structure.
śr., 21 paź 2020 o 10:33 Piotr Zarzycki <[email protected]> napisał(a): > Hi Hugo, > > Usually it is, but I have found Maven less problematic over the years and > with new project much more easy to setup. If someone checkout your project > with Maven pom file - he doesn't need Royale SDK at all, cause everything > will be downloaded on the first build. > > Plus Maven scripts are much more cleaner than ant - In ant you can do > whatever you want, in Maven you have some specific structure which you > follow. > > Just to mention - I haven't changed my Maven build for Royale in the last > 3 years - maybe command has changed over that time, but not so much. With > > When you push something without building SDK by Maven check here if it's > not failing [1]. > > [1] https://ci-builds.apache.org/job/Royale/ > > śr., 21 paź 2020 o 10:09 Hugo Ferreira <[email protected]> > napisał(a): > >> 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. >> > > > -- > > Piotr Zarzycki > -- Piotr Zarzycki
