- XMLize settimgs
- rewrite to ProjectSettings
- do backward compatibility issues
* All settings should be rewritten to new Settings Convertors API. It
also includes reading of old settings format and convertion to new format.
Petr Kuzel wrote "XML Module Integration with Projects Infrastructure"
and it is accessible at
XML modules provides 4 settings classes: CatalogSettings,
CoreSettings, TreeEditorSettings and NodeViewType. Only
CatalogSettings is *project* setting.
[CatalogSettings related issue #22848 - Module writers cannot add XML
catalog using layer.xml files.]
It also uses OpeIDE's and Editor module's settings, e.g. IndentEngine,
BaseOptions. XMLization should be inherited.
Some generators in xml-tools modulu pouzivaji org.netbeans.src (Java
Hierarchy). The XML-Tools module should be devided to two modules:
- generic XML Productivity Tools
- Java related Productivity Tools (xml-java)
The xml-java module will depend on java module: register xml-apis on
JDK1.3 (issue 27167), register xml-apis Javadoc, use new Java Model API.
It could be nice XML actions (Check and Validate) can be executed from
project/group level being performed over its content.
[Issue #21320 - Separate Java generators to standalone sub-module.]
As described in
current work on projects prototype has been stopped.
Well, work on Projects for NB3.6 has been stopped
but for upcomming NB4.0 it's been renovated, right?
thus, even though it's too late for promo-d (4.0), I'm reopening cause
work on Projects still continue and in promo-e PRojects should be mcuh
Nothing listed here makes sense any more. Issue #41447 is possibly
Probably useless issue now.
Verified invalid (not actual anymore)