[
https://issues.apache.org/jira/browse/WHIRR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085313#comment-13085313
]
Andrei Savu commented on WHIRR-361:
-----------------------------------
Hadoop works for me on cloudservers & ec2 with the current trunk. Actually
everything seems to be working fine and predictable on Rackspace. On EC2 I'm
seeing a lot of strange failures and I'm starting to think this is somehow
related to the automatically selected image. I'm planning to do more testing
against a vanilla Ubuntu 10.04 LTS server but first we should fix the pom files
so that we no longer get Guice exceptions in jclouds.
> refactor jclouds dependencies
> -----------------------------
>
> Key: WHIRR-361
> URL: https://issues.apache.org/jira/browse/WHIRR-361
> Project: Whirr
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.6.0
> Reporter: Adrian Cole
> Assignee: Adrian Cole
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: WHIRR-361.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> There are a few problems in our maven configuration, and a couple places
> where we aren't using the best jclouds configuration.
> * in our pom files, we needlessly declare transitive dependencies modules.
> this is unnecessary maintenance, as jclouds version/dependency configuration
> is scoped to whirr core
> * we've switched to SLF4J, yet haven't configured jclouds to use it
> * especially considering we are uploading large blobs, we should be using
> the jclouds EnterpriseConfigurationModule which handles file slicing much
> more effectively.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
