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: | Cannot initialize 0th child of node db.explorer.node.CatalogNode | ||
---|---|---|---|
Product: | db | Reporter: | Martin Fousek <marfous> |
Component: | Code | Assignee: | Jaroslav Havlin <jhavlin> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | cyhelsky, exceptions_reporter, fortruth, jmichelberger, jskrivanek, mmirilovic, mstarnacki, musilt2, pandajava, pjiricka, sj-nb |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 194817 |
Attachments: | stacktrace |
Description
Martin Fousek
2012-11-09 12:59:19 UTC
Created attachment 127463 [details]
stacktrace
*** Bug 221839 has been marked as a duplicate of this bug. *** *** Bug 221948 has been marked as a duplicate of this bug. *** http://hg.netbeans.org/core-main/rev/0c9de3ddbd5c Fixed. Thank you for reporting. Please verify. *** Bug 222036 has been marked as a duplicate of this bug. *** *** Bug 221977 has been marked as a duplicate of this bug. *** *** Bug 222034 has been marked as a duplicate of this bug. *** *** Bug 222049 has been marked as a duplicate of this bug. *** why it's not propaged yet even to main-silver? it almost block any activity with db, even in persistence wizards. (In reply to comment #9) > why it's not propaged yet even to main-silver? Job push-core-main is failing. It's already being solved. Integrated into 'main-golden', will be available in build *201211150001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/0c9de3ddbd5c User: Jaroslav Havlin <jhavlin@netbeans.org> Log: #221817: Cannot initialize 0th child of node db.explorer.node.CatalogNode *** Bug 222207 has been marked as a duplicate of this bug. *** *** Bug 221915 has been marked as a duplicate of this bug. *** *** Bug 222206 has been marked as a duplicate of this bug. *** *** Bug 222310 has been marked as a duplicate of this bug. *** *** Bug 223919 has been marked as a duplicate of this bug. *** *** Bug 225405 has been marked as a duplicate of this bug. *** |