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 206780 - IllegalArgumentException is thrown when creating a new File Type using the wizard
Summary: IllegalArgumentException is thrown when creating a new File Type using the wi...
Status: RESOLVED DUPLICATE of bug 204274
Alias: None
Product: apisupport
Classification: Unclassified
Component: Templates (show other bugs)
Version: 7.0.1
Hardware: PC Windows 7 x64
: P2 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-29 06:46 UTC by remould
Modified: 2011-12-29 17:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Error log (1.70 KB, text/plain)
2011-12-29 06:47 UTC, remould
Details

Note You need to log in before you can comment on or make changes to this bug.
Description remould 2011-12-29 06:46:26 UTC
Product Version = NetBeans IDE 7.0.1 (Build 201107282000)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0
Runtime = Java HotSpot(TM) 64-Bit Server VM 21.0-b17

When creating a new File Type using new file wizard in netbeans module projects, an IllegalArgumentException is thrown. All appropriate files get created/modified except the package-info.java file.

Steps
------
1. Create a new netbeans module project and create a new File Type (by file name extension) using the wizard.
2. When clicking 'Finish' button an IllegalArgumentException will be shown. See the attachment. By canceling the wizard, it can be seen that all appropriate files have been created/modified except the package-info.java file.
Comment 1 remould 2011-12-29 06:47:55 UTC
Created attachment 114515 [details]
Error log
Comment 2 Jesse Glick 2011-12-29 12:27:21 UTC

*** This bug has been marked as a duplicate of bug 204274 ***
Comment 3 remould 2011-12-29 15:31:17 UTC
I found this issue in the latest trunk revision. The ide I used to report this bug is 7.0.1 . That is why version 7.0.1 showed up in the bug description. Version 7.0.1 does not have this issue. Sorry for the confusion.
Comment 4 Jesse Glick 2011-12-29 17:10:05 UTC
I cannot reproduce in a dev build, and the stack trace you quote does not match dev sources. It matches old sources prior to enhanced diagnostics added for bug #204274. So it seems you are not running what you think you are running.