Thanks for the heads up, the -Drelease option will be helpful for TCK testing, so thanks also for adding that option! On Fri, Oct 20, 2017 at 8:47 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; wrote: > Hey guys, > > > As initial work on trimming our IO usage by testsuite and build, > I've send https://github.com/wildfly/wildfly-core/pull/2880 > which changes wildfly-core to never produce "inflated" build/distro with > jars present. > But rather uses thin server provisioning (module.xml entries point to maven > GAV) > > As part of this work, "dist" folder is now used for just that, for > distribution and noting else. > So unless build is invoked with -Drelease which is something that is done as > part of release process, "dist" folder will be empty and wont produce > anything. > > Sever for testing is still present in "build" directory as it always was. > > This was done to reduce unnecessary IO work and producing multiple server > builds without need for them. > > I am sending this mail mostly as FYI that further work on this is going to > happen, in core and in full, and such changes might clash with some poeple's > workflows, where they are used to expect server dist to be in "dist" folder > but it is not there yet. > > -- > tomaz > > > > _______________________________________________ > 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

> Does -Drelease just populate the dist folders or does it do anything else as well? -Drelease populates dist folder and also produces .zip & tar.gz "distro" of wildfly core. Without this flag, "dist" folder stays completely empty. On Mon, Oct 23, 2017 at 10:28 AM, Darran Lofthouse < darran.lofthouse(a)jboss.com&gt; wrote: > Does -Drelease just populate the dist folders or does it do anything else > as well? > > > On Sat, 21 Oct 2017 at 02:33 Scott Marlow <smarlow(a)redhat.com&gt; wrote: > >> Thanks for the heads up, the -Drelease option will be helpful for TCK >> testing, so thanks also for adding that option! >> >> On Fri, Oct 20, 2017 at 8:47 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com&gt; >> wrote: >> > Hey guys, >> > >> > >> > As initial work on trimming our IO usage by testsuite and build, >> > I've send https://github.com/wildfly/wildfly-core/pull/2880 >> > which changes wildfly-core to never produce "inflated" build/distro >> with >> > jars present. >> > But rather uses thin server provisioning (module.xml entries point to >> maven >> > GAV) >> > >> > As part of this work, "dist" folder is now used for just that, for >> > distribution and noting else. >> > So unless build is invoked with -Drelease which is something that is >> done as >> > part of release process, "dist" folder will be empty and wont produce >> > anything. >> > >> > Sever for testing is still present in "build" directory as it always >> was. >> > >> > This was done to reduce unnecessary IO work and producing multiple >> server >> > builds without need for them. >> > >> > I am sending this mail mostly as FYI that further work on this is >> going to >> > happen, in core and in full, and such changes might clash with some >> poeple's >> > workflows, where they are used to expect server dist to be in "dist" >> folder >> > but it is not there yet. >> > >> > -- >> > tomaz >> > >> > >> > >> > _______________________________________________ >> > 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 > > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev