Modified: jclouds/site-content/releasenotes/atom.xml URL: http://svn.apache.org/viewvc/jclouds/site-content/releasenotes/atom.xml?rev=1691278&r1=1691277&r2=1691278&view=diff ============================================================================== --- jclouds/site-content/releasenotes/atom.xml (original) +++ jclouds/site-content/releasenotes/atom.xml Wed Jul 15 21:33:43 2015 @@ -13,77 +13,95 @@ <title type="html"><![CDATA[Release Notes for Version 1.9.0]]></title> <link href="http://jclouds.apache.org/releasenotes/1.9.0/"/> <updated>2015-03-29T00:00:00Z</updated> - <content type="html">< -1. [Core](#core-improvements) -1. [Compute improvements](#compute-improvements) -1. [BlobStore improvements](#blobstore-improvements) -1. [API Changes](#api) -1. [Known Issues](#issues) -1. [Credits](#credits) -1. [Test Results](#test) + <content type="html"><. You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329006&styleName=Html&projectId=12314430). +<h2><a id="intro"></a>Introduction</h2> -To get started with jclouds, please see the [jclouds installation guide](/start/install/). +<p>You can read the official announcement at <a href="http://markmail.org/message/zd4cqypgrwwmogfy";>Apache jclouds 1.9.0 released</a>. You can read the details of the specific JIRA issues addressed in this release at the <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12329006&styleName=Html&projectId=12314430";>JIRA Release Notes</a>.</p> -## <a id="core-improvements"></a>Core improvements +<p>To get started with jclouds, please see the <a href="/start/install/">jclouds installation guide</a>.</p> -* Configured the [Animal Sniffer](http://mojo.codehaus.org/animal-sniffer/) plugin to make sure the code is runtime compatible with Java 6. This will help us support Android. -* Refactored the OkHttp driver to use the native API -* Added a clean way to customize SSL/TLS connections using the OkHttp driver to avoid POODLE. +<h2><a id="core-improvements"></a>Core improvements</h2> -## <a id="compute-improvements"></a>Compute improvements +<ul> +<li>Configured the <a href="http://mojo.codehaus.org/animal-sniffer/";>Animal Sniffer</a> plugin to make sure the code is runtime compatible with Java 6. This will help us support Android.</li> +<li>Refactored the OkHttp driver to use the native API</li> +<li>Added a clean way to customize SSL/TLS connections using the OkHttp driver to avoid POODLE.</li> +</ul> -* Added AWS Frankfurt region -* Added AWS signature v4 -* Added C4 instance types to AWS EC2 -* Initial support for Azure Compute -* Added authentication to the Docker provider -* Added the ProfitBricks API -* Added the Shipyard API -* Added San José and Honolulu regions to CloudSigma -* Improved Google Compute Engine Compute support -* Chef has been promoted to the main repo and updated to support Chef 12 -* Improved Google Compute Engine to use AutoValue -## <a id="blobstore-improvements"></a>BlobStore improvements +<h2><a id="compute-improvements"></a>Compute improvements</h2> -* Support for > 2 GB single-part uploads on Java 7 -* Support portable setting and getting container and object ACLs (public-read and private) -* Support portable multi-object delete -* Improved multi-part upload compatibility with InputStream Payload -* Add support for user metadata with filesystem provider -* Add multi-part upload support for generic S3 +<ul> +<li>Added AWS Frankfurt region</li> +<li>Added AWS signature v4</li> +<li>Added C4 instance types to AWS EC2</li> +<li>Initial support for Azure Compute</li> +<li>Added authentication to the Docker provider</li> +<li>Added the ProfitBricks API</li> +<li>Added the Shipyard API</li> +<li>Added San José and Honolulu regions to CloudSigma</li> +<li>Improved Google Compute Engine Compute support</li> +<li>Chef has been promoted to the main repo and updated to support Chef 12</li> +<li>Improved Google Compute Engine to use AutoValue</li> +</ul> -## <a id="api"></a>API Changes +<h2><a id="blobstore-improvements"></a>BlobStore improvements</h2> -* Downgraded Guava dependency to 16.0.1 but code will now support also versions 17 and 18. -* Removed all async interfaces from all apis and providers -* Generic S3 no longer defaults to an AWS endpoint -* Require Azure API 2012-02-12 to allow support after [August 2015](http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx) -* Require Java 7 to use filesystem provider (enables user metadata support) +<ul> +<li>Support for > 2 GB single-part uploads on Java 7</li> +<li>Support portable setting and getting container and object ACLs (public-read and private)</li> +<li>Support portable multi-object delete</li> +<li>Improved multi-part upload compatibility with InputStream Payload</li> +<li>Add support for user metadata with filesystem provider</li> +<li>Add multi-part upload support for generic S3</li> +</ul> -## <a id="issues"></a>Known Issues +<h2><a id="api"></a>API Changes</h2> -* Amazon S3 does not support signature v4 or Frankfurt -* Filesystem provider does not support user metadata on Mac OS X due to [OpenJDK issue 8030048](https://bugs.openjdk.java.net/browse/JDK-8030048) +<ul> +<li>Downgraded Guava dependency to 16.0.1 but code will now support also versions 17 and 18.</li> +<li>Removed all async interfaces from all apis and providers</li> +<li>Generic S3 no longer defaults to an AWS endpoint</li> +<li>Require Azure API 2012-02-12 to allow support after <a href="http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx";>August 2015</a></li> +<li>Require Java 7 to use filesystem provider (enables user metadata support)</li> +</ul> -## <a id="credits"></a>Credits +<h2><a id="issues"></a>Known Issues</h2> -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: +<ul> +<li>Amazon S3 does not support signature v4 or Frankfurt</li> +<li>Filesystem provider does not support user metadata on Mac OS X due to <a href="https://bugs.openjdk.java.net/browse/JDK-8030048";>OpenJDK issue 8030048</a></li> +</ul> -* Google and Microsoft for providing resources to support and develop the Google Compute Engine and Azure Compute providers. -* Apache jclouds [PMC](http://people.apache.org/committers-by-project.html#jclouds-pmc) and community for verifying the release. -* Check out who has been busy on [Open Hub](https://www.openhub.net/p/jclouds/contributors?query=&sort=latest_commit). -## <a id="test"></a>Test Results +<h2><a id="credits"></a>Credits</h2> -Please see the [discussion thread](http://markmail.org/message/wpxvq4m326z6j5kk) and the [vote thread](http://markmail.org/message/mevukaykuuhksrzp) for test results for 1.9.0. +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> + +<ul> +<li>Google and Microsoft for providing resources to support and develop the Google Compute Engine and Azure Compute providers.</li> +<li>Apache jclouds <a href="http://people.apache.org/committers-by-project.html#jclouds-pmc";>PMC</a> and community for verifying the release.</li> +<li>Check out who has been busy on <a href="https://www.openhub.net/p/jclouds/contributors?query=&sort=latest_commit";>Open Hub</a>.</li> +</ul> + + +<h2><a id="test"></a>Test Results</h2> + +<p>Please see the <a href="http://markmail.org/message/wpxvq4m326z6j5kk";>discussion thread</a> and the <a href="http://markmail.org/message/mevukaykuuhksrzp";>vote thread</a> for test results for 1.9.0.</p> ]]></content> </entry> @@ -92,62 +110,80 @@ Please see the [discussion thread](http: <title type="html"><![CDATA[Release Notes for Version 1.8.1]]></title> <link href="http://jclouds.apache.org/releasenotes/1.8.1/"/> <updated>2014-10-24T00:00:00Z</updated> - <content type="html">< -1. [Highlights](#highlights) -1. [API Changes](#api) -1. [Known Issues](#issues) -1. [Credits](#credits) -1. [Test Results](#test) + <content type="html"><. You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12327548&styleName=Html&projectId=12314430). +<p>from</p> -To get jclouds, please see the [jclouds installation guide](/start/install/). +<div class="highlight"><pre><code class="xml"><span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds.labs<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>openstack-swift<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.8.0<span class="nt"></version></span> +<span class="nt"></dependency></span> +</code></pre></div> -## <a id="highlights"></a>Highlights -* Support for Google Cloud Storage -* Graduation of OpenStack Swift. The group ID changes +<p>to</p> -from -{% highlight xml %} -<dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>openstack-swift</artifactId> - <version>1.8.0</version> -</dependency> -{% endhighlight %} -to -{% highlight xml %} -<dependency> - <groupId>org.apache.jclouds.apis</groupId> - <artifactId>openstack-swift</artifactId> - <version>1.8.1</version> -</dependency> -{% endhighlight %} +<div class="highlight"><pre><code class="xml"><span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds.apis<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>openstack-swift<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.8.1<span class="nt"></version></span> +<span class="nt"></dependency></span> +</code></pre></div> -## <a id="api"></a>API Changes +<h2><a id="api"></a>API Changes</h2> -* [openstack-swift API changes from 1.8.0 to 1.8.1](api-changes/openstack-swift/) +<ul> +<li><a href="api-changes/openstack-swift/">openstack-swift API changes from 1.8.0 to 1.8.1</a></li> +</ul> -## <a id="issues"></a>Known Issues -* Unfortunately `openstack-neutron` was broken in this release. If you depend on it, please skip this version. +<h2><a id="issues"></a>Known Issues</h2> -## <a id="credits"></a>Credits +<ul> +<li>Unfortunately <code>openstack-neutron</code> was broken in this release. If you depend on it, please skip this version.</li> +</ul> -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: -* Apache jclouds [PMC](http://people.apache.org/committers-by-project.html#jclouds-pmc) and community for verifying the release. -* Check out who has been busy on [Open Hub](https://www.openhub.net/p/jclouds/contributors?query=&sort=latest_commit). +<h2><a id="credits"></a>Credits</h2> -## <a id="test"></a>Test Results +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> -Please see the [discussion thread](http://markmail.org/thread/lertwftpifagoor3) and the [vote thread](http://markmail.org/thread/lertwftpifagoor3) for test results for 1.8.1. +<ul> +<li>Apache jclouds <a href="http://people.apache.org/committers-by-project.html#jclouds-pmc";>PMC</a> and community for verifying the release.</li> +<li>Check out who has been busy on <a href="https://www.openhub.net/p/jclouds/contributors?query=&sort=latest_commit";>Open Hub</a>.</li> +</ul> -See [this blog post](/blog/2014/10/25/poodle-and-jclouds/) for more information on POODLE and jclouds.]]></content> + +<h2><a id="test"></a>Test Results</h2> + +<p>Please see the <a href="http://markmail.org/thread/lertwftpifagoor3";>discussion thread</a> and the <a href="http://markmail.org/thread/lertwftpifagoor3";>vote thread</a> for test results for 1.8.1.</p> + +<p>See <a href="/blog/2014/10/25/poodle-and-jclouds/">this blog post</a> for more information on POODLE and jclouds.</p> +]]></content> </entry> <entry> @@ -155,51 +191,67 @@ See [this blog post](/blog/2014/10/25/po <title type="html"><![CDATA[Release Notes for Version 1.8.0]]></title> <link href="http://jclouds.apache.org/releasenotes/1.8.0/"/> <updated>2014-08-05T00:00:00Z</updated> - <content type="html">< -1. [Highlights](#highlights) -1. [API Changes](#api) -1. [Known Issues](#issues) -1. [Reminder](#reminder) -1. [Credits](#credits) -1. [Test Results](#test) + <content type="html"><. You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325587&styleName=Html&projectId=12314430). +<p>You can read the official announcement at <a href="http://markmail.org/message/plk6wedjeh3vanc6";>Apache jclouds 1.8.0 released</a>. You can read the details of the specific JIRA issues addressed in this release at the <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325587&styleName=Html&projectId=12314430";>JIRA Release Notes</a>.</p> -To get jclouds, please see the [jclouds installation guide](/start/install/). +<p>To get jclouds, please see the <a href="/start/install/">jclouds installation guide</a>.</p> -## <a id="highlights"></a>Highlights +<h2><a id="highlights"></a>Highlights</h2> -* jclouds 1.8.0 introduces initial support for [Amazon Glacier](http://aws.amazon.com/glacier), sponsored by [Google Summer of Code](/blog/2014/04/23/gsoc/) and written by Roman Coedo. This blobstore provider includes support for the portable abstraction but has vastly different semantics for blob naming and retrieval. -* Support for [Docker](/guides/docker/). -* Refactored Code supporting OpenStack Neutron. -* New Rackspace Auto Scale UK Provider and updated US region support. -* This release requires Guava 17.0 and transitions most uses of `InputSupplier` to `ByteSource`. +<ul> +<li>jclouds 1.8.0 introduces initial support for <a href="http://aws.amazon.com/glacier";>Amazon Glacier</a>, sponsored by <a href="/blog/2014/04/23/gsoc/">Google Summer of Code</a> and written by Roman Coedo. This blobstore provider includes support for the portable abstraction but has vastly different semantics for blob naming and retrieval.</li> +<li>Support for <a href="/guides/docker/">Docker</a>.</li> +<li>Refactored Code supporting OpenStack Neutron.</li> +<li>New Rackspace Auto Scale UK Provider and updated US region support.</li> +<li>This release requires Guava 17.0 and transitions most uses of <code>InputSupplier</code> to <code>ByteSource</code>.</li> +</ul> -## <a id="api"></a>API Changes -* This release removes or deprecates most uses of Guava `InputSupplier`, including `Strings2.toString`. Callers should instead use `ByteSource`, `ByteStreams2.toByteArrayAndClose`, or `Strings2.toStringAndClose`. These changes ensure compatibility with future Guava releases. -* `BlobStore` introduces a `deleteContainerIfEmpty` method which more accurately matches the semantics of some providers. Some providers like Azure have better performance with the existing `delete` method. -* The `resumeNodesMatching`, `suspendNodesMatching` and `rebootNodesMatching` of the `ComputeService` now return the affected nodes. -* Deprecates Neutron v2_0. Superseded by [v2](https://github.com/jclouds/jclouds-labs-openstack/tree/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2). Moves the code away from map-binders and parsers. Multiple interface changes. -* `RegionScopedBlobStoreContext` deprecates `configuredRegions()`, `blobStoreInRegion(String regionId)`, `signerInRegion(String regionId)`, and `asyncBlobStoreInRegion(String regionId)`. +<h2><a id="api"></a>API Changes</h2> -## <a id="issues"></a>Known Issues +<ul> +<li>This release removes or deprecates most uses of Guava <code>InputSupplier</code>, including <code>Strings2.toString</code>. Callers should instead use <code>ByteSource</code>, <code>ByteStreams2.toByteArrayAndClose</code>, or <code>Strings2.toStringAndClose</code>. These changes ensure compatibility with future Guava releases.</li> +<li><code>BlobStore</code> introduces a <code>deleteContainerIfEmpty</code> method which more accurately matches the semantics of some providers. Some providers like Azure have better performance with the existing <code>delete</code> method.</li> +<li>The <code>resumeNodesMatching</code>, <code>suspendNodesMatching</code> and <code>rebootNodesMatching</code> of the <code>ComputeService</code> now return the affected nodes.</li> +<li>Deprecates Neutron v2_0. Superseded by <a href="https://github.com/jclouds/jclouds-labs-openstack/tree/master/openstack-neutron/src/main/java/org/jclouds/openstack/neutron/v2";>v2</a>. Moves the code away from map-binders and parsers. Multiple interface changes.</li> +<li><code>RegionScopedBlobStoreContext</code> deprecates <code>configuredRegions()</code>, <code>blobStoreInRegion(String regionId)</code>, <code>signerInRegion(String regionId)</code>, and <code>asyncBlobStoreInRegion(String regionId)</code>.</li> +</ul> -* Starting with 1.8.0, the HP Cloud Object Storage provider requires the `region` attribute to be specified explicitly. This attribute is now used to select the appropriate endpoint. If the region is not explicitly set, an arbitrary endpoint will be selected, which may differ from the endpoint chosen when using previous versions of jclouds. See the [provider guide](/guides/hpcloud/) for an example of how to specify the region. -* 1.8.0 includes an [incomplete artifact](http://search.maven.org/#artifactdetails%7Corg.apache.jclouds.labs%7Cgoogle-cloud-storage%7C1.8.0%7Cjar) for Google Cloud Storage. The jclouds team does not recommend its use and 1.8.1 will either complete support or remove this artifact. -## <a id="credits"></a>Credits +<h2><a id="issues"></a>Known Issues</h2> -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: +<ul> +<li>Starting with 1.8.0, the HP Cloud Object Storage provider requires the <code>region</code> attribute to be specified explicitly. This attribute is now used to select the appropriate endpoint. If the region is not explicitly set, an arbitrary endpoint will be selected, which may differ from the endpoint chosen when using previous versions of jclouds. See the <a href="/guides/hpcloud/">provider guide</a> for an example of how to specify the region.</li> +<li>1.8.0 includes an <a href="http://search.maven.org/#artifactdetails%7Corg.apache.jclouds.labs%7Cgoogle-cloud-storage%7C1.8.0%7Cjar";>incomplete artifact</a> for Google Cloud Storage. The jclouds team does not recommend its use and 1.8.1 will either complete support or remove this artifact.</li> +</ul> -* Apache jclouds [PMC](http://people.apache.org/committers-by-project.html#jclouds-pmc) and community for verifying the release. -* Check out who has been busy on [Open Hub](https://www.openhub.net/p/jclouds/contributors?query=&sort=latest_commit). -## <a id="test"></a>Test Results +<h2><a id="credits"></a>Credits</h2> -Please see the [discussion thread](http://markmail.org/thread/2ppvzd7dtjvqfqkk) and the [vote thread](http://markmail.org/thread/7ixght2jgfbu73ok) for test results for 1.8.0.]]></content> +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> + +<ul> +<li>Apache jclouds <a href="http://people.apache.org/committers-by-project.html#jclouds-pmc";>PMC</a> and community for verifying the release.</li> +<li>Check out who has been busy on <a href="https://www.openhub.net/p/jclouds/contributors?query=&sort=latest_commit";>Open Hub</a>.</li> +</ul> + + +<h2><a id="test"></a>Test Results</h2> + +<p>Please see the <a href="http://markmail.org/thread/2ppvzd7dtjvqfqkk";>discussion thread</a> and the <a href="http://markmail.org/thread/7ixght2jgfbu73ok";>vote thread</a> for test results for 1.8.0.</p> +]]></content> </entry> <entry> @@ -207,78 +259,92 @@ Please see the [discussion thread](http: <title type="html"><![CDATA[Release Notes for Version 1.7.3]]></title> <link href="http://jclouds.apache.org/releasenotes/1.7.3/"/> <updated>2014-05-30T00:00:00Z</updated> - <content type="html">< -1. [Highlights](#highlights) -1. [Known Issues](#issues) -1. [Reminder](#reminder) -1. [Credits](#credits) -1. [Test Results](#test) - -## <a id="intro"></a>Introduction - -You can read the official announcement at [Apache jclouds 1.7.3 released](http://jclouds.markmail.org/message/6ormro7calbt5tjn). You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND%20fixVersion%20%3D%201.7.3). - -To get jclouds, please see the [jclouds installation guide](/start/install/). - -## <a id="highlights"></a>Highlights - -* ElasticStack is back. The elasticstack API has been fixed and the elastichosts-* Providers are in good working condition again. -* The swift API and cloudfiles-us & cloudfiles-uk Providers have been deprecated as of jclouds 1.7.2. -* They will be replaced with the openstack-swift API and rackspace-cloudfiles-us & rackspace-cloudfiles-uk & hpcloud-objectstorage Providers in jclouds 2.0. -* The new APIs and providers have been updated to the current jclouds interface style and are fully region aware. These APIs are new to jclouds and hence are in Beta. That means we need people to use it and give us [feedback](/community/). Based on that feedback, minor changes to the interfaces may happen. This code will replace org.jclouds.openstack.swift.SwiftClient in jclouds 2.0 and it is recommended you adopt it sooner than later. -* You can get the new Swift and Cloud Files dependencies with: - -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>openstack-swift</artifactId> - <version>1.7.3</version> - </dependency> - <dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>rackspace-cloudfiles-us</artifactId> - <version>1.7.3</version> - </dependency> - <dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>rackspace-cloudfiles-uk</artifactId> - <version>1.7.3</version> - </dependency> -</dependencies> -{% endhighlight %} - -* Here is the [Javadoc](/reference/javadoc/1.7.x/) for the new Swift and Cloud Files classes. - -## <a id="issues"></a>Known Issues - -* jclouds 1.7.3 is incompatible with [Guava](https://code.google.com/p/guava-libraries/) 16 and 17. Please switch to Guava 15.0 or earlier, or wait for jclouds 1.8. - -## <a id="reminder"></a>Reminder - -The jclouds Maven group ID for versions since [1.6.1-incubating](../1.6.1) is `org.apache.jclouds` rather than `org.jclouds`, so a pom.xml dependency would now look like: - -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds</groupId> - <artifactId>jclouds-all</artifactId> - <version>1.7.3</version> - </dependency> -</dependencies> -{% endhighlight %} - -## <a id="credits"></a>Credits + <content type="html">< and community for verifying the release. -* Check out who has been busy [here](http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit). +<ul> +<li>Apache jclouds <a href="http://people.apache.org/committers-by-project.html#jclouds-pmc";>PMC</a> and community for verifying the release.</li> +<li>Check out who has been busy <a href="http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit";>here</a>.</li> +</ul> -## <a id="test"></a>Test Results -Please see the [discussion thread](http://jclouds.markmail.org/message/smznp6474kpojqeb) and the [vote thread](http://jclouds.markmail.org/message/ydekpm36pwaqpvbf) for test results for 1.7.3. +<h2><a id="test"></a>Test Results</h2> +<p>Please see the <a href="http://jclouds.markmail.org/message/smznp6474kpojqeb";>discussion thread</a> and the <a href="http://jclouds.markmail.org/message/ydekpm36pwaqpvbf";>vote thread</a> for test results for 1.7.3.</p> ]]></content> </entry> @@ -287,79 +353,93 @@ Please see the [discussion thread](http: <title type="html"><![CDATA[Release Notes for Version 1.7.2]]></title> <link href="http://jclouds.apache.org/releasenotes/1.7.2/"/> <updated>2014-04-15T00:00:00Z</updated> - <content type="html">< -1. [Highlights](#highlights) -1. [Known Issues](#issues) -1. [Reminder](#reminder) -1. [Credits](#credits) -1. [Test Results](#test) - -## <a id="intro"></a>Introduction - -jclouds version 1.7.2 is the fourth release of jclouds as an Apache TLP. - -You can read the official announcement at [Apache jclouds 1.7.2 released](http://markmail.org/message/on6prwzxi2cbi3mr). You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND%20fixVersion%20%3D%201.7.2). - -To get jclouds, please see the [jclouds installation guide](/start/install/). - -## <a id="highlights"></a>Highlights - -* The swift API and cloudfiles-us & cloudfiles-uk Providers have been deprecated as of jclouds 1.7.2. -* They will be replaced with the openstack-swift API and rackspace-cloudfiles-us & rackspace-cloudfiles-uk & hpcloud-objectstorage Providers in jclouds 2.0. -* The new APIs and providers have been updated to the current jclouds interface style and are fully region aware. These APIs are new to jclouds and hence are in Beta. That means we need people to use it and give us [feedback](/community/). Based on that feedback, minor changes to the interfaces may happen. This code will replace org.jclouds.openstack.swift.SwiftClient in jclouds 2.0 and it is recommended you adopt it sooner than later. -* You can get the new Swift and Cloud Files dependencies with: - -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>openstack-swift</artifactId> - <version>1.7.2</version> - </dependency> - <dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>rackspace-cloudfiles-us</artifactId> - <version>1.7.2</version> - </dependency> - <dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>rackspace-cloudfiles-uk</artifactId> - <version>1.7.2</version> - </dependency> -</dependencies> -{% endhighlight %} - -* Here is the [Javadoc](/reference/javadoc/1.7.x/) for the new Swift and Cloud Files classes. - -## <a id="issues"></a>Known Issues - -* jclouds 1.7.2 is incompatible with [Guava](https://code.google.com/p/guava-libraries/) 16 and 17. Please switch to Guava 15.0 or earlier, or wait for jclouds 1.8. - -## <a id="reminder"></a>Reminder - -The jclouds Maven group ID for versions since [1.6.1-incubating](../1.6.1) is `org.apache.jclouds` rather than `org.jclouds`, so a pom.xml dependency would now look like: - -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds</groupId> - <artifactId>jclouds-all</artifactId> - <version>1.7.2</version> - </dependency> -</dependencies> -{% endhighlight %} - -## <a id="credits"></a>Credits + <content type="html">< and community for verifying the release. -* Check out who has been busy [here](http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit). +<h2><a id="intro"></a>Introduction</h2> -## <a id="test"></a>Test Results +<p>jclouds version 1.7.2 is the fourth release of jclouds as an Apache TLP.</p> -Please see the [release discussion thread](http://markmail.org/thread/zi5nnppwdvaafpsb) for test results for 1.7.2. +<p>You can read the official announcement at <a href="http://markmail.org/message/on6prwzxi2cbi3mr";>Apache jclouds 1.7.2 released</a>. You can read the details of the specific JIRA issues addressed in this release at the <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20JCLOUDS%20AND%20fixVersion%20%3D%201.7.2";>JIRA Release Notes</a>.</p> +<p>To get jclouds, please see the <a href="/start/install/">jclouds installation guide</a>.</p> + +<h2><a id="highlights"></a>Highlights</h2> + +<ul> +<li>The swift API and cloudfiles-us & cloudfiles-uk Providers have been deprecated as of jclouds 1.7.2.</li> +<li>They will be replaced with the openstack-swift API and rackspace-cloudfiles-us & rackspace-cloudfiles-uk & hpcloud-objectstorage Providers in jclouds 2.0.</li> +<li>The new APIs and providers have been updated to the current jclouds interface style and are fully region aware. These APIs are new to jclouds and hence are in Beta. That means we need people to use it and give us <a href="/community/">feedback</a>. Based on that feedback, minor changes to the interfaces may happen. This code will replace org.jclouds.openstack.swift.SwiftClient in jclouds 2.0 and it is recommended you adopt it sooner than later.</li> +<li>You can get the new Swift and Cloud Files dependencies with:</li> +</ul> + + +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds.labs<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>openstack-swift<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.7.2<span class="nt"></version></span> + <span class="nt"></dependency></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds.labs<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>rackspace-cloudfiles-us<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.7.2<span class="nt"></version></span> + <span class="nt"></dependency></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds.labs<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>rackspace-cloudfiles-uk<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.7.2<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> + + +<ul> +<li>Here is the <a href="/reference/javadoc/1.7.x/">Javadoc</a> for the new Swift and Cloud Files classes.</li> +</ul> + + +<h2><a id="issues"></a>Known Issues</h2> + +<ul> +<li>jclouds 1.7.2 is incompatible with <a href="https://code.google.com/p/guava-libraries/";>Guava</a> 16 and 17. Please switch to Guava 15.0 or earlier, or wait for jclouds 1.8.</li> +</ul> + + +<h2><a id="reminder"></a>Reminder</h2> + +<p>The jclouds Maven group ID for versions since <a href="../1.6.1">1.6.1-incubating</a> is <code>org.apache.jclouds</code> rather than <code>org.jclouds</code>, so a pom.xml dependency would now look like:</p> + +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>jclouds-all<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.7.2<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> + + +<h2><a id="credits"></a>Credits</h2> + +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> + +<ul> +<li>Apache jclouds <a href="http://people.apache.org/committers-by-project.html#jclouds-pmc";>PMC</a> and community for verifying the release.</li> +<li>Check out who has been busy <a href="http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit";>here</a>.</li> +</ul> + + +<h2><a id="test"></a>Test Results</h2> + +<p>Please see the <a href="http://markmail.org/thread/zi5nnppwdvaafpsb";>release discussion thread</a> for test results for 1.7.2.</p> ]]></content> </entry> @@ -368,64 +448,77 @@ Please see the [release discussion threa <title type="html"><![CDATA[Release Notes for Version 1.7.1]]></title> <link href="http://jclouds.apache.org/releasenotes/1.7.1/"/> <updated>2014-02-11T00:00:00Z</updated> - <content type="html"><. You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/browse/JCLOUDS/fixforversion/12325588). +<p>You can read the official announcement at <a href="http://markmail.org/message/wvskzm356n2mraif";>Apache jclouds 1.7.1 released</a>. You can read the details of the specific JIRA issues addressed in this release at the <a href="https://issues.apache.org/jira/browse/JCLOUDS/fixforversion/12325588";>JIRA Release Notes</a>.</p> -To get jclouds, please see the [jclouds installation guide](/start/install/). +<p>To get jclouds, please see the <a href="/start/install/">jclouds installation guide</a>.</p> -## Notable updates +<h2>Notable updates</h2> -* A workaround for [JCLOUDS-427](https://issues.apache.org/jira/browse/JCLOUDS-427) is provided to make jclouds compatible with JRE 1.7.0\_51-b13. -* Added the [DigitalOcean](https://www.digitalocean.com) compute provider. It is available in labs under the following Maven coordinates: -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds.labs</groupId> - <artifactId>digitalocean</artifactId> - <version>1.7.1</version> - </dependency> -</dependencies> -{% endhighlight %} -* Upgraded Bouncycastle to version 1.49. -* Added an HTTP driver based on the [OkHttp](http://square.github.io/okhttp/) library for efficient HTTP connections. -* Added support for PATCH methods that have a body. -* Allow configuring of networks to which the nodes will be attached directly from the portable [Compute](/start/compute) interface. +<ul> +<li>A workaround for <a href="https://issues.apache.org/jira/browse/JCLOUDS-427";>JCLOUDS-427</a> is provided to make jclouds compatible with JRE 1.7.0_51-b13.</li> +<li>Added the <a href="https://www.digitalocean.com";>DigitalOcean</a> compute provider. It is available in labs under the following Maven coordinates:</li> +</ul> -## Notes -* jclouds 1.7.1 is incompatible with [Guava](https://code.google.com/p/guava-libraries/) 16. Please switch to -Guava 15.0 or earlier, or wait for jclouds 1.8. +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds.labs<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>digitalocean<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.7.1<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> -## Reminder -As per [1.6.1-incubating](../1.6.1), the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like: +<ul> +<li>Upgraded Bouncycastle to version 1.49.</li> +<li>Added an HTTP driver based on the <a href="http://square.github.io/okhttp/";>OkHttp</a> library for efficient HTTP connections.</li> +<li>Added support for PATCH methods that have a body.</li> +<li>Allow configuring of networks to which the nodes will be attached directly from the portable <a href="/start/compute">Compute</a> interface.</li> +</ul> -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds</groupId> - <artifactId>jclouds-all</artifactId> - <version>1.7.1</version> - </dependency> -</dependencies> -{% endhighlight %} -## Credits +<h2>Notes</h2> -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: +<ul> +<li>jclouds 1.7.1 is incompatible with <a href="https://code.google.com/p/guava-libraries/";>Guava</a> 16. Please switch to +Guava 15.0 or earlier, or wait for jclouds 1.8.</li> +</ul> - * Ignasi Barrera for managing the release. - * Andrew Phillips for his quick and diligent fixes for [JCLOUDS-427](https://issues.apache.org/jira/browse/JCLOUDS-427). - * Apache jclouds PMC for verifying. - * Check out who has been busy [here](http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit). -## Test Results +<h2>Reminder</h2> -Please see the [release discussion thread](http://markmail.org/message/dpfrnkcwvtf5scb7) for test results for 1.7.1. +<p>As per <a href="../1.6.1">1.6.1-incubating</a>, the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like:</p> +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>jclouds-all<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.7.1<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> + + +<h2>Credits</h2> + +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> + +<ul> +<li>Ignasi Barrera for managing the release.</li> +<li>Andrew Phillips for his quick and diligent fixes for <a href="https://issues.apache.org/jira/browse/JCLOUDS-427";>JCLOUDS-427</a>.</li> +<li>Apache jclouds PMC for verifying.</li> +<li>Check out who has been busy <a href="http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit";>here</a>.</li> +</ul> + + +<h2>Test Results</h2> + +<p>Please see the <a href="http://markmail.org/message/dpfrnkcwvtf5scb7";>release discussion thread</a> for test results for 1.7.1.</p> ]]></content> </entry> @@ -434,45 +527,50 @@ Please see the [release discussion threa <title type="html"><![CDATA[Release Notes for Version 1.7.0]]></title> <link href="http://jclouds.apache.org/releasenotes/1.7.0/"/> <updated>2013-12-23T00:00:00Z</updated> - <content type="html"><. You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324405&styleName=Html&projectId=12314430). +<p>To get jclouds, please see the <a href="/start/install/">jclouds installation guide</a>.</p> -To get jclouds, please see the [jclouds installation guide](/start/install/). +<h2>Notes</h2> -## Notes +<ul> +<li>jclouds 1.7.0 is incompatible with <a href="https://code.google.com/p/guava-libraries/";>Guava</a> 16. Please switch to +Guava 15.0 or earlier, or wait for jclouds 1.7.1</li> +</ul> -* jclouds 1.7.0 is incompatible with [Guava](https://code.google.com/p/guava-libraries/) 16. Please switch to -Guava 15.0 or earlier, or wait for jclouds 1.7.1 -## Reminder +<h2>Reminder</h2> -As per [1.6.1-incubating](../1.6.1), the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like: +<p>As per <a href="../1.6.1">1.6.1-incubating</a>, the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like:</p> -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds</groupId> - <artifactId>jclouds-all</artifactId> - <version>1.7.0</version> - </dependency> -</dependencies> -{% endhighlight %} +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>jclouds-all<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.7.0<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> -## Credits -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: +<h2>Credits</h2> - * Andrew Bayer for managing the release. - * Apache jclouds PMC for verifying. - * Check out who has been busy [here](http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit). +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> -## Test Results +<ul> +<li>Andrew Bayer for managing the release.</li> +<li>Apache jclouds PMC for verifying.</li> +<li>Check out who has been busy <a href="http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit";>here</a>.</li> +</ul> -Please see the [release discussion thread](http://markmail.org/thread/zwasetkfcbfgrhjz) for test results for 1.7.0. +<h2>Test Results</h2> + +<p>Please see the <a href="http://markmail.org/thread/zwasetkfcbfgrhjz";>release discussion thread</a> for test results for 1.7.0.</p> ]]></content> </entry> @@ -481,40 +579,42 @@ Please see the [release discussion threa <title type="html"><![CDATA[Release Notes for Version 1.6.3]]></title> <link href="http://jclouds.apache.org/releasenotes/1.6.3/"/> <updated>2013-11-30T00:00:00Z</updated> - <content type="html"><. You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324789&styleName=Html&projectId=12314430). +<p>To get jclouds, please see the <a href="/start/install">jclouds installation guide</a>.</p> -To get jclouds, please see the [jclouds installation guide](/start/install). +<h2>Reminder</h2> -## Reminder +<p>As per <a href="../1.6.1">1.6.1-incubating</a>, the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like:</p> -As per [1.6.1-incubating](../1.6.1), the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like: +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>jclouds-all<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.6.3<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds</groupId> - <artifactId>jclouds-all</artifactId> - <version>1.6.3</version> - </dependency> -</dependencies> -{% endhighlight %} -## Credits +<h2>Credits</h2> -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> - * Andrew Gaul for managing the release. - * Apache jclouds PMC for verifying. - * Check out who has been busy [here](http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit). +<ul> +<li>Andrew Gaul for managing the release.</li> +<li>Apache jclouds PMC for verifying.</li> +<li>Check out who has been busy <a href="http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit";>here</a>.</li> +</ul> -## Test Results -Please see the [release discussion thread](http://markmail.org/thread/gkqw7uidfnnze4lv) for test results for 1.6.3 +<h2>Test Results</h2> +<p>Please see the <a href="http://markmail.org/thread/gkqw7uidfnnze4lv";>release discussion thread</a> for test results for 1.6.3</p> ]]></content> </entry> @@ -523,40 +623,45 @@ Please see the [release discussion threa <title type="html"><![CDATA[Release Notes for Version 1.6.2]]></title> <link href="http://jclouds.apache.org/releasenotes/1.6.2/"/> <updated>2013-08-27T00:00:00Z</updated> - <content type="html"><. You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324574&styleName=Html&projectId=12314430). +<p>You can read the official announcement at <a href="http://markmail.org/message/ttznfvr3pqfs2cxm";>Apache jclouds 1.6.2-incubating released</a>. You can read the details of the specific JIRA issues addressed in this release at the <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324574&styleName=Html&projectId=12314430";>JIRA Release Notes</a>.</p> -To get jclouds, please see the [jclouds installation guide](/start/install). +<p>To get jclouds, please see the <a href="/start/install">jclouds installation guide</a>.</p> -## Reminder +<h2>Reminder</h2> - * As per [1.6.1-incubating](../1.6.1), the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like: +<ul> +<li>As per <a href="../1.6.1">1.6.1-incubating</a>, the jclouds Maven group ID has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like:</li> +</ul> -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds</groupId> - <artifactId>jclouds-all</artifactId> - <version>1.6.2-incubating</version> - </dependency> -</dependencies> -{% endhighlight %} -## Credits +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>jclouds-all<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.6.2-incubating<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: - * Andrew Bayer for assisting on the release charge. - * Our Apache mentors for verifying. - * Check out who has been busy [here](http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit). +<h2>Credits</h2> -## Test Results +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> -Please see the [test results](/releasenotes/1.6.2-tests) for test failures for 1.6.2. +<ul> +<li>Andrew Bayer for assisting on the release charge.</li> +<li>Our Apache mentors for verifying.</li> +<li>Check out who has been busy <a href="http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit";>here</a>.</li> +</ul> + +<h2>Test Results</h2> + +<p>Please see the <a href="/releasenotes/1.6.2-tests">test results</a> for test failures for 1.6.2.</p> ]]></content> </entry> @@ -565,59 +670,79 @@ Please see the [test results](/releaseno <title type="html"><![CDATA[Release Notes for Version 1.6.1]]></title> <link href="http://jclouds.apache.org/releasenotes/1.6.1/"/> <updated>2013-06-19T00:00:00Z</updated> - <content type="html"><![CDATA[## Introduction + <content type="html"><![CDATA[<h2>Introduction</h2> + +<p>jclouds Version 1.6.1 is geared around the transition into the Apache Incubator. It represents the first release of jclouds in the Apache Incubator. The most significant change is to the jclouds Maven groupId. You can read more about it in the Changes section below.</p> + +<p>You can read the official announcement at <a href="http://www.mail-archive.com/[email protected]/msg00112.html";>Apache jclouds 1.6.1-incubating released</a>. You can read the details of the specific JIRA issues addressed in this release at the <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314430&version=12324412";>JIRA Release Notes</a>.</p> + +<p>To get jclouds, please see the <a href="/start/install">jclouds installation guide</a>.</p> + +<h2>Additions</h2> + +<ul> +<li>Added the karaf/CLI command blobstore-blob-exists.</li> +</ul> + + +<h2>Removals</h2> -jclouds Version 1.6.1 is geared around the transition into the Apache Incubator. It represents the first release of jclouds in the Apache Incubator. The most significant change is to the jclouds Maven groupId. You can read more about it in the Changes section below. +<ul> +<li>Removed sandbox-apis and sandbox-providers.</li> +</ul> -You can read the official announcement at [Apache jclouds 1.6.1-incubating released](http://www.mail-archive.com/[email protected]/msg00112.html). You can read the details of the specific JIRA issues addressed in this release at the [JIRA Release Notes](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314430&version=12324412). -To get jclouds, please see the [jclouds installation guide](/start/install). +<h2>Changes</h2> +<ul> +<li>The jclouds Maven groupId has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like:</li> +</ul> -## Additions - * Added the karaf/CLI command blobstore-blob-exists. +<div class="highlight"><pre><code class="xml"><span class="nt"><dependencies></span> + <span class="nt"><dependency></span> + <span class="nt"><groupId></span>org.apache.jclouds<span class="nt"></groupId></span> + <span class="nt"><artifactId></span>jclouds-all<span class="nt"></artifactId></span> + <span class="nt"><version></span>1.6.1-incubating<span class="nt"></version></span> + <span class="nt"></dependency></span> +<span class="nt"></dependencies></span> +</code></pre></div> -## Removals - * Removed sandbox-apis and sandbox-providers. +<ul> +<li>Note that the package names in the source code have <em>not</em> changed.</li> +<li>jclouds-karaf has undergone a similar modification and you'll need to change the <code>featureRepositories</code> line in <code>etc/org.apache.karaf.features.cfg</code> to <code>featuresRepositories=mvn:org.apache.jclouds.karaf/jclouds-karaf/${jclouds.karaf.version}/xml/features</code> in the command line interface.</li> +<li>Updated license headers and project metadata to align with Apache Incubator.</li> +</ul> -## Changes - * The jclouds Maven groupId has changed from org.jclouds to org.apache.jclouds so a pom.xml dependency would now look like: +<h2>Fixes</h2> -{% highlight xml %} -<dependencies> - <dependency> - <groupId>org.apache.jclouds</groupId> - <artifactId>jclouds-all</artifactId> - <version>1.6.1-incubating</version> - </dependency> -</dependencies> -{% endhighlight %} +<ul> +<li>Allow repeatable Payload with InputSupplier input (allows retries to work)</li> +<li>Map S3 TooManyBuckets to InsufficientResourcesException</li> +<li>Fixed the jclouds-cli start script so that it now runs smoothly on Windows.</li> +</ul> - * Note that the package names in the source code have *not* changed. - * jclouds-karaf has undergone a similar modification and you'll need to change the `featureRepositories` line in `etc/org.apache.karaf.features.cfg` to `featuresRepositories=mvn:org.apache.jclouds.karaf/jclouds-karaf/${jclouds.karaf.version}/xml/features` in the command line interface. - * Updated license headers and project metadata to align with Apache Incubator. -## Fixes +<h2>Deprecated and Non-backwards Compatible Changes</h2> - * Allow repeatable Payload with InputSupplier input (allows retries to work) - * Map S3 TooManyBuckets to InsufficientResourcesException - * Fixed the jclouds-cli start script so that it now runs smoothly on Windows. +<ul> +<li>All Async interfaces are deprecated and will be removed in the next major version of jclouds. Please only use the synchronous APIs, those without "Async" in the class name, such as <code>NovaApi</code>. You can find an example of doing an asynchronous file upload without the Async interface in <a href="https://github.com/jclouds/jclouds-cloud-storage-workshop/blob/master/exercise2/src/main/java/org/jclouds/labs/blobstore/exercise2/MultiFileUploaderC.java";>MultiFileUploaderC.java</a>.</li> +<li>Accordingly, please discontinue use of <code>RestContext</code>. This is replaced with <code>ApiContext</code>, which doesn't have an Async type. Note that you can use <code>ContextBuilder.buildApi(YourApi.class)</code> instead of using contexts, as API interfaces are now closeable.</li> +<li>Please discontinue use of <code>Context.utils()</code> as many features there were only present to support the Async interfaces of jclouds. Code in jclouds will be easier to maintain when we needn't support utilities that are also present in tools such as Guava and Bouncycastle.</li> +</ul> -## Deprecated and Non-backwards Compatible Changes - * All Async interfaces are deprecated and will be removed in the next major version of jclouds. Please only use the synchronous APIs, those without "Async" in the class name, such as `NovaApi`. You can find an example of doing an asynchronous file upload without the Async interface in [MultiFileUploaderC.java](https://github.com/jclouds/jclouds-cloud-storage-workshop/blob/master/exercise2/src/main/java/org/jclouds/labs/blobstore/exercise2/MultiFileUploaderC.java). - * Accordingly, please discontinue use of `RestContext`. This is replaced with `ApiContext`, which doesn't have an Async type. Note that you can use `ContextBuilder.buildApi(YourApi.class)` instead of using contexts, as API interfaces are now closeable. - * Please discontinue use of `Context.utils()` as many features there were only present to support the Async interfaces of jclouds. Code in jclouds will be easier to maintain when we needn't support utilities that are also present in tools such as Guava and Bouncycastle. -## Credits +<h2>Credits</h2> -jclouds would like to thank everyone who contributed time and effort in order to make this release happen: +<p>jclouds would like to thank everyone who contributed time and effort in order to make this release happen:</p> - * Andrew Bayer for leading the release charge. - * A special thanks to our Apache mentors for guiding us through our first release. - * Check out who has been busy [here](http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit). +<ul> +<li>Andrew Bayer for leading the release charge.</li> +<li>A special thanks to our Apache mentors for guiding us through our first release.</li> +<li>Check out who has been busy <a href="http://www.ohloh.net/p/jclouds/contributors?query=&sort=latest_commit";>here</a>.</li> +</ul> ]]></content> </entry>
Modified: jclouds/site-content/start/concepts/index.html URL: http://svn.apache.org/viewvc/jclouds/site-content/start/concepts/index.html?rev=1691278&r1=1691277&r2=1691278&view=diff ============================================================================== --- jclouds/site-content/start/concepts/index.html (original) +++ jclouds/site-content/start/concepts/index.html Wed Jul 15 21:33:43 2015 @@ -160,20 +160,20 @@ <h2><a id="views"></a>Views</h2> -<p><a href="http://javadocs.jclouds.cloudbees.net/org/jclouds/View.html";><strong>Views</strong></a> are portable abstractions that are designed to allow you to write code that uses cloud services without tying yourself to a specific vendor. Take <a href="http://docs.oracle.com/javase/7/docs/technotes/guides/jdbc/index.html";>JDBC</a> as an example: rather than writing code directly for a specific type of database, you can make generic database requests, and the JDBC specification and drivers translate these into specific commands and statements for a certain type of database.</p> +<p><a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/View.html";><strong>Views</strong></a> are portable abstractions that are designed to allow you to write code that uses cloud services without tying yourself to a specific vendor. Take <a href="http://docs.oracle.com/javase/7/docs/technotes/guides/jdbc/index.html";>JDBC</a> as an example: rather than writing code directly for a specific type of database, you can make generic database requests, and the JDBC specification and drivers translate these into specific commands and statements for a certain type of database.</p> <p>Views generally make sense only once a reasonably broad set of functionality is supported by multiple vendors. In the cloud space, jclouds currently supports three such views:</p> <ul> <li><a href="/start/blobstore/">BlobStore</a></li> <li><a href="/start/compute/">ComputeService</a></li> -<li><a href="http://javadocs.jclouds.cloudbees.net/org/jclouds/loadbalancer/LoadBalancerService.html";>LoadBalancerService</a></li> +<li><a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/loadbalancer/LoadBalancerService.html";>LoadBalancerService</a></li> </ul> <h2><a id="apis"></a>APIs</h2> -<p>An <strong>API</strong> in jclouds describes the actual calls (often, but not always, HTTP requests) that can be executed against a specific cloud service to "do stuff". In the case of popular APIs, such as the <a href="http://javadocs.jclouds.cloudbees.net/org/jclouds/ec2/EC2Api.html";>EC2 compute API</a>, or the <a href="http://javadocs.jclouds.cloudbees.net/org/jclouds/s3/S3Client.html";>S3 storage API</a>, there may be multiple vendors with cloud services that support that particular API. For example, EC2 is supported by <a href="/guides/aws-ec2/">Amazon</a> and <a href="/guides/openstack/">OpenStack</a>, amongst others.</p> +<p>An <strong>API</strong> in jclouds describes the actual calls (often, but not always, HTTP requests) that can be executed against a specific cloud service to "do stuff". In the case of popular APIs, such as the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/ec2/EC2Api.html";>EC2 compute API</a>, or the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/s3/S3Client.html";>S3 storage API</a>, there may be multiple vendors with cloud services that support that particular API. For example, EC2 is supported by <a href="/guides/aws-ec2/">Amazon</a> and <a href="/guides/openstack/">OpenStack</a>, amongst others.</p> <p>A vendor may also support an API in multiple geographic locations. For example, <a href="/guides/rackspace/">Rackspace</a>'s Cloud Servers API is available both in the <a href="/reference/providers/#compute-providers">US</a> and the <a href="/reference/providers/#compute-providers">UK</a>.</p> @@ -213,7 +213,7 @@ <h4>You can use API-specific calls where needed</h4> -<p>If the particular views you are working with do not allow you to do exactly what you want, but the API supports the desired functionality, you can <a href="http://javadocs.jclouds.cloudbees.net/org/jclouds/View.html#unwrap()">"unwrap"</a> the view to access the underlying API. This reduces the portability of your code, but you can still move between providers that support this API.</p> +<p>If the particular views you are working with do not allow you to do exactly what you want, but the API supports the desired functionality, you can <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/View.html#unwrap()">"unwrap"</a> the view to access the underlying API. This reduces the portability of your code, but you can still move between providers that support this API.</p> <p>For example, if you unwrap the EC2 API from a ComputeService view and talk directly to EC2, you will not be able move to vCloud without code changes any more. You will still be able to switch to a different provider that also supports the EC2 API, however.</p> @@ -229,7 +229,7 @@ <p>A context represents a specific connection to a particular provider. >From the perspective of our database analogy, this would be broadly similar to a database connection against a specific DB.</p> -<p>Once you have created a context via the <a href="http://javadocs.jclouds.cloudbees.net/org/jclouds/ContextBuilder.html";>ContextBuilder</a> and are "connected" to a particular cloud service, you can either get any of the views that are supported by that provider, or go straight to the API or even to the provider level.</p> +<p>Once you have created a context via the <a href="http://jclouds-javadocs.elasticbeanstalk.com/org/jclouds/ContextBuilder.html";>ContextBuilder</a> and are "connected" to a particular cloud service, you can either get any of the views that are supported by that provider, or go straight to the API or even to the provider level.</p> <p>Creating a context is an expensive operation, so in general it is a good idea to create one context per credential and target cloud when the application starts and close it when it terminates. Contexts are thread-safe, so can be shared across your application.</p> @@ -237,8 +237,6 @@ <p>You can also get a view back from the ContextBuilder and <em>later</em> unwrap it to access the underlying API or provider.</p> -<p>The context also provides access to some low level resources, such as the dependency injection framework or the executors used to perform concurrent operations, so it is important to close it once you are done, to free all its associated resources.</p> - <div class="row clearfix"> <div id="footer" class="col-md-12 column"> <div id="footer">
