StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>This uses a build of AS 7.2.0.Final (there's a tricky tag for this one - see below) as the example since, at the time of writing, that's the latest JBoss AS build.</p> <p>It takes about 20 mins on a top spec Macbook Pro (again at the time of writing). Most of that time is spent running thousands of tests. The resulting binaries are exactly what used to be available for download from the Redhat site. Just because you built them locally doesn't make them somehow "less stable" than the binaries you used to be able to download. There's no difference between you building them and someone at Redhat building them and then uploading them. (I know <em>you</em> know that but not everyone does.)</p> <p>The tags should be available here (which is a good way to check what the latest version actually is!): <a href="https://github.com/wildfly/wildfly/tags" rel="nofollow">https://github.com/wildfly/wildfly/tags</a></p> <p>The example is obviously for a *nix machine but should apply with almost no changes to a Windows machine.</p> <p>You will need git and Maven installed (but if you're running JBoss you probably already have!).</p> <p><em><strong>Note: Do not have a JBoss instance running when building this! The tests detect a running instance and fail, to avoid confusion with which JBoss is being tested.</em></strong></p> <pre><code>cd anyDirectoryWhereYoupPeferBuildsToBe git clone https://github.com/wildfly/wildfly.git cd wildfly git checkout 7.2.0.Final-testsuite-fix mvn clean install -Drelease=true </code></pre> <p>Once it is built, just smoke test the sever:</p> <pre><code>cd build/target/jboss-as-7.2.0.Final/bin/ ./standalone.sh </code></pre> <p>You should now find the release version as a zip file in the directory dist/target</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload