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.

Bug 226119 - NullPointerException: The brandingSource parameter cannot be null
Summary: NullPointerException: The brandingSource parameter cannot be null
Status: RESOLVED DUPLICATE of bug 227374
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Martin Kozeny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-14 13:23 UTC by scanti
Modified: 2013-03-19 08:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 185506


Attachments
stacktrace (3.64 KB, text/plain)
2013-02-14 13:23 UTC, scanti
Details

Note You need to log in before you can comment on or make changes to this bug.
Description scanti 2013-02-14 13:23:32 UTC
Build: NetBeans IDE 7.2.1 (Build 201210100934)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.6-b04, Java(TM) SE Runtime Environment, 1.7.0_10-b18
OS: Windows 7

User Comments:
GUEST: putting in a branding splash page.

scanti: Pressed OK in Branding window




Stacktrace: 
java.lang.NullPointerException: The brandingSource parameter cannot be null
   at org.openide.util.Parameters.notNull(Parameters.java:89)
   at org.netbeans.modules.apisupport.project.spi.BrandingSupport$BrandedFile.setBrandingSource(BrandingSupport.java:585)
   at org.netbeans.modules.apisupport.project.spi.BrandingModel.setIconSource(BrandingModel.java:239)
   at org.netbeans.modules.apisupport.project.suite.SuiteBrandingModel.setIconSource(SuiteBrandingModel.java:125)
   at org.netbeans.modules.apisupport.project.ui.branding.BasicBrandingPanel.store(BasicBrandingPanel.java:137)
   at org.netbeans.modules.apisupport.project.ui.branding.BrandingEditorPanel.doSave(BrandingEditorPanel.java:156)
Comment 1 scanti 2013-02-14 13:23:34 UTC
Created attachment 131385 [details]
stacktrace
Comment 2 Martin Kozeny 2013-03-19 08:08:00 UTC

*** This bug has been marked as a duplicate of bug 227374 ***