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.
Otherwise it is harder to edit the XML files, and very hard to know what some of the special tags mean - e.g. what are permitted values of the 'category' attr of <property>?! You can easily "splice in" the XHTML DTD (libs/external/dtds/...); see apichanges.dtd for how to use entities which cover all block-level or all inline constructs.
Where such DTD should go? Is there any howto?
Date: 2003/02/04 13:19:57 Author: jtulach Log: Implemetation of #30558. Written Arch.dtd and changed generation of answers.xml to provide correct location to the DTD as well as api-questions.xml Members: antsrc/org/netbeans/nbbuild/Arch-api-questions.xml:1.5->1.6 antsrc/org/netbeans/nbbuild/Arch.dtd:INITIAL->1.1 antsrc/org/netbeans/nbbuild/Arch.java:1.7->1.8 Just regenerate your answer.xml to get correct header.
Thanks, looks good. I fixed up openide/arch/*.xml too.
<property> element inadequate. Seems to be overloaded for Java system properties as well as environment variables. This should be differentiated by a third attribute. Suggest: <!ATTLIST property name CDATA #REQUIRED category %category; #REQUIRED type (java | env) #REQUIRED >
Make that: type (java | env | win-registry) #REQUIRED
I suggest not to implement your last suggestions. The questions were ment for module developers and those cannot (under normal circumstances) access env and registry variables. That is why for them the type of property would have no meaning. The launcher is special and the module questions are not well suited for it. If you want to differentiate, I suggest just to write it into the documentation. If you disagree, I can put the attribute there with default value "System.getProperty", but as I wrote above, I do not consider that necessary.