I have seen this issue myself. I can't really say anything about what caused it to start happening, but I did manage to work around it by "closing" all projects in the workspace, then reopening just the ones I was working on i.e. the ones which *didn't* reference in any way the jar in the error message. Eventually I'm sure I reopened the offending project/s but by that time the issue had gone. BTW, this has happened to me 3 or 4 times.
cheers, Craig On Mon, Sep 8, 2008 at 8:58 PM, Todor Boev <[EMAIL PROTECTED]> wrote: > Eugene Kuleshov wrote: > >> Todor, >> >> What m2eclipse version you are using? >> Please run "Maven / Update project configuration" from popup menu and >> then "Update All Maven dependencies" action from the main Project menu. This >> will make sure your project is up to date and all dependencies are resolved >> without errors (check the Maven Console and Problems view to verify that). >> If that won't help, try to delete and recreate your launch configuration. >> >> If above won't resolve your issue, please open a JIRa issue and provide >> sample test projects that would allow us to reproduce this. See the >> following wiki page for some tips. >> http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues >> >> Thanks >> >> Eugene >> >> >> Todor Boev wrote: >> >>> For some reason when I try to start a maven build out of eclipse I always >>> get the following error: >>> >>> 'Launching Executing install in <the path to the pom>' has encountered a >>> problem. >>> >>> The archive: <some completely unrelated non-existing archive> which is >>> referenced by the classpath, does not exist. >>> >>> Can anyone tell me where can I find this classpath to correct it? The >>> missing archive is from a completely unrelated project I have in Eclipse and >>> is not mentioned in any of several pom files used in the maven supported >>> Eclipse project. Note that the maven build runs from the console - it fails >>> only in eclipse. >>> >>> Cheers, >>> Todor >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> >> >> I tried all that and it did not help. It seems that maven somehow > searches for any an all jars it finds scattered in the classpaths of the > other projects in working space. I deleted the project that contained the > offending jar and now maven blows up with an error of some other jar > missing. :( > > Also I noticed when Eclipse starts up maven prints on the console: > > Error on adding indexing context central; read past EOF > > I did have a mirror of repo1 I named "central" in my > <maven>/conf/settings.xml. I removed it from there to see if the error will > disappear. It did not. > > Cheers, > Todor > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
