That is because Eclipse does weird things with the classpath. Often is enough to "close" the jclouds-core project.
On 10 September 2014 17:25, Jai M <jaiganes...@gmail.com> wrote: > > >> When I import the whole branch as a project, Eclipse is not able to >> resolve the dependencies. Note that, I am able to execute the base pom.xml >> without issues. (It compiles and executes the tests). The problem was for >> running individual test methods when eclipse complains about the class not >> found . >> So I just imported the provider I want to test. since I noticed that the >> pom.xml under each provider is self sufficient. With one provider as a >> project and the build path having the maven dependencies, I am able to run >> individual unit test methods. >> >> Rgds >> Jai >> >> On Sat, Sep 6, 2014 at 2:11 AM, Ignasi Barrera <n...@apache.org> wrote: >>> >>> I also use m2e. You will just have to "Import an existing Maven project" >>> and everything should be ready. >>> El 06/09/2014 01:08, "Andrew Phillips" <aphill...@qrmedia.com> escribió: >>> >>> > I am having problems setting up jclouds as an eclipse project with >>> > maven. >>> >> >>> > >>> > Are you using m2e [1]? I always found that to be the easiest way to get >>> > things set up. >>> > >>> > If you are unable to use that, for some reason, could you share a >>> > screenshot of how your Workspace is set up and/or which errors you are >>> > seeing? >>> > >>> > Regards >>> > >>> > ap >>> > >>> > [1] https://www.eclipse.org/m2e/ >>> > >> >> >
