Please use the Apache issue tracking system for new NetBeans issues (https://issues.apache.org/jira/projects/NETBEANS0/issues) !!
Bug 267789 - ClassCastException: sun.awt.image.ToolkitImage cannot be cast to javax.swing.Icon
ClassCastException: sun.awt.image.ToolkitImage cannot be cast to javax.swing....
Status: NEW
Product: third-party
Classification: Unclassified
Component: -- Other --
8.2
All All
: P3 (vote)
: TBD
Assigned To: attila.kelemen
issues@third-party
EXCEPTIONS_REPORT
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-30 17:51 UTC by javydreamercsw
Modified: 2016-10-04 19:58 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
:


Attachments
stacktrace (1.67 KB, text/plain)
2016-08-30 17:51 UTC, javydreamercsw
Details
stacktrace (1.67 KB, text/plain)
2016-09-01 18:33 UTC, javydreamercsw
Details
stacktrace (1.67 KB, text/plain)
2016-09-26 17:13 UTC, javydreamercsw
Details
stacktrace (1.67 KB, text/plain)
2016-10-02 18:46 UTC, swpalmer
Details
stacktrace (1.67 KB, text/plain)
2016-10-03 08:49 UTC, J Bachorik
Details
stacktrace (1.67 KB, text/plain)
2016-10-04 17:22 UTC, mclaassen
Details
stacktrace (1.67 KB, text/plain)
2016-10-04 19:58 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description javydreamercsw 2016-08-30 17:51:49 UTC
Build: NetBeans IDE Dev (Build 201608230002)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.91-b14, Java(TM) SE Runtime Environment, 1.8.0_91-b14
OS: Linux

User Comments:
javydreamercsw: Tried to run a gradle project.




Stacktrace: 
java.lang.ClassCastException: sun.awt.image.ToolkitImage cannot be cast to javax.swing.Icon
   at org.netbeans.core.output2.ui.WeakAction.<init>(WeakAction.java:73)
   at org.netbeans.core.output2.ui.AbstractOutputTab.installKeyboardAction(AbstractOutputTab.java:194)
   at org.netbeans.core.output2.ui.AbstractOutputTab.setToolbarActions(AbstractOutputTab.java:169)
   at org.netbeans.core.output2.Controller.createOutputTab(Controller.java:118)
   at org.netbeans.core.output2.Controller.performCommand(Controller.java:329)
   at org.netbeans.core.output2.Controller.eventDispatched(Controller.java:108)
Comment 1 javydreamercsw 2016-08-30 17:51:50 UTC
Created attachment 161832 [details]
stacktrace
Comment 2 javydreamercsw 2016-09-01 18:33:34 UTC
Created attachment 161867 [details]
stacktrace

Right click on project node.
Comment 3 javydreamercsw 2016-09-26 17:13:07 UTC
Created attachment 162219 [details]
stacktrace

Executing a second project.
Comment 4 swpalmer 2016-10-02 18:46:12 UTC
Created attachment 162307 [details]
stacktrace

Happens when I try to run my project (using the Gradle plugin)
Comment 5 Jaroslav Havlin 2016-10-03 08:34:11 UTC
Seems related to Gradle plugin. Reassigning to owner of Gradle Support.
Attila, can you please evaluate this issue?
Thank you.
Comment 6 J Bachorik 2016-10-03 08:49:13 UTC
Created attachment 162314 [details]
stacktrace

Nothing. Working in IDE
Comment 7 Exceptions Reporter 2016-10-03 08:49:18 UTC
This bug already has 5 duplicates 
see http://statistics.netbeans.org/exceptions/detail.do?id=225990
Comment 8 attila.kelemen 2016-10-03 09:00:12 UTC
I cannot reproduce the issue in a clean install of NetBeans 8.2 RC (with the Gradle plugin). What should I do to reproduce the issue?
Comment 9 attila.kelemen 2016-10-03 09:41:27 UTC
Though I could not reproduce this issue, I made some changes which might affect this issue: https://github.com/kelemen/netbeans-gradle-project/commit/9b455e097b63848295a19863efa3384ebdc5e3a5
Comment 10 mclaassen 2016-10-04 17:22:14 UTC
Created attachment 162332 [details]
stacktrace

Trying 8.2 for first time.  Installed 8.1 update center plugin or gradle, not sure if that is related.
Comment 11 attila.kelemen 2016-10-04 18:13:27 UTC
I would like to ask someone to build the Gradle plugin from the sources and check if it solves their issue or not.

Though it seems reasonable that my changes might fix this issue, I have no means to verify it because I cannot reproduce the issue. Also, looking at NB's sources: The related classes were not changed since forever, so if the Gradle plugin is at fault, I don't see why the issue did not manifest in earlier version of NB.
Comment 12 Exceptions Reporter 2016-10-04 19:58:14 UTC
Created attachment 162336 [details]
stacktrace

just open my projets with dracula LAF


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo