With EAP 8, we switched to the channel based provisioning which means that the base server repository no longer mirrors the latest state of the server. While it still guarantees that the individual server dependencies/components need to be backwards compatible and thus delivering fixes to the main codebase with the dependencies versions frozen in the time of EAP 8 release is valid, we might still want to verify the latest provisioning state that the customers have (or will have with the next Update).

For this reason, we should document how engineers can easily update they local clones of the jboss-eap8 repository to the latest artifacts and optionally also provide a script that will automate this task.