| Summary: | Deadlock, with repository indexing in the background, editing a pom plugin version | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Andy Brook <javahollic> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | CLOSED INVALID | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | igor | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Andy Brook
p.s. m2e integration version is 1.0.0.20110607 Created attachment 204477 [details]
Thread dump of eclipse after the deadlock
Technically, this is not a deadlock, the GUI will eventually show the proposals. Still, I agree that observed behaviour is wrong, GUI should not wait for index download to complete but provide some feedback that the index is not available yet. closing old/stale bugreports |