[JBWS-3735] Add dependencies on WS endpoint services to the web deployment
[JBWS-3735] Also wait for EndpointService to be started when the webapp is directly created by the EndpointPublisherImpl
[JBWS-3735] Revisiting EndpointPublisherImpl to allow running the process in 3 steps: prepare, deploy, publish. This allows setting proper service dependencies when running in-service (prevents XTS from getting stuck at boot)
[JBWS-3735] Refactoring
[JBWS-3735] Making an attribute final
Undertow 1.0.0.Beta25
Disable watch service based file watching for now
Update README to reflect current state
[WFLY-786] Remove invalid testing of address pruning
Revert "Remove some deps leftovers & testsuite cleanup"

This reverts commit 005567fe438049426292e4ca270060eadd8c9b7b.
WFLY-2468 MappingModuleDefinition is incorrectly constructing the write-attribute handler
WFLY-1469 WFLY-160 add support for runtime reloadable operations

- new model version 2.0
- new parser version 2.0 & xsd
- better runtime operation tests
- all operations are runtime executable now
- update XSD & default confguration
WFLY-2532 @Transactional and TransactionPhase does not work
Fixed init script for Ubuntu 13.10

In Ubuntu 13.10 they changed /lib/lsb/init-functions making /full/path/to/executable as required parameter of pidofproc. As result this init script stopped working for Ubuntu 13.10. Why did they do that? I suppose because man page for pidofproc specifies this parameter as required. Will my change affect existing distributions? I've checked init-functions for Debian Wheezy and Ubuntu 12.04, they silently ignore all parameters except pidfile. Why path to executable is java, why not $JBOSS_SCRIPT? Because man page for pidofproc says that pid should correspond to executable, and pid corresponds to java process. Although current implementation in Ubuntu 13.10 doesn't check it (indeed any additional parameter would resolve this issue). Testing done: Manually checked that after modification the init script can start and stop service in Debian Wheezy, Ubuntu 12.04, 13.10 and there're no pending abandoned wildfly processes.
Introduced JAVA variable in Debian init script to be used with pidofproc.
Use virtual file based resource manager to make sure deployment overlays work correctly with Undertow
WFLY-2266 Make deployment overlays feature able to replace application libraries
Temprorary change to work around watch service issue
Update to work with latest Undertow
[WFLY-2519] Useless mod_cluster drained context logging (...UndertowContext@3abb2fbc)