Hi Emmanuel, I'm not trying to start a flame war.
This thread was started because there doesn't seem to be a lot of activity on the project. A statement like "The biggest changes had to do with moving away from Ivy and moving toward Maven", suggests to me that significant time was spent on getting the tooling to work. Going from a completely free format Ant/Ivy to a completely structured Maven is bound to be difficult and expensive. Going to something more flexible like Gradle would have saved time that could then have been spent to advance the project. So in my mind it's very relevant to discuss the tooling here. Not a lot of people have even heard of XACML, let alone would be willing to put time into this project. Therefore, optimizing the productivity of those who do seems like a good idea to me. Thanks, Ray -----Original Message----- From: Emmanuel Lécharny [mailto:[email protected]] Sent: dinsdag 9 februari 2016 11:07 To: [email protected] Subject: Re: [DISCUSS] - Retire OpenAz? Le 09/02/16 11:01, Sinnema, Remon a écrit : > Hi David, > > I agree that good architectural design is slow to gain traction. The same can > be said for tooling. It's been known for 4 years now how flawed Maven is and > how superior other build tools are in comparison. > https://www.thoughtworks.com/radar/tools/maven > http://gradle.org/maven_vs_gradle/ This is not the right place to discuss about Maven vs Graddle. Please keep focus on OpenAZ, thanks !
