-->
<?xml-stylesheettype="text/xml"href="../../nbbuild/javadoctools/apichanges.xsl"?>
<!DOCTYPE apichanges PUBLIC"-//NetBeans//DTD API changes list 1.0//EN""../../nbbuild/javadoctools/apichanges.dtd">
<changes>
<change id="arch.token">
<summary>
Provide tokens for the CPU architecture as <code>org.openide.modules.arch.${os_arch}</code>
</summary>
<version major="1" minor="84"/>
<date day="2" month="6" year="2023"/>
<author login="matthiasblaesing"/>
<compatibility addition="yes" binary="compatible" source="compatible"/>
<description>
<p>
There are libraries, that are only compatible with a single
architecture. Modules wrapping these must be able to signal
this and prevent loading. One such example is OpenJFX.
</p>
</description>
</change>
<change id="splash.screen.version.option">
<summary>
An optional version string can be added to the splash screen.
</summary>
<version major="1" minor="61"/>
<date day="11" month="5" year="2019"/>
<author login="ebakke"/>
<compatibility addition="yes" binary="compatible" source="compatible"/>
<description>
<p>
Branding bundles may now include the SplashVersionTextBounds,
SplashVersionTextFontSize, SplashVersionTextFontType,
SplashVersionTextColor, and SplashVersionTextHorizontalAlignment
properties in order to display the application's product version
and build number in the startup splash screen.
</p>
</description>
</change>
<change id="core.base.split">
<api name="bridge"/>
<summary>
Classes related to preferences and layered filesystems split into a
separate module.
</summary>
<version major="1" minor="60"/>
<date day="25" month="2" year="2015"/>
<author login="sdedic"/>
<compatibility addition="yes" binary="compatible" source="compatible"/>
<description>
<p>
Layered filesystem impl and preferences was split off to core.startup.base module.
A SPI was created in core.startup.base and implemented in core.startup for actual
FileSystem creation.
</p>
</description>
<class name="LayerFactory" package="org.netbeans.core.startup.base" link="no"/>
<p>
This document lists changes made to the API between core/startup and core
modules. It is a friend API so it does not need to be developed compatibly,
and indeed it is not.
</p>
<!-- The actual lists of changes, as summaries and details: -->
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 und die Messung sind noch experimentell.