Hi Richard, rm -rvf ~/.m2
then mvn compile Same problem still. I was actually clearing the .m2 directory to verify that my cache wasn't causing me any problems on a build. Thanks, Kim Ebert 1.801.669.7342 Perfect Search Corp http://www.perfectsearchcorp.com/ On 11/12/2013 02:05 PM, Richard Eckart de Castilho wrote: > That's what I was expecting. I assume that you have the 3.9.0-xxx version in > your local .m2 repository, so the version range is resolved to that and > I don't see Maven actively accessing a strange repository in your logs, > so it might just be a remnant of some other project you built earlier. > > Try purging that version from your local .m2 repository (or maybe start with > a new > empty .m2 repository). > > -- Richard > > On 12.11.2013, at 21:46, Kim Ebert <kim.eb...@perfectsearchcorp.com> wrote: > >> It appears for some reason that my version is resolving to >> org.eclipse.core:runtime:jar:3.9.0-v20130326-1255:provided instead of >> org.eclipse.core:runtime:jar:3.3.100-v20070530 >> >> The eclipse dependency is listed as: >> >> <!-- Eclipse dependencies --> >> <dependency> >> <groupId>org.eclipse.core</groupId> >> <artifactId>runtime</artifactId> >> <version>[3.3.0.0,4.0.0)</version> >> <scope>provided</scope> >> </dependency> >
