Validating an Apache jclouds release involves verifying the following:
Some steps require a manual verification, and others are fully automated. The following scripts can be used:
On your local machine create a directory and a pom.xml file to download the release candidate JARs from the staging repo. In the [VOTE] thread look for the "Maven staging repos" section and replace the xxxx below with the value from the "Maven staging repos" section.
<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> <properties> <jclouds.version>1.6.3</jclouds.version> </properties> <groupId>org.apache.jclouds</groupId> <artifactId>jclouds-staging</artifactId> <version>1.0</version> <dependencies> <dependency> <groupId>org.apache.jclouds</groupId> <artifactId>jclouds-all</artifactId> <version>${jclouds.version}</version> </dependency> <!-- Add any jclouds additional dependency here --> </dependencies> <profiles> <profile> <id>jclouds-staging</id> <repositories> <repository> <id>jclouds-staging</id> <url>https://repository.apache.org/content/repositories/orgapachejclouds-xxxx/</url> </repository> </repositories> </profile> </profiles> </project> |
Run the command mvn clean -Pjclouds-staging dependency:copy-dependencies "-DoutputDirectory=./lib" -U to download the JARs to a lib directory. At the end of it you should have a simple directory structure like so.
jclouds-1.9.2$ ls lib/ pom.xml |
With the lib directory full of jclouds JARs. You can now use these JARs to do things like run the jclouds-examples. If something goes wrong, notify the dev list.