jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven Integration for Eclipse
  • MNGECLIPSE-150

Repository Search results in error

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 0.0.10
  • Component/s: Dependency Resolver
  • Labels:
    None
  • Environment:
    eclipse 3.1.0 (windows)

Description

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 ???

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. MNGECLIPSE-138 "Unable to index" error

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Martin Dickey added a comment - 05/Jul/06 6:41 PM

This happens with Eclipse 3.2 also. Closing and then restarting Eclipse clears the problem.

Show
Martin Dickey added a comment - 05/Jul/06 6:41 PM This happens with Eclipse 3.2 also. Closing and then restarting Eclipse clears the problem.
Hide
Permalink
Chris Bredesen added a comment - 17/Oct/06 8:30 AM

To clarify the above, the dependency resolver works until exactly one dependency is added to the project, after which time the error described above appears. The only apparent workaround is to restart Eclipse (closing & reopening the project does not work). Once this is done, the resolver will work again, but only until a dependency is added. My copy of Eclipse is configured to use a proxy server.

Show
Chris Bredesen added a comment - 17/Oct/06 8:30 AM To clarify the above, the dependency resolver works until exactly one dependency is added to the project, after which time the error described above appears. The only apparent workaround is to restart Eclipse (closing & reopening the project does not work). Once this is done, the resolver will work again, but only until a dependency is added. My copy of Eclipse is configured to use a proxy server.
Hide
Permalink
abdurrrahman sahin added a comment - 04/Nov/06 6:21 AM

i think these are the same problem.

Show
abdurrrahman sahin added a comment - 04/Nov/06 6:21 AM i think these are the same problem.
Hide
Permalink
Brill Pappin added a comment - 09/Dec/06 7:53 PM

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).

Show
Brill Pappin added a comment - 09/Dec/06 7:53 PM 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).
Hide
Permalink
Brill Pappin added a comment - 09/Dec/06 9:47 PM

I think the dependency of this issue on MNGECLIPSE-138 is mistaken. The issue dependency link should checked with the person who created it.

Show
Brill Pappin added a comment - 09/Dec/06 9:47 PM I think the dependency of this issue on MNGECLIPSE-138 is mistaken. The issue dependency link should checked with the person who created it.
Hide
Permalink
Eugene Kuleshov added a comment - 06/Jan/07 2:50 PM

I think it should work ok in the trunk. Please reopen if you'll see this after 0.0.10 release.

Show
Eugene Kuleshov added a comment - 06/Jan/07 2:50 PM I think it should work ok in the trunk. Please reopen if you'll see this after 0.0.10 release.

People

  • Assignee:
    Eugene Kuleshov
    Reporter:
    Stefan
Vote (4)
Watch (4)

Dates

  • Created:
    04/Jul/06 10:33 AM
    Updated:
    06/Jan/07 2:50 PM
    Resolved:
    06/Jan/07 2:50 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.