I’ll check this out. I don’t recall a specific reason for doing it this way, but I have seen a precedent for picking the last match on multiple matches so I might have simply followed that pattern.
If you specify a region by setting jclouds.region property, you should get exactly the one you ask for, so I would think this code could only cause a problem if the calling code made assumptions about which region would be selected internally by jclouds. Thoughts on that? Thanks, Chris -- Chris Custine On July 31, 2014 at 2:43:02 PM, Shrinand Javadekar (shrin...@maginatics.com) wrote: > I hit bug 645[1] with the 1.8.0 RC1 bits. We should fix this before we > release 1.8.0. > > Chris Custine, you made changes to the HPCloud Object Storage code > recently. Do you want to take a look at it? > > Thanks in advance. > -Shri > > [1] https://issues.apache.org/jira/browse/JCLOUDS-645 > > On Thu, Jul 31, 2014 at 10:37 AM, Shrinand Javadekar > wrote: > > I am in the process of verifying the release. I ran into some issues > > with the deprecated methods and have fixed them (at least the code > > compiles). Will run tests against well known blobstores and report the > > results. > > > > On Wed, Jul 30, 2014 at 5:39 AM, Andrew Phillips wrote: > >> This thread is for discussion of the first release candidate for Apache > >> jclouds 1.8.0. Please use this thread for discussion of issues uncovered in > >> the RC, questions you may have about the RC, etc. Thank you. > >> > >> Regards > >> > >> ap > > > > -- > --- > Make the Openstack Summit talks in Paris awesome by voting for our talk! > http://bit.ly/1nO6grS >
