| <html> |
| <!-- |
| |
| NO NO NO NO NO! |
| |
| ==============> DO NOT EDIT ME! <====================== |
| |
| AUTOMATICALLY GENERATED FROM APICHANGES.XML, DO NOT EDIT |
| |
| SEE parsing.api/apichanges.xml |
| |
| --> |
| |
| <head> |
| <META http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
| |
| <title>Change History for the Indexing API</title> |
| |
| <link rel="stylesheet" href="prose.css" type="text/css"> |
| |
| <meta name="CATEGORY" content="OtherDevelopmentDoc"> |
| |
| <meta name="DESCRIPTION" content="A cross-indexed list of all changes made to the Parsing & Indexing API."> |
| |
| </head> |
| |
| <body> |
| |
| <p class="overviewlink"> |
| |
| <a href="overview-summary.html" shape="rect">Overview</a> |
| |
| </p> |
| |
| <h1>Introduction</h1> |
| |
| <h2>What do the Dates Mean?</h2> |
| |
| <p> |
| The supplied dates indicate when the API change was made, on the CVS |
| trunk. From this you can generally tell whether the change should be |
| present in a given build or not; for trunk builds, simply whether it |
| was made before or after the change; for builds on a stabilization |
| branch, whether the branch was made before or after the given date. In |
| some cases corresponding API changes have been made both in the trunk |
| and in an in-progress stabilization branch, if they were needed for a |
| bug fix; this ought to be marked in this list. |
| </p> |
| |
| <hr> |
| |
| <h1> |
| <a name="list-all-apis">Index of APIs</a> |
| </h1> |
| <ul> |
| <li> |
| <a href="#IndexingAPI">Indexing API</a> |
| </li> |
| </ul> |
| <h1> |
| <a name="incompat-by-date">Incompatible changes by date</a> |
| </h1> |
| <p>Fuller descriptions of all changes can be found below (follow links).</p> |
| <p>Not all deprecations are listed here, assuming that the deprecated |
| APIs continue to essentially work. For a full deprecation list, please |
| consult the |
| <a href="deprecated-list.html">Javadoc</a>.</p> |
| <ul> |
| <li>(Apr 20 '14) <a href="#Separate.Parsing.Indexing">Indexing API separated to its own module</a> |
| </li> |
| </ul> |
| <h1> |
| <a name="all-by-date">All changes by date</a> |
| </h1> |
| <ul> |
| <li>(Apr 14 '15) <a href="#CustomCamelCase">Added custom camel case support into <code>QuerySupport</code></a> |
| </li> |
| <li>(Apr 20 '14) <a href="#Separate.Parsing.Indexing">Indexing API separated to its own module</a> |
| </li> |
| </ul> |
| <h1> |
| <a name="all-by-version">Changes by version</a> |
| </h1> |
| <p> |
| These API specification versions may be used to indicate that a module |
| requires a certain API feature in order to function. For example, if you |
| see here a feature you need which is labelled <samp>1.20</samp>, your |
| manifest should contain in its main attributes the line: |
| </p> |
| <pre>OpenIDE-Module-Module-Dependencies: $codebase > 1.20</pre> |
| <ul> |
| <li> |
| (9.5) <a href="#CustomCamelCase">Added custom camel case support into <code>QuerySupport</code></a> |
| </li> |
| <li> |
| (9.0) <a href="#Separate.Parsing.Indexing">Indexing API separated to its own module</a> |
| </li> |
| </ul> |
| <h1> |
| <a name="all-by-class">Changes by affected class</a> |
| </h1> |
| <h2> |
| <a name="org.netbeans.modules.parsing.spi.indexing.support.QuerySupport"><code><span style="color:gray">org.netbeans.modules.parsing.spi.indexing.support.</span>QuerySupport</code></a> |
| </h2><ul><li>(Apr 14 '15) <a href="#CustomCamelCase">Added custom camel case support into <code>QuerySupport</code></a> |
| </li></ul><hr> |
| <h1> |
| <a name="details-by-api">Details of all changes by API and date</a> |
| </h1> |
| <hr style="width:50%"> |
| <h2> |
| <a name="IndexingAPI">Indexing API</a> |
| </h2> |
| <!-- AUTOMATICALLY GENERATED - DO NOT EDIT ME! --> |
| <h3> |
| <a name="CustomCamelCase">Added custom camel case support into <code>QuerySupport</code></a> |
| </h3> |
| <em>Apr 14 '15; API spec. version: 9.5; affected top-level classes: <a href="./org/netbeans/modules/parsing/spi/indexing/support/QuerySupport.html"><code>QuerySupport</code></a>; made by: tzezula</em> |
| <br> |
| |
| <p> |
| Added a support for custom camel case separators and custom camel case parts into <code>QuerySupport</code> |
| |
| </p> |
| <!-- AUTOMATICALLY GENERATED - DO NOT EDIT ME! --> |
| <h3> |
| <a name="Separate.Parsing.Indexing">Indexing API separated to its own module</a> |
| </h3> |
| <em>Apr 20 '14; API spec. version: 9.0; made by: sdedic</em> |
| <br> |
| |
| <p> |
| Historically the module offered both APIs for Parsing (invoking parser, implementing parser) and |
| Indexing (refresh index, index SPIs). Those APIs are typically used by unrelated pieces of code, |
| possibly with the exception of "refresh" actions. |
| </p> |
| |
| <p> |
| The indexing now resides separately in its <code>parsing.indexing</code> module. Binary compatibility |
| is kept by using module-auto-deps.xml. |
| </p> |
| |
| <p> |
| Please also refer to the <a href="../org-netbeans-modules-parsing-api/apichanges.html" shape="rect">API Changes document</a> of the parental module. |
| </p> |
| |
| <br> |
| <em><a href="http://wiki.netbeans.org/VersioningPolicy#Compatible_change_on_the_trunk">Binary-compatible</a></em> |
| |
| <hr> |
| |
| <p><span class="footnote">Built on September 14 2018. | Copyright © 2017-2018 Apache Software Foundation. All Rights Reserved.</span></p> |
| |
| </body> |
| |
| </html> |
