-
Notifications
You must be signed in to change notification settings - Fork 921
Expand file tree
/
Copy pathapichanges.xml
More file actions
142 lines (113 loc) · 5.69 KB
/
apichanges.xml
File metadata and controls
142 lines (113 loc) · 5.69 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<?xml-stylesheet type="text/xml" href="../../nbbuild/javadoctools/apichanges.xsl"?>
<!DOCTYPE apichanges PUBLIC "-//NetBeans//DTD API changes list 1.0//EN" "../../nbbuild/javadoctools/apichanges.dtd">
<!--
INFO FOR PEOPLE ADDING
8000
CHANGES:
Check the DTD (apichanges.dtd) for details on the syntax. You do not
need to regenerate the HTML, as this is part of Javadoc generation; just
change the XML. Rough syntax of a change (several parts optional):
<change>
<api name="compiler"/>
<summary>Some brief description here, can use <b>XHTML</b></summary>
<version major="1" minor="99"/>
<date day="13" month="6" year="2001"/>
<author login="jrhacker"/>
<compatibility addition="yes"/>
<description>
The main description of the change here.
Again can use full <b>XHTML</b> as needed.
</description>
<class package="org.openide.compiler" name="DoWhatIWantCompiler"/>
<issue number="14309"/>
</change>
Also permitted elements: <package>, <branch>. <version> is API spec
version, recommended for all new changes. <compatibility> should say
if things were added/modified/deprecated/etc. and give all information
related to upgrading old code. List affected top-level classes and
link to issue numbers if applicable. See the DTD for more details.
Changes need not be in any particular order, they are sorted in various
ways by the stylesheet anyway.
Dates are assumed to mean "on the trunk". If you *also* make the same
change on a stabilization branch, use the <branch> tag to indicate this
and explain why the change was made on a branch in the <description>.
Please only change this file on the trunk! Rather: you can change it
on branches if you want, but these changes will be ignored; only the
trunk version of this file is important.
Deprecations do not count as incompatible, assuming that code using the
deprecated calls continues to see their documented behavior. But do
specify deprecation="yes" in <compatibility>.
This file is not a replacement for Javadoc: it is intended to list changes,
not describe the complete current behavior, for which ordinary documentation
is the proper place.
-->
<apichanges>
<!-- First, a list of API names you may use: -->
<apidefs>
<apidef name="general">General</apidef>
<!-- etc. -->
</apidefs>
<!-- ACTUAL CHANGES BEGIN HERE: -->
<changes>
<change id="JavaFoldManager.deprecated">
<summary>JavaFoldManager class deprecated</summary>
<version major="1" minor="1.49"/>
<date day="7" month="10" year="2020"/>
<author login="sdedic"/>
<compatibility binary="compatible" source="compatible" semantic="incompatible" deprecation="yes"/>
<description>
Java Editor dependencies on ext.* editor interfaces have been cut off, its Folding implementation does not derive
from the <a href="@TOP@/org/netbeans/editor/ext/java/JavaFoldManager.html">org.netbeans.editor.ext.java.JavaFoldManager</a> class. The <code>*_FOLD_TYPE</code> definitions
are still valid, although deprecated. Generic <a href="@org-netbeans-modules-editor-fold@/org/netbeans/api/editor/fold/FoldType.html">FoldType.*</a>
values should be used whenever possible.
</description>
</change>
<change id="old-editor-settings-deprecation">
<summary>Removing old settings classes</summary>
<version major="1" minor="9"/>
<date day="5" month="6" year="2008"/>
<author login="vstejskal"/>
<compatibility binary="compatible" source="incompatible" semantic="incompatible" addition="no" deprecation="no" deletion="yes"/>
<description>
The following classes were moved to <code>editor.deprecated.pre61settings</code> module:
<ul>
<li><code>org.netbeans.editor.ext.java.JavaSettingsDefaults</code></li>
<li><code>org.netbeans.editor.ext.java.JavaSettingsInitializer</code></li>
<li><code>org.netbeans.editor.ext.java.JavaSettingsNames</code></li>
</ul>
</description>
<issue number="90403"/>
</change>
</changes>
<!-- Now the surrounding HTML text and document structure: -->
<htmlcontents>
<!-- Generated from apichanges.xml -->
<head>
<title>Change History for the Java Editor Library API</title>
</head>
<body>
<p class="overviewlink"><a href="overview-summary.html">Overview</a></p>
<h1>Introduction</h1>
<p>This document lists changes made to the <a href="overview-summary.html">Java Editor Library API</a>.</p>
<!-- The actual lists of changes, as summaries and details: -->
<hr/>
<standard-changelists module-code-name="org.netbeans.modules.java.editor.lib/1"/>
<hr/><p>@FOOTER@</p>
</body>
</htmlcontents>
</apichanges>