> +<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'
Hi guys. I agree that this is not the perfect place for this, but I wouldt classify this as maven basics - the difficulty is to determine which dependencies are required for each example. The right place for a detailed overview of different artefacts, and what they cover / when they would be required would be here: http://jclouds.apache.org/start/install/ (which currently only shows - indeed maven basics - but is lacking jClouds-maven basics :) Also, In each example, I would recommend including the list of specific dependencies (full maven pom is not required - just a list) For me as a first-time user of the getting started guide, after realising that jclouds-all doesn't cover all dependencies, I used the Eclipse maven plugin to search. I typed clouds, and got: There's org.apache.jclouds.common, org.apache.jclouds.api, org.apache.jclouds.driver, org.apache.jclouds.labs with jclouds-labs-aws, org.apache.jclouds.provider, And to make matters worse, there's also org.jclouds. Moreover, Eclipse sets default type for the dependency to 'bundle', which results in 'artefact not found' even though it is available in the class path. (I spent an hour on this annoying 'bundle' issue alone - nothing to do with jClouds, but if you can save this from other people it would be very nice) All in all, this process that may seem like basic maven, is pretty annoying. For your consideration. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-site/pull/129/files#r18239283
