[ http://jira.codehaus.org/browse/MNGECLIPSE-150?page=comments#action_82266 ] Brill Pappin commented on MNGECLIPSE-150: -----------------------------------------
The priority of this bug needs to be changed to Major as it makes it almost unusable on a windows machine. This has been happening with every version I've tried, including the latest. A quick check shows that a java process has the index file(s) locked. It's not always the same index file (segment is mentioned above). The index files look like Lucen(sp) files and this could possible be a bug in the that library. If that is the case, then the bug in the dependency needs to be resolved of a new method of indexing implemented. This is getting very annoying. I can "unlock" the index files with a 3rd party tool (in windows) but its a real pain. I expect this does not show up on *nix machines because of the way files are handled (no locking). > Repository Search results in error > ---------------------------------- > > Key: MNGECLIPSE-150 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-150 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug > Components: Dependency Resolver > Environment: eclipse 3.1.0 (windows) > Reporter: Stefan > Priority: Minor > > When adding a dependency, the repository search now always results in an > error (used to work before). > As soon as a letter is typed in the query box then a "Search error" appears: > C:\MyProject\workspace\.metadata\.plugins\org.maven.ide.eclipse\index\local\segments > (The system cannot find the file spedified) > I have no clue what caused the file to disappear, however since I never > created it before it should try to create one again based on the repository > ??? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
