File: apichanges.xml

package info (click to toggle)
libnb-platform18-java 12.1-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 729,800 kB
  • sloc: java: 5,059,097; xml: 574,432; php: 78,788; javascript: 29,039; ansic: 10,278; sh: 6,386; cpp: 4,612; jsp: 3,643; sql: 1,097; makefile: 540; objc: 288; perl: 277; haskell: 93
file content (248 lines) | stat: -rw-r--r-- 10,735 bytes parent folder | download | duplicates (2)
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
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
<?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 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">Gradle Project API</apidef>
        <!-- etc. -->
    </apidefs>

    <!-- ACTUAL CHANGES BEGIN HERE: -->

    <changes>
        <change id="gradle-java-independence">
            <api name="general"/>
            <summary>Remove Java Platform dependency.</summary>
            <version major="2" minor="3"/>
            <date year="2020" month="7" day="15"/>
            <author login="lkishalmi"/>
            <compatibility binary="compatible" source="compatible"/>
            <description>
                <p>
                    Due to recent movement and the plan to support Gradle native
                    projects as well in the future the dependency on
                    Java Platform module has been removed.
                </p>
                <p>
                    The removal affects <code>org.netbeans.modules.gradle.api.execute.RunUtils</code>
                    <code>getActivePlatform</code> methods. The method returns a
                    Pair with <code>null</code> as <code>second</code> which
                    indicates a broken Platform. This is for keeping the binary compatibility only.
                    These methods shall be not used at all. There is no
                    replacement planned for these API functions.
                </p>
                <p>
                    Added <code>org.netbeans.modules.gradle.spi.exectute.GradleJavaPlatformProvider</code>
                    which can be put into the project lookup, to be able to specify the JDK
                    to be used for Gradle build execution.
                </p>
            </description>
        </change>
        <change id="gradle-project-trust">
            <api name="general"/>
            <summary>Introduce Trust relationship with Gradle Projects to prevent unintentional Gradle invocation.</summary>
            <version major="2" minor="2"/>
            <date year="2020" month="6" day="24"/>
            <author login="lkishalmi"/>
            <compatibility binary="compatible" source="compatible"/>
            <description>
                <p>
                    Gradle projects are maintaining a trust attribute from now.
                    This trust is based on the NetBeans user directory and the
                    a secret placed in the Gradle Root project directory.
                </p>
                <p>
                    Trusting any project of a multi-project Gradle build means
                    trust all project in that multi-project project, as the
                    trust is placed on the root project.
                </p>
                <p>
                    This change is backported to version 2.0.1 as well.
                </p>
                <p>
                    Added <code>RunUtils.isProjectTrusted(Project,boolean)</code>
                    where plugin can check if a project is trusted or request
                    one time trust with interactive mode.
                </p>
                <p>
                    There is no API/SPI to mark a project trusted/untrusted.
                    Projects are not trusted by default, but become trusted once
                    a priming build is requested or a Gradle task is invoked as
                    a result of an user action.
                </p>
                <p>
                    Added <code>org.netbeans.modules.gradle.spi.GradleSettings.GradleExecutionRule</code>
                    with setter ad getter in <code>org.netbeans.modules.gradle.spi.GradleSettings</code>
                    as a global option to how to treat automatic Gradle Execution globally.
                </p>
            </description>
        </change>
        <change id="gradle-tooling-api-split">
            <api name="general"/>
            <summary>Move Gradle Tooling API to a separate module.</summary>
            <version major="2" minor="0"/>
            <date year="2020" month="4" day="4"/>
            <author login="lkishalmi"/>
            <compatibility binary="incompatible" source="compatible"/>
            <description>
                <p>
                    The Gradle Tooling API has been removed from this module to
                    its own into: <code>org.netbeans.modules.libs.gradle</code>
                </p>
                <p>
                    Modules depending on previous versions of this module need
                    an additional dependency on the new library module. The
                    main reason behind this split is that it is easier to do
                    Gradle Tooling API update in the future.
                </p>
                <pre>
                    &lt;dependency&gt;
                        &lt;code-name-base&gt;org.netbeans.modules.libs.gradle&lt;/code-name-base&gt;
                        &lt;compile-dependency/&gt;
                        &lt;run-dependency&gt;
                            &lt;release-version&gt;6&lt;/release-version&gt;
                            &lt;specification-version&gt;6.3&lt;/specification-version&gt;
                        &lt;/run-dependency&gt;
                    &lt;/dependency&gt;
                </pre>
                <p>
                    <b>Note:</b> The specification version of the <code>org.netbeans.modules.libs.gradle</code>
                    module is matching the provided Gradle Tooling API version. The release version number
                    follows the major version.
                </p>
                <p>
                    Besides of the library removal the source code provided in
                    this module are backward compatible.
                </p>
            </description>
            <issue number="NETBEANS-4118"/>
        </change>
        <change id="allow-cancelling-gradle-process">
            <api name="general"/>
            <summary>Added <code>RunUtils.cancelGradle(RunConfig)</code> to allow plugins to cancel an executed Gradle process.</summary>
            <version major="1" minor="4"/>
            <date year="2019" month="10" day="22"/>
            <author login="lkishalmi"/>
            <compatibility source="compatible"/>
            <description>
                <p>
                    Added <code>RunUtils.cancelGradle(RunConfig)</code> to allow plugins to cancel an executed Gradle process.
                </p>
            </description>
            <class package="org.netbeans.modules.gradle.api.execute" name="RunUtils"/>
            <issue number="NETBEANS-3279"/>
        </change>
    </changes>

    <!-- Now the surrounding HTML text and document structure: -->

    <htmlcontents>
        <!--

                            NO NO NO NO NO!

         ==============>    DO NOT EDIT ME!  <==============

          AUTOMATICALLY GENERATED FROM APICHANGES.XML, DO NOT EDIT

                SEE projects/projectuiapi/apichanges.xml

        -->
        <head>
            <title>Change History for the Gradle Project API</title>
            <link rel="stylesheet" href="prose.css" type="text/css"/>
        </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="@org-netbeans-modules-gradle@/index.html">Gradle Project API</a>.</p>

            <!-- The actual lists of changes, as summaries and details: -->
            <hr/>
            <standard-changelists module-code-name="org.netbeans.modules.gradle/0"/>

            <hr/>
            <p>@FOOTER@</p>

        </body>
    </htmlcontents>

</apichanges>