This repository was archived by the owner on Mar 25, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Updated to jclouds 1.6.1 #142
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,60 @@ | ||
| --- | ||
| layout: jclouds | ||
| title: Release Notes for jclouds Version 1.6.1 | ||
| --- | ||
|
|
||
| Release Notes for jclouds Version 1.6.1 | ||
| ========================= | ||
|
|
||
| Release Date: June 19, 2013 | ||
|
|
||
| ## Introduction | ||
|
|
||
| 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. | ||
|
|
||
| You can read the official announcement at [Apache jclouds 1.6.1-incubating released](http://www.mail-archive.com/user@jclouds.incubator.apache.org/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](/documentation/userguide/installation-guide). | ||
|
|
||
|
|
||
| ## Additions | ||
|
|
||
| * Added the karaf/CLI command blobstore-blob-exists. | ||
|
|
||
| ## Removals | ||
|
|
||
| * Removed sandbox-apis and sandbox-providers. | ||
|
|
||
| ## Changes | ||
|
|
||
| * The jclouds Maven groupId has changed from org.jclouds to org.apache.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.6.1-incubating</version> | ||
| </dependency> | ||
| </dependencies> | ||
| {% endhighlight %} | ||
|
|
||
| * 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 | ||
|
|
||
| * 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. | ||
|
|
||
| ## 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 normal apis, such as `NovaApi`. | ||
| * 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 | ||
|
|
||
| jclouds would like to thank everyone who contributed time and effort in order to make the release of jclouds Version 1.6.1 happen. 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). | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 1.6.1 docs are currently being built, by the way...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we document how that's done and get that onto something under jclouds.incubator.apache.org? I'll open a JIRA. Ideally, I'd like anything that's part of a release to be done as part of the release process, by the release manager (or at least overseen by the release manager), so that things like updating the site, getting the javadocs up, etc, doesn't lag.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Absolutely! Let's get this hosted somewhere on Apache space as quickly as possible. There's nothing magical going on here - it's just generation of the Maven site, which includes the Javadocs. We should try to trim down the amount of what's generated to speed things up, then it's simply a matter of changing the POM to publish the site to wherever on Apache we should be hosting it.