On Wed, Mar 09, 2016 at 01:50:40PM -0500, Andrew Phillips wrote: > package org.jclouds.azureblob > [+] AzureBlobClient.copyBlob ( URI p1, String p2, String p3, > CopyBlobOptions p4 ) [abstract] : void (1)
I changed this method to return the ETag from the response. It is not binary compatible but is source compatible with previous releases. > package org.jclouds.blobstore.options > CopyOptions.Builder.contentMetadata ( ContentMetadata > contentMetadata ) : CopyOptions.Builder (1) > CopyOptions.Builder.userMetadata ( Map<String,String> userMetadata ) > : CopyOptions.Builder (1) These method break source compatibility but CopyOptions has a @Beta annotation. > Are these actually "real" problems, or false positives? This report has a lot of noise due to tests. Can we exclude these? Many of the removal warnings have proper deprecation tags although others like CloudFilesBlobStore were deprecated via informal means. -- Andrew Gaul http://gaul.org/
