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: | NullPointerException at java.awt.Container.addNotify (MavenProblemNode cting ProblemsPanel off EQ) | ||
|---|---|---|---|
| Product: | platform | Reporter: | gaxzero <gaxzero> |
| Component: | JDK Problems | Assignee: | Antonin Nebuzelsky <anebuzelsky> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | aldobrucale, davotoula, dheffelfinger, jglick, lazarius, nickbence, onmomo, pavanvusirika, rptmaestro, simpatico, weolopez |
| Priority: | P3 | Keywords: | THREAD |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://statistics.netbeans.org/exceptions/detail.do?id=152426 | ||
| Issue Type: | DEFECT | Exception Reporter: | 152426 |
| Attachments: |
stacktrace
stacktrace stacktrace stacktrace stacktrace |
||
Created attachment 90463 [details]
stacktrace
This issue already has 7 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=152426 reassigning to winsys for evaluation. Did you see anything similar? a jdk issue maybe? the affected code at org.netbeans.modules.maven.nodes.MavenProjectNode.java:280 looks like pretty much standard code. Any advice welcome. *** Issue 174146 has been marked as a duplicate of this issue. *** Maybe it could be caused by constructing ProblemsPanel out of AWT queue in MavenProblemNode? Created attachment 97754 [details]
stacktrace
Reassigning to default owner. ProblemsPanel is constructed on EQ by ShowProblemsAction.actionPerformed, so I don't see anything wrong in maven/src code. Seems Component.peer == null. While this may ultimately be a bug in NB, AWT is doing a very poor job of reporting the source of the bug. Created attachment 105430 [details]
stacktrace
Show and resolve problems on javase maven project
Created attachment 106122 [details]
stacktrace
Opening properties for a maven EJB project
Created attachment 106996 [details]
stacktrace
"Show Problems" on a Maven project.
The offending lines of code throwing the NPE have been removed in JDK 1.7
ContainerPeer cpeer = (ContainerPeer)peer;
if (cpeer.isRestackSupported()) {
cpeer.restack();
}
|
Build: NetBeans IDE 6.7.1 (Build 200907230233) VM: Java HotSpot(TM) Client VM, 1.5.0_20-141, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_20-b02-315 OS: Mac OS X, 10.5.8, i386 User Comments: GUEST: Using a maven2 project... 1) Did a subversion update via Netbeans (was successful) Whilst it was running, I noticed that Netbeans was complaining about one of my pom.xml files (<Badly formed Maven project>) 2) Executed a build (mvn install) from the command line, to update any missing local artefacts. Netbeans was still complaining about the same pom.xml file (<Badly formed Maven project>) 3) Selected "the view/resolve problem"(?) option - why is the Report Problem dialog modal? Anyways... After selecting that option, I got no dialog to assist with finding out what the real issue is/was but saw the NullPointerException occur around the same time as I would have expected the dialog box to have appeared. cadorca: Using the resolve problem dialog to download some libraries in a maven project GUEST: Clicked on review and resolve issues for a maven project Stacktrace: java.lang.NullPointerException at java.awt.Container.addNotify(Container.java:2544) at javax.swing.JComponent.addNotify(JComponent.java:4478) at java.awt.Container.addNotify(Container.java:2544) at javax.swing.JComponent.addNotify(JComponent.java:4478) at java.awt.Container.addNotify(Container.java:2544) at javax.swing.JComponent.addNotify(JComponent.java:4478)