This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | org.openide.util.lookup.ALPairComparator$DuplicatedPairException: Duplicate pair in treePair1: org.netbeans.modules.versioning.FileBasedVCSProvider pair2: org.netbeans.modules.projectapi.ProjectFileBu | ||
---|---|---|---|
Product: | platform | Reporter: | Exceptions Reporter <exceptions_reporter> |
Component: | Lookup | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | ovrabec, txomon |
Priority: | P4 | ||
Version: | 7.4 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 208124 |
Attachments: | stacktrace |
Description
Exceptions Reporter
2014-03-04 04:03:55 UTC
Created attachment 145730 [details]
stacktrace
Some issue with FileBasedVCSProvider? exception reporter lists too many duplicates mentioning *not* only FileBasedVCSProvider. I expect it to be a general problem with lookup. So the problem appears only with FileBasedVCSProvider and you conclude it is a general problem in Lookup. What a weird logic! (In reply to Jaroslav Tulach from comment #4) > So the problem appears only with FileBasedVCSProvider and you conclude it is > a general problem in Lookup. What a weird logic! Does it happen only with FileBasedVCSProvider? I don't think so, have you looked at the reports at all? I can list: FileBasedVCSProvider, DefaultModelProvider, NbLifecycleManager, NexusRepositoryIndexerImpl, NbURLDisplayer, ProjectLocaleQueryImplementation, DefaultOutputProcessorFactory, EnabledModulesCollector, and many other... Does my weird logic make sense now? I see. Missed "not", probably because it was inside of some weird characters - e.g. *not* The problem is that all the reports are too old and we can ignore them. Except http://statistics.netbeans.org/exceptions/exception.do?id=715306 which is from NetBeans 7.4. Previous reports of this kind included some sooner failure before the actual failure in Lookup. The report 715306 is an exception, there is no known failure before. Anyway it is just a single report of its kind, so let's adjust priority to P4. No report from 8.0 - something must have been fixed. |