I don't see anything wrong in your config. The wire and header logging
happens here [1], and this is the method [2] used to log the headers. Could
you debug it to verify that the headers are in place?
I.
[1]
https://github.com/jclouds/jclouds/blob/master/core/src/main/java/org/jclouds/http/intern
This makes me think that it may be better to have the project ID as a
context-wide parameter, and any time the compute service calls a
project-aware operation, it fills in the project ID. Security groups
are an example of something else that lives in project namespaces. Is
this a good route?
Wou
I'm not familiar with the APIs of other storage offerings like Google Drive
or Dropbox, but I'm not sure if they should fall in the same category. My
little knowledge suggests thay they don't have the same purpose. "Object
storage" and "document storage" (which is the topic of your thesis) sound
l
I also received some old notifications.
I'm not aware of any changes made to the repo itself that would be
causing this...does it affect other repos too, or just labs-aws?
ap
PS: I don't seem to have received any old notifications, by the way.
Here it is: https://github.com/jclouds/jclouds/pull/361
The warning about the RAT plugin has disappeared with this parent pom.
On 11 May 2014 23:18, Andrew Phillips wrote:
>> We could update the parent pom to version 14, which already updates the
>> rat
>> plugin from 0.8 to 0.10 and see if the w
