> Now for a [final run of the entire 
> project](https://jclouds.ci.cloudbees.com/job/DEBUG-jclouds-checkstyle-verify-phase/6/console)...

```
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache jclouds Project ............................ SUCCESS [1:15.989s]
[INFO] jclouds shared Maven resources .................... SUCCESS [21.572s]
[INFO] jclouds Components Core ........................... SUCCESS [2:08.564s]
[INFO] jclouds OpenStack Components Core ................. SUCCESS [13.871s]
[INFO] jclouds commons project ........................... SUCCESS [3.025s]
[INFO] jclouds script builder ............................ SUCCESS [18.828s]
[INFO] jclouds compute core .............................. SUCCESS [42.833s]
[INFO] jclouds Log4J Logging Module ...................... SUCCESS [6.041s]
[INFO] jclouds loadbalancer core ......................... SUCCESS [17.740s]
[INFO] jclouds sts api ................................... SUCCESS [10.594s]
[INFO] jclouds cloudwatch api ............................ SUCCESS [10.696s]
[INFO] jclouds SLF4J Logging Module ...................... SUCCESS [12.224s]
[INFO] jclouds bouncycastle EncryptionService Module ..... SUCCESS [4.846s]
[INFO] jclouds sshj ssh client ........................... SUCCESS [9.879s]
[INFO] jclouds cloudstack core ........................... SUCCESS [57.416s]
[INFO] jclouds blobstore core ............................ SUCCESS [16.593s]
[INFO] jclouds filesystem core ........................... SUCCESS [5.618s]
[INFO] jclouds bring your own node provider .............. SUCCESS [8.910s]
[INFO] jclouds OkHttp Driver ............................. SUCCESS [7.213s]
[INFO] jclouds s3 api .................................... SUCCESS [14.674s]
[INFO] jclouds ec2 api ................................... SUCCESS [26.654s]
[INFO] jclouds sqs api ................................... SUCCESS [10.277s]
[INFO] jclouds vcloud api ................................ SUCCESS [22.933s]
[INFO] jclouds elasticstack core ......................... SUCCESS [14.290s]
[INFO] jclouds atmos components .......................... SUCCESS [19.871s]
[INFO] jclouds openstack-keystone api .................... SUCCESS [13.063s]
[INFO] jclouds swift api ................................. SUCCESS [11.638s]
[INFO] jclouds openstack-cinder api ...................... SUCCESS [5.687s]
[INFO] Apache jclouds :: OpenStack :: Nova API ........... SUCCESS [27.332s]
[INFO] jclouds openstack-nova-ec2 api .................... SUCCESS [6.383s]
[INFO] jclouds openstack-trove api ....................... SUCCESS [10.244s]
[INFO] jclouds cloudfiles api ............................ SUCCESS [9.601s]
[INFO] jclouds cloudservers api .......................... SUCCESS [12.230s]
[INFO] jclouds rackspace cloudidentity api ............... SUCCESS [5.306s]
[INFO] jclouds Rackspace Cloud Load Balancers API ........ SUCCESS [18.736s]
[INFO] jclouds Rackspace Next Generation Cloud Servers US provider  SUCCESS 
[4.783s]
[INFO] jclouds rackspace clouddns api .................... SUCCESS [10.660s]
[INFO] jclouds route53 api ............................... SUCCESS [14.071s]
[INFO] jclouds apis project .............................. SUCCESS [3.068s]
[INFO] jclouds GoGrid provider ........................... SUCCESS [11.873s]
[INFO] jclouds Azure Storage provider .................... SUCCESS [9.582s]
[INFO] jclouds Apache Http Components Client ............. SUCCESS [7.940s]
[INFO] jclouds joda DateService Module ................... SUCCESS [3.696s]
[INFO] jclouds netty payload module ...................... SUCCESS [4.293s]
[INFO] jclouds enterprise Module ......................... SUCCESS [3.806s]
[INFO] jclouds Amazon Simple Storage Service (S3) provider  SUCCESS [10.113s]
[INFO] jclouds Amazon Elastic Load Balancer provider ..... SUCCESS [4.305s]
[INFO] jclouds Amazon EC2 provider ....................... SUCCESS [15.693s]
[INFO] jclouds Amazon Simple Queue Service provider ...... SUCCESS [4.156s]
[INFO] jclouds ElasticHosts Peer1 London provider ........ SUCCESS [5.259s]
[INFO] jclouds ElasticHosts Peer1 San Antonio provider ... SUCCESS [3.866s]
[INFO] jclouds ElasticHosts BlueSquare London provider ... SUCCESS [4.091s]
[INFO] jclouds ElasticHosts Peer1 Toronto provider ....... SUCCESS [4.152s]
[INFO] jclouds ElasticHosts Peer1 Los Angeles provider ... SUCCESS [5.425s]
[INFO] jclouds ElasticHosts Amsterdam provider ........... SUCCESS [4.003s]
[INFO] jclouds ElasticHosts San Jose provider ............ SUCCESS [3.918s]
[INFO] jclouds ElasticHosts Hong Kong provider ........... SUCCESS [3.932s]
[INFO] jclouds ElasticHosts Sydney provider .............. SUCCESS [4.049s]
[INFO] jclouds Open Hosting East1 provider ............... SUCCESS [4.341s]
[INFO] jclouds Serverlove Manchester provider ............ SUCCESS [3.961s]
[INFO] jclouds SkaliCloud Malaysia provider .............. SUCCESS [5.842s]
[INFO] jclouds Go2Cloud Johannesburg1 provider ........... SUCCESS [4.529s]
[INFO] jclouds SoftLayer core ............................ SUCCESS [11.108s]
[INFO] jclouds HP Cloud Compute provider ................. SUCCESS [4.426s]
[INFO] jclouds HP Cloud Block Storage Provider ........... SUCCESS [4.250s]
[INFO] jclouds HP Cloud Object Storage ................... SUCCESS [6.371s]
[INFO] jclouds CloudServers US provider .................. SUCCESS [4.220s]
[INFO] jclouds CloudServers UK provider .................. SUCCESS [4.144s]
[INFO] jclouds CloudFiles US provider .................... SUCCESS [4.216s]
[INFO] jclouds CloudFiles UK provider .................... SUCCESS [3.640s]
[INFO] jclouds Rackspace Next Generation Cloud DNS US provider  SUCCESS [3.717s]
[INFO] jclouds Rackspace Next Generation Cloud DNS UK provider  SUCCESS [3.589s]
[INFO] jclouds Rackspace Cloud Databases US provider ..... SUCCESS [7.451s]
[INFO] jclouds Rackspace Cloud Databases UK provider ..... SUCCESS [4.698s]
[INFO] jclouds Rackspace Cloud Load Balancers US provider  SUCCESS [4.095s]
[INFO] jclouds Rackspace Cloud Load Balancers UK provider  SUCCESS [4.529s]
[INFO] jclouds Rackspace Next Generation Cloud Servers provider  SUCCESS 
[5.329s]
[INFO] jclouds Rackspace Next Generation Cloud Block Storage US provider  
SUCCESS [4.117s]
[INFO] jclouds Rackspace Next Generation Cloud Block Storage UK provider  
SUCCESS [4.232s]
[INFO] jclouds GleSYS core ............................... SUCCESS [11.051s]
[INFO] jclouds Amazon Identity and Access Management (STS) provider  SUCCESS 
[3.637s]
[INFO] jclouds Amazon Route 53 provider .................. SUCCESS [3.657s]
[INFO] jclouds ultradns-ws provider ...................... SUCCESS [10.380s]
[INFO] jclouds dynect api ................................ SUCCESS [8.679s]
[INFO] jclouds providers project ......................... SUCCESS [2.928s]
[INFO] jclouds jsch ssh client ........................... SUCCESS [5.483s]
[INFO] jclouds example components for a standalone compute provider  SUCCESS 
[5.312s]
[INFO] jclouds skeletons project ......................... SUCCESS [3.219s]
[INFO] jclouds Google App Engine Components .............. SUCCESS [12.103s]
[INFO] jclouds drivers project ........................... SUCCESS [2.194s]
[INFO] allcompute ........................................ SUCCESS [7.297s]
[INFO] allblobstore ...................................... SUCCESS [4.878s]
[INFO] allloadbalancer ................................... SUCCESS [3.679s]
[INFO] all ............................................... SUCCESS [5.888s]
[INFO] Apache jclouds .................................... SUCCESS [5.367s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19:16.178s
[INFO] Finished at: Tue Oct 07 00:43:02 EDT 2014
[INFO] Final Memory: 163M/365M
[INFO] ------------------------------------------------------------------------
```
OK! Merged to 
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=e6bf0cc9af726dcbebf4515ae49398ebfd1f8353)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/551#issuecomment-58135763

Reply via email to