The default answer to this question is:
These modules are required in project.xml:
java.io.Filedirectly? Answer: No. Question (resources-layer): Does your module provide own layer? Does it create any files or folders in it? What it is trying to communicate by that and with which components? Answer: No. Question (resources-read): Does your module read any resources from layers? For what purpose? Answer: No. Question (resources-mask): Does your module mask/hide/override any resources provided by other modules in their layers? Answer: No. Question (resources-preferences): Does your module uses preferences via Preferences API? Does your module use NbPreferences or or regular JDK Preferences ? Does it read, write or both ? Does it share preferences with other modules ? If so, then why ? WARNING: Question with id="resources-preferences" has not been answered!
org.openide.util.Lookupor any similar technology to find any components to communicate with? Which ones? Answer: No. Question (lookup-register): Do you register anything into lookup for other code to find? Answer: No. Question (lookup-remove): Do you remove entries of other modules from lookup? Answer: No.
System.getProperty) property? On a similar note, is there something interesting that you pass to
java.util.logging.Logger? Or do you observe what others log? Answer: LookAndFeelClassName - The module initializes proper Look&Feel. The decision is done based on various inputs including what has been specified on command line. To allow easier branding for those who build applications on top of NetBeans, there is key
org.netbeans.swing.plaf.Bundlebundle which can be branded to actual name of the L&F class. The module will decide which sets of customizations to load based on the chosen look and feel. LookAndFeelCustomsClassName - The module adds some UIManager keys and values to provide e.g. special border for main window toolbar or UI classes for tab control headers. By default the proper subclass of LFCustoms is derived from current Look and Feel name. Applications building on top of NetBeans can provide their own look and feel customizations by branding
org.netbeans.swing.plaf.Bundlebundle. Question (exec-component): Is execution of your code influenced by any (string) property of any of your components? Answer: For testing purposes only, the system property "nb.forceui" can be used to load NetBeans customizations for a different look and feel (such as loading the custom Aqua UI delegates on Windows). The only purpose for this flag is to enable development/bug fixing and minimal testing when a developer is working on a machine that does not support the requested look and feel, and they want to be sure they have not broken anything. Question (exec-ant-tasks): Do you define or register any ant tasks that other can use? WARNING: Question with id="exec-ant-tasks" has not been answered! Question (exec-classloader): Does your code create its own class loader(s)? Answer: No. Question (exec-reflection): Does your code use Java Reflection to execute other code? Answer: If org.openide.util.Utilities is not resolvable, it will use ImageIO.read() to load images. Question (exec-privateaccess): Are you aware of any other parts of the system calling some of your methods by reflection? Answer: Swing will resolve and load UI classes which are added to UIDefaults, which are defined in this library, when a component needs a UI delegate. Question (exec-process): Do you execute an external process from your module? How do you ensure that the result is the same on different platforms? Do you parse output? Do you depend on result code? Answer: No. Question (exec-introspection): Does your module use any kind of runtime type information (
instanceof, work with
java.lang.Class, etc.)? Answer: No. Question (exec-threading): What threading models, if any, does your module adhere to? How the project behaves with respect to threading? Answer: First come first served - the single API method is meant to be called once (this is enforced) by an application on startup. It does not matter on which thread; what is important is that the application do so before constructing its main GUI. Question (security-policy): Does your functionality require modifications to the standard policy file? Answer: No. Question (security-grant): Does your code grant additional rights to some other code? Answer: No.
java.awt.datatransfer.Transferable? Answer: N/A