Re: [wildfly-dev] Maven 3.3.1+ coming to wildfly and wildfly-core

Hi Peter, It may not be a big deal because it's just for builds, but instead of deleting the build.(sh|bat) maybe we just make those invoke the appropriate mvnw command instead.

On Fri, Dec 9, 2016 at 7:28 AM, Peter Palaga <ppalaga(a)redhat.com <mailto:ppalaga@redhat.com>> wrote: Hi *, as discussed with some of you on Brno F2F, both wildfly and wildfly-core are ready for Maven 3.3.1+ now. I am in the process of preparing PRs that will: * Enforce Maven version 3.3.1+ * Introduce mvnw (a.k.a.) Maven Wrapper [1] - a script that downloads and installs (if necessary) the required Maven version to ~/.m2/wrapper and runs it from there. * Use of mvnw will be optional * build.sh/bat <http://build.sh/bat> in wildfly will be removed * MAVEN_OPTS will live in .mvn/jvm.config and .mvn/maven.config A PR for core [2] was sent already. [1] https://github.com/takari/maven-wrapper#maven-wrapper <https://github.com/takari/maven-wrapper#maven-wrapper> [2] https://github.com/wildfly/wildfly-core/pull/2017 <https://github.com/wildfly/wildfly-core/pull/2017> Thanks, Peter _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/wildfly-dev <https://lists.jboss.org/mailman/listinfo/wildfly-dev> -- James R. Perkins JBoss by Red Hat