Could you please confirm if the version number below is the latest? Jothis-MacBook-Pro:camel jothi$ svn update At revision 1351131.
But the issue is yet not resolved. Should I add any other remote repositories in my settings.xml? I just have a local repository defined in my settings.xml as below: <localRepository>.. /jothi/Softwares/maven-repo</localRepository> Regards, Jothi On Sun, Jun 17, 2012 at 7:15 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > There could be a few explanations, although it's a bit weird. Try this: > > 1. Make sure you have a recent copy of the sources. I assume you got your > copy from the repo, so you may need to update it (either `svn up` if you > used subversion or `git pull` if you used the github repo). That should > just use the local copies and not try to fetch snapshots from the apache > snapshots repo. > > 2. If you still have the problem, follow the instructions and run `mvn -X > install -Dfastinstall` (it skips tests, so it's much faster) and send us a > copy of the output. You may have some conflicting settings in > ~/.m2/settings.xml. You may consider attaching that too. > > In most cases just 1. should fix your problem. > Hadrian > > > > > On 06/17/2012 11:41 AM, Jothi Sankarraj wrote: > >> Camel Riders, >> >> I'm just getting started with building Camel locally on my machine. When I >> hit the error below, I updated my sources and tried to build again. But >> the >> error seems to still be there. Is there anything that could be done? >> >> [ERROR] Failed to execute goal on project camel-spring: Could not resolve >> dependencies for project >> org.apache.camel:camel-spring:**bundle:2.10-SNAPSHOT: Failure to find >> org.apache.camel:camel-core:**jar:tests:2.10-SNAPSHOT in >> http://repository.apache.org/**snapshots/<http://repository.apache.org/snapshots/>was >> cached in the local repository, >> resolution will not be reattempted until the update interval of >> apache.snapshots has elapsed or updates are forced -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e >> switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> >> Regards, >> Jothi >> >>
