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 199140 - Add the ability to create an XML Layer to the Module Development category for generating a Layer.xml file
Summary: Add the ability to create an XML Layer to the Module Development category for...
Status: RESOLVED DUPLICATE of bug 154752
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.0
Hardware: All All
: P4 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-03 12:06 UTC by bdschubert
Modified: 2011-06-03 14:53 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bdschubert 2011-06-03 12:06:58 UTC
With the advent of annotations, some of the wizards don't generate an editable layer.xml file for a module project (e.g., the New Action wizard).  Thus, if a module was created without a layer.xml file, there is no self-evident way of creating this file with the proper DTD and an entry in the manifest file. (I've discovered that the QuickSearch will do this, but I had to ask.)  Hand editing is an option, but I had to find an example in another module to use as a template -- and an example may not always be available.  

Thus, I request a new FIle Type be added to the Module Development category for generating an XML Layer file, for example:
New File.. > Module Development > XML Layer

This new File Type would generate the layer.xml file for the module with the proper XML DOCTYPE, plus it would ensure the proper OpenIDE-Module-Layer entry in the manifest.mf file.

Product Version = NetBeans IDE 7.0 (Build 201104080000)
Operating System = Windows Vista version 6.0 running on x86
Java; VM; Vendor = 1.6.0_24
Runtime = Java HotSpot(TM) Client VM 19.1-b02
Comment 1 Jesse Glick 2011-06-03 14:53:43 UTC

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