AFAICT currently (i.e. before this change), the normal dist module build (i.e. no -Drelease) didn't do anything different from the 'build' module besides creating a fat server, except [1]. So I'm ok with skipping that.  I'll just change my normal

$ dist/target/wildfly-whatever-SNAPSHOT/bin/


$ build/target/wildfly-whatever-SNAPSHOT/bin/

[1] In full WildFly the dist module runs the maven-verifier-plugin. We'll need to move that to 'build' as I don't want it only run when we're about to release. I believe all the existing verifications should work just fine from build, except for this one, which IMO should be removed anyway, as it's not checking any contract we support:


Rob -- can you confirm that JBDS doesn't really need to check the contents of the server module any more? AIUI doing that was just a workaround in some prior releases and isn't relevant with the latest releases.

On Fri, Oct 20, 2017 at 7:47 AM, Tomaž Cerar <> wrote:
Hey guys,

As initial work on trimming our IO usage by testsuite and build,
I've send
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.



wildfly-dev mailing list

Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat