Hi, Yaron. Appreciate your interest. I will give you some hints.
1. Fork jclouds on github and make sure you work on a branch of master for anything you would like to go in th project. 2. Import project from maven in eclipse. Use jdk 7, but language level 6. 3. Use this formatter http://wiki.apache.org/jclouds/Coding%20Standards 4. Check jclouds.org, the wiki, and do markmail searches. Jclouds hasn't changed fundamentally, but last notable change was undoing async. IOTW, there is a high chance questions have been asked, and the code referenced is similar if not same. Hope this helps On Nov 23, 2014 3:45 AM, "Yaron Rosenbaum" <[email protected]> wrote: > Adrian, > > Although not on the same subject as the original email: > If you help me understand the project structure, and create a dev env in > Eclipse - I promise I will contribute back and help wherever I can. I'm not > being lazy - I did spend quite a lot of time on this, but I find that the > structure and set of idiom secrecies of this specific project are a bit > complex. > > > (Y) > > > On Nov 21, 2014, at 7:05 PM, Adrian Cole <[email protected]> > wrote: > > > >> Yes, I know - I tried tracking it down myself. I find the jClouds code > a bit hard to comprehend. > > understood.. try maintaining it :) > > > >> BTW > >> 50-1000 msecs are insanely small numbers IMO. No wonder AWS returned > errors > > yeah, it is silly for spot instances, but some clouds start vms in > > well under 30 seconds, so not terrible there. > >
