> +
> +-->
> +<project xmlns="http://maven.apache.org/POM/4.0.0"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> +         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd";>
> +  <modelVersion>4.0.0</modelVersion>
> +  <groupId>org.apache.jclouds.examples</groupId>
> +  <artifactId>google-lb</artifactId>
> +  <version>1.9.0</version>
> +  <name>google-lb</name>
> +  <description>jclouds-labs-google example that shows using the compute 
> specific api and constructing a load balancer.</description>
> +
> +  <properties>
> +    <jclouds.version>1.9.0</jclouds.version>
> +  </properties>
> +
> +  <dependencies>

What do you think about leaving only the required dependencies to run the 
example? (the gce, jclouds-compute and ssh driver ones?).

Users might find easier to get started with their projects by just adding the 
"jclouds-all" dependency, but given that this example is GCE specific, it might 
make sense to have a small dependency set, showing how they can narrow the size 
of their projects. WDYT?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/75/files#r28965955

Reply via email to