>> Which would exactly results in coded builds which is in the end much >> more complicated and worse maintainable than any Maven build every be....
I agreed that the build is worse maintainable after long time, but the problem is that Java Hamcrest project, as an example, decided to use Graddle even after my pressure to accept Maven. They decided because of the only one reason : It's younger. They did not say Maven has a bug. Their decision was not professional and most probably such builds like they have would not be portable in another SCM or platform or CI but they do not know it now yet. People want to always try to use something new but there is also personal attitude, like it was with Java security and broken RSA 1. A lot of devs hate Java but they like JVM. Another problem why they hate Java was the problem with JRE stability/cryptography. The idea is that cryptography is built on computing complexity and not on Java itself. And here the Java lost reputation and renewed again with Java 8 as fixed number of bugs. I can clearly see in my company - they are shaking on the chair, what would happen with new version of JRE and I calm their down saying that JRE 8 already solved known bugs reported against in JRE7. Maybe the same should happen with Maven, who knows. :-) -- View this message in context: http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838755.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
