Update aws.md

Update to 1.8
Added explicitly required maven dependencies (it's a nightmare for a new user to figure this on his own)
Added explicitly correct imports (some are very confusing)

Need to do the same for S3.
Makes sense :)

(Y)

On Sep 30, 2014, at 10:07 PM, Andrew Phillips <notifications@github.com> wrote:

> In guides/aws.md:
> 
> > +<dependency>
> > +	<groupId>org.apache.jclouds</groupId>
> > +	<artifactId>jclouds-all</artifactId>
> > +	<version>1.8.0</version>
> > +</dependency>
> > +<dependency>
> > +	<groupId>org.apache.jclouds.driver</groupId>
> > +	<artifactId>jclouds-log4j</artifactId>
> > +	<version>1.8.0</version>
> > +</dependency>
> > +<dependency>
> > +	<groupId>org.apache.jclouds.driver</groupId>
> > +	<artifactId>jclouds-sshj</artifactId>
> > +	<version>1.8.0</version>
> > +</dependency>
> > +* Note - make sure that the dependency is 'JAR'
> All in all, this process that may seem like basic maven, is pretty annoying. For your consideration.
> 
> Thanks! That certainly helps. The goal indeed should be (in my opinion, of course), to make the barrier to entry as low as possible...and if finding dependencies and getting the right dep type is non-trivial, we should certainly help users.
> 
> I can imagine a "Getting Started with jclouds and Maven" and/or "Getting Started with jclouds and Eclipse" guide somewhere, with tips such as setting the artifact type to bundle, and things like "how to choose drivers for logging and SSH" or so. The individual API/provider guides would then list the GAVs of the dependencies required for that particular API/provider.
> 
> —
> Reply to this email directly or view it on GitHub.
>