You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Adrian Cole (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/02/17 23:12:57 UTC

[jira] [Issue Comment Edited] (WHIRR-504) Upgrade to jclouds 1.4.0

    [ https://issues.apache.org/jira/browse/WHIRR-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210593#comment-13210593 ] 

Adrian Cole edited comment on WHIRR-504 at 2/17/12 10:11 PM:
-------------------------------------------------------------

I looked over whirr for deprecation issues, as it uses things in guava that have replacements.  Also, I had a look at DryRunModule, which is very sensitive to internal details of jclouds.  I'm in the process of revamping this patch to get rid of all deprecated guava usage.  I'm also updating jclouds to publish statement execution events on an EventBus, which is much cleaner than the aop pattern currently used in DryRunModule.
                
      was (Author: adrian@jclouds.org):
    I looked over whirr for deprecation issues, as it uses things in guava that have replacements.  Also, I had a look at DryRunModule, which is very sensitive to internal details of jclouds.  I'm in the process of revamping this patch to get rid of all deprecated guava usage.  I'm also updating jclouds to public statement execution events on an EventBus, which is much cleaner than the aop pattern currently used in DryRunModule.
                  
> Upgrade to jclouds 1.4.0
> ------------------------
>
>                 Key: WHIRR-504
>                 URL: https://issues.apache.org/jira/browse/WHIRR-504
>             Project: Whirr
>          Issue Type: Improvement
>            Reporter: Andrei Savu
>            Assignee: Adrian Cole
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-504.patch, WHIRR-504.patch
>
>
> At this time 1.4.0 RC1 is out and if no major bugs are discovered we should be able to have a final release pretty soon. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira