Hi Paul, jclouds-all is just an aggregator pom [1] that adds the dependencies to all providers in the *main* repo, but does *not* include the providers in labs. To use those providers you need to manually add the dependencies for the providers you are going to use, vcloud-director [2] in your case.
HTH Ignasi [1] https://github.com/jclouds/jclouds/tree/master/all [2] https://github.com/jclouds/jclouds-labs/blob/master/vcloud-director/pom.xml On 5 November 2013 16:07, Paul Bell <[email protected]> wrote: > Hi again, > > I should have mentioned that I am using the 1.6.1 incubating release. Well, > the project POM contains: > > <dependency> > <groupId>org.apache.jclouds</groupId> > <artifactId>jclouds-all</artifactId> > <version>1.6.1-incubating</version> > </dependency> > <dependency> > <groupId>org.apache.jclouds.driver</groupId> > <artifactId>jclouds-sshj</artifactId> > <version>1.6.1-incubating</version> > </dependency> > > And I do see among the Maven dependencies a bunch of 1.6.1 jar files > including jclouds-all-1.6.1-incubating.jar. > > Thanks again. > > -Paul > > > On Mon, Nov 4, 2013 at 7:45 PM, Andrew Phillips <[email protected]> wrote: >>> >>> I would be most grateful for some guidance in how to go about using >>> jclouds to talk "directly" to VMware's VCD. >> >> >> You should be able to instantiate a context using the "plain" >> 'vcloud-director' API, setting (at minimum) the "endpoint" property for your >> target installation: >> >> Properties overrides = new Properties(); >> overrides.setProperty(..., ...); >> overrides.setProperty(..., ...); >> >> ComputeServiceContext context = >> ContextBuilder.newBuilder("vcloud-director") >> .endpoint("https://your-vloud-ip-or-host/api";) >> .credentials("user@org", "password") >> //.overrides(overrides) - only if needed >> .buildView(ComputeServiceContext.class); >> >> computeService = context.getComputeService(); >> // do something with the compute service >> >> You can see some of the properties you can specific via the overrides in >> the API metadata [1]. You'll notice that providers using the vCloud Director >> API, such as Carrenza, effectively do just that in their provider metadata >> [2]. >> >> What I don't know, however, is whether or how Whirr allows you to specify >> a context such as this one. One of the Whirr-savvy members of the list will >> hopefully be able to help out here! >> >> ap >> >> [1] >> https://github.com/jclouds/jclouds-labs/blob/master/vcloud-director/src/main/java/org/jclouds/vcloud/director/v1_5/VCloudDirectorApiMetadata.java#L59 >> [2] >> https://github.com/jclouds/jclouds-labs/blob/master/carrenza-vcloud-director/src/main/java/org/jclouds/carrenza/vcloud/director/CarrenzaVCloudDirectorProviderMetadata.java#L69 > >
