Adds EntityCleanupLongevityTest
JcloudsLocationTest: fix indent
Adds ControlledDynamicWebAppCluster.WEB_CLUSTER_SPEC
Add JcloudsLocation.MAX_CONCURRENT_MACHINE_CREATIONS

- Prevent more than the given number of concurrent calls to create
  VMs for a given JcloudsLocation instance.
- Required in various clouds (sometimes, at least!) such as aws-ec2
  where one gets http response 503 RequestLimitExceeded when trying to
  provision 18 machines concurrently.
Fix JcloudsLocationTest

- only throw NoMachinesAvailableException if the last obtain attempt
  threw that; otherwise throw the underlying exception.
- (the problem is probably not that the cloud is full with no more
  machines available!)
Merge pull request #1001 from aledsage/feature/ControlledDynamicWebAppCluster.webClusterSpec

Adds ControlledDynamicWebAppCluster.WEB_CLUSTER_SPEC (to 0.6.x)
DynamicCluster.quarantineFailedEntities now defaults to true
DynamicCluster.quarantine: review comments

- adds javadoc
- improves config key description
Merge pull request #1002 from aledsage/fix/DynamicCluster-quarantee-defaults-true

DynamicCluster quarantine now defaults to true
Merge pull request #999 from aledsage/feature/jclouds-max-concurrent-creates-0.6.0

Feature: jclouds max-concurrent-creates (in 0.6.x)
Compiled release notes for 0.5.0 -> 0.6.0.

Conflicts:
	docs/start/release-notes.md
Don't rely on sketchy `OsDetails.isLinux()` method.
Merge pull request #1005 from alasdairhodge/mariadb-os-detection

Don't rely on sketchy `OsDetails.isLinux()` method.
track if SERVICE_UP previously up, so only execute setupMachine when transitions from false->true. Added comments to areas with issues
Merge pull request #1007 from Nakomis/web-fabric-hadoop-issues

track if SERVICE_UP previously up, so only execute setupMachine when...
remove osgi bundle packaging, instead add osgi MANIFEST.MF to jar (which does the same thing, only better) -- as a fix for https://github.com/brooklyncentral/brooklyn/issues/1008;
main change is in root pom.xml, everything else just changes packaging bundle to jar
downgrade maven-jar-plugin to 2.3.2 (from 2.4) to fix eclipse integration
remove the selenium tests as they just cause problems w eclipse/maven and even CLI maven build, and i think refer to out-dated javascript
XML serialisation: avoid error if try to serialize entity

- If entity/location/policy sneaks through to be serialized
  (e.g. through config key of LocationConfigKeys.CALLER_CONTEXT
  pointing at Entity)...
- Don't blow up: instead let it deserialize as null, which is better
  than failing to serialize+deserialize everything about the entity.
- Logs at WARN for first time encountered, and debug subsequently.
XML persist: fix serializing MutableSet