This project provides the core runtime that is used by the Wildfly application server. This includes:
- Modular class loading.
- Unified management, including domain mode.
- Basic deployment architecture.
- CLI for management.
- JDK 8 or newer
- Maven 3.6.0 or newer
To build with your own Maven installation:
Alternatively, you can use the Maven Wrapper script that downloads and installs (if necessary) the required Maven version to
~/.m2/wrapper and runs it from there. On Linux, run
Starting and Stopping WildFly
Change to the bin directory after a successful build:
$ cd core-build/target/wildfly-core-[version]/bin
Start the server in domain mode:
Start the server in standalone mode:
To stop the server, press Ctrl + C, or use the admin console:
$ ./jboss-cli.sh --connect command=:shutdown
Note that there is not very much that you can do with the core server, without first adding some extensions to it. If you are trying to deploy Java EE application then you likely want the full Wildfly distribution, which is located at: https://github.com/wildfly/wildfly
- Install the latest version of Eclipse.
- Make sure Xmx in Eclipse.ini is at least 1280M, and it's using java 7
- Launch Eclipse and install the m2e plugin, make sure it uses your repo configs (get it from: https://www.eclipse.org/m2e/ or install "Maven Integration for Eclipse" from the Eclipse Marketplace).
- In Eclipse preferences Java->Compiler->Errors/Warnings->Deprecated and restricted set forbidden reference to WARNING.
- In Eclipse preferences Java->Code Style, import the cleanup, templates, and formatter configs in ide-configs/eclipse.
- In Eclipse preferences Java->Editor->Save Actions enable "Additional Actions", and deselect all actions except for "Remove trailing whitespace".
- Use import on the root pom, which will pull in all modules.
- Wait (m2e takes awhile on initial import).