<?xmlversion="1.0"encoding="UTF-8"?> <!-- Search for CHANGEME in this document when copying and using it: --> <!--
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
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="common_server_spi">Common Server SPI</apidef>
<apidef name="common_server_api">Common Server API</apidef>
<apidef name="common_server_properties_api">Common Server Properties API</apidef> <!-- etc. -->
</apidefs>
<!-- ACTUAL CHANGES BEGIN HERE: -->
<changes>
<change id="lookup">
<api name="common_server_api"/>
<summary>The ServerInstance implements Lookup.Provider</summary>
<version major="1" minor="19"/>
<date day="13" month="1" year="2012"/>
<author login="phejl"/>
<compatibility addition="yes"/>
<description>
The ServerInstance became Lookup.Provider.
</description>
<class package="org.netbeans.api.server" name="ServerInstance"/>
<issue number="206196"/>
</change>
<change id="CommonServerUIs-showAddServerInstanceWizard">
<api name="common_server_api"/>
<summary>Added UI helper method CommonServerUIs.showAddServerInstanceWizard</summary>
<version major="1" minor="18"/>
<date day="22" month="12" year="2011"/>
<author login="marfous"/>
<compatibility addition="yes"/>
<description>
Added helper method invoking wizard for adding new server instance.
</description>
<issue number="206479"/>
</change>
<change id="cloud">
<api name="common_server_api"/>
<summary>Establish layer to register cloud providers</summary>
<version major="1" minor="15"/>
<date day="24" month="8" year="2011"/>
<author login="dkonecny"/>
<compatibility addition="yes"/>
<description>
Reuse existing server support provided by this module and use
it to support concept of cloud providers. At the moment registration
of cloud providers is implemented (<code>/Cloud</code> folder in layer). Their
visualization will be added later. This is work in progress.
</description>
</change>
<change id="node.actions">
<api name="common_server_properties_api"/>
<summary>Extensible actions on root server node</summary>
<version major="1" minor="4"/>
<date day="3" month="4" year="2009"/>
<author login="jtulach"/>
<compatibility addition="yes"/>
<description>
By registering actions to <code>Servers/Actions</code> you
can extend the list of popup actions on Servers node in
Services tab.
</description>
</change>
<change>
<api name="common_server_properties_api"/>
<summary>Support API for server instance persistence</summary>
<version major="1" minor="1"/>
<date day="10" month="2" year="2008"/>
<author login="phejl"/>
<compatibility addition="yes"/>
<description>
Support API providing easy way for persistence of instance
properties. Not manadatory for clients to use.
</description>
</change>
<change>
<api name="common_server_spi"/>
<summary>Initial version released</summary>
<version major="1" minor="0"/>
<date day="12" month="1" year="2008"/>
<author login="phejl"/>
<compatibility addition="yes"/>
<description>
First initial release of the Common Server SPI.
</description>
</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 CHANGEME/apichanges.xml
-->
<head>
<title>Change History for the Common Server API/SPI</title>
<link rel="stylesheet"href="prose.css"type="text/css"/>
</head>
<body>
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung ist noch experimentell.
