[
https://issues.apache.org/jira/browse/WHIRR-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471043#comment-13471043
]
Aled Sage commented on WHIRR-666:
---------------------------------
For producing a 0.8.1 with this, are there any whirr conventions for not
changing dependencies in minor releases? I'm guessing it would be fine: it's
(sort of) a minor jclouds release bump; and most people don't embed whirr in
their own apps (I presume?).
> Upgrade to jclouds 1.5.1
> ------------------------
>
> Key: WHIRR-666
> URL: https://issues.apache.org/jira/browse/WHIRR-666
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Aled Sage
> Fix For: 0.8.1
>
>
> Now that jclouds 1.5.1 final release is available, it would be great to have
> a new release of whirr that uses this.
> brooklyncentral.github.com in particular would love this, as we make use of
> whirr - 0.8.0's dependency on jclouds 1.5.0-beta.10 makes it hard for us to
> upgrade brooklyn to the most recent jclouds.
> (This is related to WHIRR-593, where whirr was upgraded to 1.5.0-beta.11; but
> it looks like whirr 0.8.0 was released with 1.5.0-beta.10).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
