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 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 [2] https://github.com/wildfly/wildfly-core/pull/2017 Thanks, Peter _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Hi James, On 2016-12-13 22:51, James Perkins wrote: > 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. That would be easy to do, but can you name a situation where it would actually matter?

Hi Peter, On Tue, Dec 13, 2016 at 5:26 PM, Peter Palaga <ppalaga(a)redhat.com&gt; wrote: > Hi James, > > On 2016-12-13 22:51, James Perkins wrote: >> 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. > > That would be easy to do, but can you name a situation where it would > actually matter? We have a few (compliance) test scripts that invoke build.sh to build the app server from source. I'm not sure how widespread use of build.sh is in other test environments but we probably could ask that question via a separate topic. Scott

The PR https://github.com/wildfly/wildfly-core/pull/2017 got merged in WF Core (thanks Brian!) and I am going to prepare a similar PR for WF. -- P On 2016-12-14 09:36, Peter Palaga wrote: > Hi Scott, OK, let's keep the build.(sh|bat) scripts for now. I'll change > them (1) to wrap mvnw and (2) to print a warning that they are > deprecated in favor of mvnw. -- P > > On 2016-12-14 01:04, Scott Marlow wrote: >> Hi Peter, >> >> On Tue, Dec 13, 2016 at 5:26 PM, Peter Palaga <ppalaga(a)redhat.com&gt; wrote: >>> Hi James, >>> >>> On 2016-12-13 22:51, James Perkins wrote: >>>> 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. >>> >>> That would be easy to do, but can you name a situation where it would >>> actually matter? >> >> We have a few (compliance) test scripts that invoke build.sh to build >> the app server from source. I'm not sure how widespread use of >> build.sh is in other test environments but we probably could ask that >> question via a separate topic. >> >> Scott >> > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev