WildFly Application Server
Java XSLT HTML Shell Batchfile PowerShell
Latest commit c03aecf Aug 23, 2016 @kabir kabir committed on GitHub Merge pull request #9146 from jmesnil/WFLY-6983_pcf_transaction_descr…
…iption

[WFLY-6983] Fix transaction attribute description
Failed to load latest commit information.
appclient Next is 11.0.0.Alpha1 Jul 26, 2016
batch WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
bean-validation WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
build Next is 11.0.0.Alpha1 Jul 26, 2016
client Next is 11.0.0.Alpha1 Jul 26, 2016
clustering Merge pull request #9134 from pferraro/master Aug 18, 2016
connector WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
dist Next is 11.0.0.Alpha1 Jul 26, 2016
ee WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
ejb3 Merge pull request #8865 from rpelisse/WFLY-6422 Aug 23, 2016
feature-pack WFLY-6955 Application client has not assigned security permissions de… Aug 21, 2016
iiop-openjdk WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
jaxrs Next is 11.0.0.Alpha1 Jul 26, 2016
jdr Next is 11.0.0.Alpha1 Jul 26, 2016
jpa WFLY-6901 - add checkstyle to hibernate4 & 5 tests Aug 17, 2016
jsf Next is 11.0.0.Alpha1 Jul 26, 2016
jsr77 Next is 11.0.0.Alpha1 Jul 26, 2016
legacy WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
mail Next is 11.0.0.Alpha1 Jul 26, 2016
messaging-activemq [WFLY-6983] Fix transaction attribute description Aug 23, 2016
mod_cluster WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
naming WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
picketlink Next is 11.0.0.Alpha1 Jul 26, 2016
pojo Next is 11.0.0.Alpha1 Jul 26, 2016
rts WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
sar Next is 11.0.0.Alpha1 Jul 26, 2016
security-manager Next is 11.0.0.Alpha1 Jul 26, 2016
security WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
servlet-build Next is 11.0.0.Alpha1 Jul 26, 2016
servlet-dist Next is 11.0.0.Alpha1 Jul 26, 2016
servlet-feature-pack [WFLY-5136] Update configuration to use the new <http-upgrade/> child… Jul 28, 2016
spec-api WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
system-jmx Next is 11.0.0.Alpha1 Jul 26, 2016
testsuite Merge pull request #9122 from ctomc/testsuite-reload Aug 23, 2016
tools WFLY-4305: fix broken download-maven.sh script Mar 5, 2015
transactions [WFLY-5613] Remove the default values from the descriptions as they c… Aug 23, 2016
undertow Merge pull request #9095 from stuartwdouglas/WFLY-6910 Aug 23, 2016
web-common Next is 11.0.0.Alpha1 Jul 26, 2016
webservices WFLY-6901 - Enable checkstyle for test code Aug 17, 2016
weld Next is 11.0.0.Alpha1 Jul 26, 2016
xts Next is 11.0.0.Alpha1 Jul 26, 2016
.gitattributes Enable text conversion Aug 17, 2010
.gitignore Merge pull request #7228 from wolfc/WFLY-4305-2 Sep 3, 2015
README.md Update README.md Aug 18, 2016
build.bat No test arg anymore Aug 22, 2014
build.sh Merge pull request #7228 from wolfc/WFLY-4305-2 Sep 3, 2015
integration-tests.bat change powershell call in integration-tests.bat too Aug 22, 2014
integration-tests.sh WFLY-6295 Wrong header comments on integration-tests.sh script Feb 27, 2016
pom.xml WFLY-6615 Upgrade wildfly-arquillian to 2.0.0.Final Aug 19, 2016
zanata.xml fix zanata configuration Mar 6, 2012

README.md

WildFly Application Server

http://wildfly.org

  • Fast Startup
  • Small Footprint
  • Modular Design
  • Unified Configuration and Management

And of course Java EE7!

Building

Ensure you have JDK 8 (or newer) installed

java -version

On *nix-like system use the prepared script

./build.sh

On Windows use the corresponding batch script

build.bat

If you already have Maven 3.2.5 (or newer) installed you can use it directly

mvn install

Starting and Stopping WildFly

Change to the bin directory after a successful build

$ cd build/target/wildfly-[version]/bin

Start the server in domain mode

$ ./domain.sh

Start the server in standalone mode

$ ./standalone.sh

To stop the server, press Ctrl + C, or use the admin console

$ ./jboss-cli.sh --connect command=:shutdown

More information: https://docs.jboss.org/author/display/WFLY10/Getting+Started+Guide

Contributing

https://developer.jboss.org/wiki/HackingOnWildFly

Build vs. Dist directories

After running mvn install, WildFly will be available in two distinct directories, build and dist.

  • The build directory contains a build of WildFly that is based on Maven artifact resolution for module configuration
  • The dist directory, on the other hand, contains a full distributable build of WildFly

Using the build directory makes iterating with subsystem or module development easier since there is no need to rebuild the whole of WildFly or copy JAR files around on every change.

The dist directory is better suited when a full build of WildFly is needed for development or test purposes.

Running the Testsuite

The testsuite module contains several submodules including the following:

  • "smoke" -- core tests that should be run as part of every build of the AS. Failures here will fail the build.
  • "api" -- tests of features that involve end user use of the public JBoss AS 8 API. Should be run with no failures before any major commits.
  • "cluster" -- tests of the WildFly HA clustering features. Should be run with no failures before any major commits.
  • "domain" -- tests of the domain management features. Should be run with no failures before any major commits.
  • "integration" -- tests of a WildFly standalone server's internals. Should be run with no failures before any major commits.
  • "spec" -- tests of features that only involve end user use of the Java EE 7 spec APIs. Should be run with no failures before any major commits.

To run the basic testsuite including smoke tests from the root directory, run the build script "./build.sh" or "build.bat":

For basic smoke tests, simply: "./build.sh test"

To run all the tests

$ ./build.sh install -DallTests

Using Eclipse

  1. Install the latest version of eclipse
  2. Make sure Xmx in eclipse.ini is at least 1280M, and it's using Java 8
  3. Launch eclipse and install the m2e plugin, make sure it uses your repo configs (get it from: http://www.eclipse.org/m2e/ or install "Maven Integration for Eclipse" from the Eclipse Marketplace)
  4. In eclipse preferences Java->Compiler->Errors/Warnings->Deprecated and restricted set forbidden reference to WARNING
  5. In eclipse preferences Java->Code Style, import the cleanup, templates, and formatter configs in ide-configs/eclipse in the wildfly-core repository.
  6. In eclipse preferences Java->Editor->Save Actions enable "Additional Actions", and deselect all actions except for "Remove trailing whitespace"
  7. Use import on the root pom, which will pull in all modules
  8. Wait (m2e takes a while on initial import)

License