Return true if the container does not exist -- this matches the
behavior of Atmos and Swift. This allows deleteAndEnsurePathGone to
terminate correctly with S3.
* 'master' of github.com:jclouds/jclouds: (33 commits)
optimize imports
reset loginpassword/privatekey when explicitly set
revised tests that AdminAccess change recently broke
Issue 1028:vCloud Director 1.5: require x-vcloud-authorization header on vcloud api
Add SYSTEM scope from DMTF CIMI. FGCP provider needs it.
Issue-1020 Add full name option for AdminUser and UserAdd
Add missing @Override in TransientStorageStrategy
format and imports
Ensure that EventBus is a singleton
Introduce LocalAsyncBlobStore
Miscellaneous local blobstore cleanups
Prefer valueOf over explicit object creation
Move helper method to TransientStorageStrategy
Move copy(MutableBlobMetadata) to BlobStoreUtils
Cloudstack VirtualMachines can have negative cpuUsed values for some reason
removed dead code
corrected destroyNodes bug
Fixed compilation failures caused by 70fa74df1a6
Remove encodeString() and encodeString(String)
Shuffle blobstore parameters to match superclass
...
* 'master' of github.com:jclouds/jclouds: (30 commits)
Issue 1011: introducing PagedIterable
Transform to work with SaxParser
added @Transform
disabled test that broke cloudbees build
Issue 1022:Move naming convention to Api from Client or Services:: cdmi
merged cdmi changes and fixed classpath issues
Issue 1022:Move naming convention to Api from Client or Services:: glesys jenkins openstack-* opsource-servers savvis-symphonyvpdc cloudwatch cloudidentity rackspace-cloudidentity aws-cloudwatch rackspace-cloudservers-us hpcloud-compute rackspace-cloudservers-us trystack-nova
Issue 1022: naming conventions
cloudstack: removing unnecessary (and in some cases misleading Named annotations). Also removing CloudstackParserModule - handling deserialization in constructors marked with ConstructorProperties annotation
Issue 1022:Move naming convention to Api from Client or Services:: carrenza-vcloud-director
Issue 1022:Move naming convention to Api from Client or Services:: joyent-cloudapi joyentcloud
Issue 1022:Move naming convention to Api from Client or Services:: vcloud-director
cleaned up http builders and expect tests
Fix infinite loops, found by FindBugs
Log hostnames only if they differ
vcloud tidies
nodepool progress and AdminAccessBuilderSpec
Issue 1022: updated aws-elb aws-iam aws-rds iam elb rds to new naming conventions
Issue 1022: added BaseRestApiExpectTest
swift keystone 2.0: applying defaultProperties()
...
Prior to this commit, jclouds wouldn't allow you to interact with any buckets
in S3 that were named with uppercase characters. Per AWS S3 docs, this
non-standard naming is valid in US regions only. This update fixes jclouds so
that it can interact with, and even attempt to create, buckets with uppercase
characters for AWS S3 without actually impacting other S3 implementations. This
fix also will not have any impact in non-US regions other than instead of a
bucket name validation error you'll get an InvalidBucketName error back from
AWS S3 when you attempt to create a bucket with an uppercase character in a
non-US region. To summarize, nothing changes other than US regions now allow
creation of bucket names with upper case characters and jclouds now can
interact with these non-standard named buckets without failure.
