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 (JIRA)" <ji...@apache.org> on 2010/07/26 23:45:16 UTC

[jira] Created: (WHIRR-57) Dependencies seems to be aws-centric

Dependencies seems to be aws-centric
------------------------------------

                 Key: WHIRR-57
                 URL: https://issues.apache.org/jira/browse/WHIRR-57
             Project: Whirr
          Issue Type: Improvement
            Reporter: Adrian Cole


jclouds-aws shouldn't be a mandatory dependency.  In fact, it is probably better to add the known working jclouds provider artifacts as optional and only in the core module.  In the near future, jclouds will include an composite artifact called jclouds-allcompute (or something) which would have optional deps on all working compute providers.

http://code.google.com/p/jclouds/issues/detail?id=317

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WHIRR-57) Dependencies seems to be aws-centric

Posted by "Tom White (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896212#action_12896212 ] 

Tom White commented on WHIRR-57:
--------------------------------

+1 for depending on jclouds-allcompute (which I see is fixed now).

> Dependencies seems to be aws-centric
> ------------------------------------
>
>                 Key: WHIRR-57
>                 URL: https://issues.apache.org/jira/browse/WHIRR-57
>             Project: Whirr
>          Issue Type: Improvement
>            Reporter: Adrian Cole
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> jclouds-aws shouldn't be a mandatory dependency.  In fact, it is probably better to add the known working jclouds provider artifacts as optional and only in the core module.  In the near future, jclouds will include an composite artifact called jclouds-allcompute (or something) which would have optional deps on all working compute providers.
> http://code.google.com/p/jclouds/issues/detail?id=317

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WHIRR-57) Dependencies seems to be aws-centric

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WHIRR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White resolved WHIRR-57.
----------------------------

    Resolution: Fixed

WHIRR-52 changed the dependency to jclouds-allcompute.

> Dependencies seems to be aws-centric
> ------------------------------------
>
>                 Key: WHIRR-57
>                 URL: https://issues.apache.org/jira/browse/WHIRR-57
>             Project: Whirr
>          Issue Type: Improvement
>            Reporter: Adrian Cole
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> jclouds-aws shouldn't be a mandatory dependency.  In fact, it is probably better to add the known working jclouds provider artifacts as optional and only in the core module.  In the near future, jclouds will include an composite artifact called jclouds-allcompute (or something) which would have optional deps on all working compute providers.
> http://code.google.com/p/jclouds/issues/detail?id=317

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.