Make zkClusterService optional again and just properly guard against NPEs
[jboss-fuse-6.1.x 036] Updating perfectus-build number to new build
[jboss-fuse-6.1.x 037] Updating perfectus-build number to new build
minor refactor so we can move the git profiles directory in git to another directory other than the root directory easily
added a little helper method to allow safe navigation of children of possibly non-existing paths
avoid bringing in old version of commons-codec
avoid using the name 'fuse' for the default app for a fuse container; as it may clash with the local clone of the fuse project ;)
minor refactor so that we can start to implement a DataStore which uses git for its version/profile configuration
revert to build 35 as 36 and 37 seem duff/partial distros?
added first spike of DTO classes for creating OpenShift containers
first spike of #54 got the basic import, create version, create/delete profile working; still lots to do
mostly working version/profile/configuration git implementation of DataStore for #54; file watching is missing though
refactor of the DataStore so that we have a ZooKeeper and Git implementation (with the ZooKeeper one still enabled by default)
rollback the change c478e376586b633ca3461843b774a638b002dd59 as at least for me, it seems to cause the fabric to lock up with missing dependencies on startup when running "fabric:create". Hope its working fine for everyone else too & its not just that we've some other timing issue going on!
moved the GitDataStore into fabric-core as its way too hard to have plugable DataStores in separate bundles right now.
this change adds git into fabric-core and I've had to move FabricGitService interface to fabric-core from fabric-git (which adds a fabric-core dependency on fabric-git - we could move FabricGitService into a separate bundle later if this proves troublesome). Other than that right now we still hard code the ZooKeeperDataStore with DS as being the only implementation; this change was really about moving things around and checking I'd not broken anything ;). Next we can try have a smarter DataStore factory which picks the DataStore to use based on configuration (and does the same on bootstrap time too)
fix osgi wiring issue caused by moving git into fabric-core
[FABRIC-496]: Ensure that the fabric-maven-proxy and fabric-web reregister entries if zookeeper recconnects (after session expiration). Cleanup old state in ZooKeeperGroup, when session expires.
Added jsch to fabric-core feature, since its required by some git classes recently added to core
use a ConfiguredDataStoreFactory to decide which DataStore to create (both at bootstrap and at normal fabric creation time); for now its hard coded though ;)
use a system property to define which kind of DataStore to use; both at bootstrap and when running the fabric properly. We could maybe refactor this later on so that we have separate configurations of bootstrap versus runtime configurations which are passed in by hand in bootstrap or injected via DS in @Activate for runtime; but for now its a simple way to switch that works :)