> + */
> +package org.jclouds.profitbricks.compute.domain.internal;
> +
> +import static com.google.common.base.Preconditions.checkNotNull;
> +import static
> org.jclouds.profitbricks.compute.domain.internal.ProvisioningStatusAware.DATACENTER;
> +import static
> org.jclouds.profitbricks.compute.domain.internal.ProvisioningStatusAware.SERVER;
> +import static
> org.jclouds.profitbricks.compute.domain.internal.ProvisioningStatusAware.SNAPSHOT;
> +import static
> org.jclouds.profitbricks.compute.domain.internal.ProvisioningStatusAware.STORAGE;
> +import static org.jclouds.profitbricks.domain.ProvisioningState.AVAILABLE;
> +
> +import org.jclouds.profitbricks.ProfitBricksApi;
> +import org.jclouds.profitbricks.domain.ProvisioningState;
> +
> +import com.google.common.base.Predicate;
> +
> +public class ProvisioningStatusPollingPredicate implements Predicate<String>
> {
hmmm.. is having an aggregate, multi-purpose poller worth the head-scratching?
Id so, please add javadoc as to why a composite object like this is needed (not
saying it isn't, just it isn't obvious)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/72/files#r19648586
