Always use jboss developer repository
Fix model cache location
Re compress zip files to get zip distro down bit more.
Remove javax.activation, it belongs to web/full distro
WFLY-3581: add new phase entry
WFLY-3572 Deployment overlay feature does not work if a leading / is present on the overlay path
Externalize the checkstyle config into its own repository
Merge pull request #4 from ctomc/build

Fix transformers framework problems
Merge pull request #5 from ctomc/build-cleanup

Few build related changes
Merge pull request #6 from emmartins/WFLY-3581

WFLY-3581: add new phase entry
Merge pull request #7 from stuartwdouglas/checkstyle

Externalize the checkstyle config into its own repository
Merge pull request #8 from stuartwdouglas/WFLY-3572

WFLY-3572 Deployment overlay feature does not work if a leading / is pre...
WFLY-3551: updating deployment phase
Change checkstyle scope to provided
Merge pull request #9 from emmartins/WFLY-3551

WFLY-3551: updating deployment phase
1.0.0.Alpha2
Next is 1.0.0.Alpha3-SNAPSHOT
Exclude plugin for eclipse build
[WFLY-266] Notification Support

* add notifications to AS7 resources description
  * notifications are described in :read-resource-description operation
    if the notifications boolean is true
* all resources emit 3 types of notifications by default:
  * resource-added
  * resource-removed
  * attribute-value-written
* NotificationDefinition let any resources describe the notifications
  they can emit by registering them in the ManagementResourceRegistration
* add NotificationSupport to let AS7 resource register/unregister
  notification handlers and emit notifications
* emit notification for resource added/removed and attribute-value-written
  directly from the AbstractOperationContext.
* emit notifications for server lifecycle notifications (server-started,
  server-stopped, server-restarted, server-killed & server-destroyed)

Notification emitted by OperationContext.emit(Notification) are
effectively sent at the end of the operation execution if it is
successful. This ensure that the order of notifications emitted by a
single OperationContext will be received in the same order (unless
they are emitted during the ResultHandler execution).

JIRA: https://issues.jboss.org/browse/WFLY-266
[WFLY-3169] add JMX notifications for management resources

* provide standard JMX notifications RESOURCE_ADDED_NOTIFICATION,
  RESOURCE_REMOVED_NOTIFICATION and ATTRIBUTE_VALUE_WRITTEN_NOTIFICATION
  based on WildFly's notifications (WFLY-266).
* hack PluggableMBeanServerImpl#addNotificationListener. If listener
  is registered on JMImplementation:type=MBeanServerDelegate, register it
  on jboss-as:management-root=server too to receive
  RESOURCE_ADDED_NOTIFICATION and RESOURCE_REMOVED_NOTIFICATION
  notifications when management resources are added/removed.

JIRA: https://issues.jboss.org/browse/WFLY-3169