Well, our VCD 1.5 is back up, but I'm having difficulty getting some elementary stuff to work. I've little doubt that this is largely because I'm not quite sure what I'm doing, but it's nonetheless frustrating. 
At any rate, per instructions from folks on the list, I incorporated the "labs" pom into my project. Pom now looks like this:
I then tried to run this code:
 ComputeServiceContext context = ContextBuilder.newBuilder("vcloud-director")
                             .credentials("pbell@MyOrg", "mypassword")
                             //.overrides(overrides) - only if needed
This fails with the following (line 31 is the buildView call):
Exception in thread "main" java.lang.IllegalArgumentException: api {id=vcloud-director, name=vCloud Director 1.5 API, views=[], endpointName=https endpoint, identityName=User at Organization (user@org), credentialName=Optional.of(Password), documentation=http://www.vmware.com/support/pubs/vcd_pubs.html, api=interface org.jclouds.vcloud.director.v1_5.user.VCloudDirectorApi, asyncApi=interface org.jclouds.vcloud.director.v1_5.user.VCloudDirectorAsyncApi} not wrappable as org.jclouds.compute.ComputeServiceContext; context: org.jclouds.vcloud.director.v1_5.VCloudDirectorContext, views: []
       at org.jclouds.ContextBuilder.buildView(ContextBuilder.java:616)
       at org.jclouds.ContextBuilder.buildView(ContextBuilder.java:600)
       at test.VcdTest.main(VcdTest.java:31)

Before I posted this, I looked fairly closely at the sources jar file to see if I could find source code for the some of the test code, but to no avail. If such test source code exists, can someone point me to them. Also, could someone provide me an example of how to:
a. get logged into VCD
b. list vApps
c. define VMs and vApps
d. etc.?
On Tue, Nov 5, 2013 at 10:24 AM, Paul Bell <arachweb@gmail.com> wrote:
Thanks Ignasi and Andrew (nice timing by the way!).
I will tend to this directly. Unfortunately, our in-house VCD seems to be down (mildly frustrating given my interest in getting going with jclouds).

On Tue, Nov 5, 2013 at 10:20 AM, Andrew Phillips <andrewp@apache.org> wrote:
I right away hit a "provider not found" issue concerning provider
"vcloud-director." I noticed in the list of extant providers (about 12
tokens from the end) an entry for "vcloud." Should I be using this one

How is your project set up? "vcloud-director" is a labs provider, you'll need to include it in your project dependencies explicitly: