Added content and reworked the formatting.
diff --git a/noteworthy/cdt.adoc b/noteworthy/cdt.adoc
index 6aeb3dd..7be7872 100644
--- a/noteworthy/cdt.adoc
+++ b/noteworthy/cdt.adoc
@@ -12,21 +12,20 @@
:cdtPackageUrl: https://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/marsr
[[cdt]]
-C/C++
-~~~~~
+== C/C++
pass:[C/C++] support is provided by the {cdtPackageUrl}[Eclipse IDE for pass:[C/C++] Developers].
-Import Projects
-^^^^^^^^^^^^^^^
+=== General
+
+==== Import Projects
When code completion is invoked in a function call expression, appropriate
substitutions are suggested for each of the function parameters.
image::images/Function_call.png[]
-Create New Class - Quick Fix
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+==== Create New Class - Quick Fix
In C++ files if "Type not found" error is detected, there is a new *Quick Fix*
now to create a class based on that type, which opens the *New C++ Class Wizard*.
diff --git a/noteworthy/images/add-meta-annotations.png b/noteworthy/images/add-meta-annotations.png
new file mode 100644
index 0000000..45f543f
--- /dev/null
+++ b/noteworthy/images/add-meta-annotations.png
Binary files differ
diff --git a/noteworthy/images/add-nonnull1.png b/noteworthy/images/add-nonnull1.png
new file mode 100644
index 0000000..1cb3d7c
--- /dev/null
+++ b/noteworthy/images/add-nonnull1.png
Binary files differ
diff --git a/noteworthy/images/annotation-selection.png b/noteworthy/images/annotation-selection.png
new file mode 100644
index 0000000..ca247aa
--- /dev/null
+++ b/noteworthy/images/annotation-selection.png
Binary files differ
diff --git a/noteworthy/images/assign-all-params-to-new-fields.png b/noteworthy/images/assign-all-params-to-new-fields.png
new file mode 100644
index 0000000..dde9f9e
--- /dev/null
+++ b/noteworthy/images/assign-all-params-to-new-fields.png
Binary files differ
diff --git a/noteworthy/images/configure-pessimistic-analysis.png b/noteworthy/images/configure-pessimistic-analysis.png
new file mode 100644
index 0000000..d8694fe
--- /dev/null
+++ b/noteworthy/images/configure-pessimistic-analysis.png
Binary files differ
diff --git a/noteworthy/images/configure-problem-severity.png b/noteworthy/images/configure-problem-severity.png
new file mode 100644
index 0000000..e5a282e
--- /dev/null
+++ b/noteworthy/images/configure-problem-severity.png
Binary files differ
diff --git a/noteworthy/images/eclipse-welcome-launchbar.png b/noteworthy/images/eclipse-welcome-launchbar.png
new file mode 100644
index 0000000..2a1a16b
--- /dev/null
+++ b/noteworthy/images/eclipse-welcome-launchbar.png
Binary files differ
diff --git a/noteworthy/images/eclipse-welcome-solstice.png b/noteworthy/images/eclipse-welcome-solstice.png
new file mode 100644
index 0000000..bafb606
--- /dev/null
+++ b/noteworthy/images/eclipse-welcome-solstice.png
Binary files differ
diff --git a/noteworthy/images/formatter-align-groups.png b/noteworthy/images/formatter-align-groups.png
new file mode 100644
index 0000000..b258600
--- /dev/null
+++ b/noteworthy/images/formatter-align-groups.png
Binary files differ
diff --git a/noteworthy/images/formatter-enum-constants.png b/noteworthy/images/formatter-enum-constants.png
new file mode 100644
index 0000000..97c57ea
--- /dev/null
+++ b/noteworthy/images/formatter-enum-constants.png
Binary files differ
diff --git a/noteworthy/images/formatter-parentheses.png b/noteworthy/images/formatter-parentheses.png
new file mode 100644
index 0000000..82c5bf9
--- /dev/null
+++ b/noteworthy/images/formatter-parentheses.png
Binary files differ
diff --git a/noteworthy/images/formatter-wrap-for.png b/noteworthy/images/formatter-wrap-for.png
new file mode 100644
index 0000000..7af33b5
--- /dev/null
+++ b/noteworthy/images/formatter-wrap-for.png
Binary files differ
diff --git a/noteworthy/images/hide-empty-library-containers-project-explorer.png b/noteworthy/images/hide-empty-library-containers-project-explorer.png
new file mode 100644
index 0000000..8b81949
--- /dev/null
+++ b/noteworthy/images/hide-empty-library-containers-project-explorer.png
Binary files differ
diff --git a/noteworthy/images/if-null-template.png b/noteworthy/images/if-null-template.png
new file mode 100644
index 0000000..2443e0d
--- /dev/null
+++ b/noteworthy/images/if-null-template.png
Binary files differ
diff --git a/noteworthy/images/info-problem-decorator.png b/noteworthy/images/info-problem-decorator.png
new file mode 100644
index 0000000..566e967
--- /dev/null
+++ b/noteworthy/images/info-problem-decorator.png
Binary files differ
diff --git a/noteworthy/images/info-severity.png b/noteworthy/images/info-severity.png
new file mode 100644
index 0000000..2591541
--- /dev/null
+++ b/noteworthy/images/info-severity.png
Binary files differ
diff --git a/noteworthy/images/pessimistic-analysis.png b/noteworthy/images/pessimistic-analysis.png
new file mode 100644
index 0000000..b8ad3b6
--- /dev/null
+++ b/noteworthy/images/pessimistic-analysis.png
Binary files differ
diff --git a/noteworthy/images/prefs-errors-warnings.png b/noteworthy/images/prefs-errors-warnings.png
new file mode 100644
index 0000000..8d69ae8
--- /dev/null
+++ b/noteworthy/images/prefs-errors-warnings.png
Binary files differ
diff --git a/noteworthy/images/remove-redundant-type-arguments.png b/noteworthy/images/remove-redundant-type-arguments.png
new file mode 100644
index 0000000..19f9593
--- /dev/null
+++ b/noteworthy/images/remove-redundant-type-arguments.png
Binary files differ
diff --git a/noteworthy/images/search-on-multi-selections.png b/noteworthy/images/search-on-multi-selections.png
new file mode 100644
index 0000000..c8cd20d
--- /dev/null
+++ b/noteworthy/images/search-on-multi-selections.png
Binary files differ
diff --git a/noteworthy/images/show-referenced-libraries-node-project-explorer.png b/noteworthy/images/show-referenced-libraries-node-project-explorer.png
new file mode 100644
index 0000000..4bcfe0f
--- /dev/null
+++ b/noteworthy/images/show-referenced-libraries-node-project-explorer.png
Binary files differ
diff --git a/noteworthy/images/substring-code-completion.png b/noteworthy/images/substring-code-completion.png
new file mode 100644
index 0000000..90853dc
--- /dev/null
+++ b/noteworthy/images/substring-code-completion.png
Binary files differ
diff --git a/noteworthy/images/unsafe-nonnull-interpretation.png b/noteworthy/images/unsafe-nonnull-interpretation.png
new file mode 100644
index 0000000..00f1b21
--- /dev/null
+++ b/noteworthy/images/unsafe-nonnull-interpretation.png
Binary files differ
diff --git a/noteworthy/jdt.adoc b/noteworthy/jdt.adoc
index 7ee591b..e49ef14 100644
--- a/noteworthy/jdt.adoc
+++ b/noteworthy/jdt.adoc
@@ -10,10 +10,249 @@
//////////////////////////////////////////
[[java]]
-Java(TM)
-~~~~~~~~
+== Java(TM)
Eclipse Neon includes numerous bug fixes and improvements in the Java 8
support, along with a lot of other useful features.
+=== Java Editor
+==== ifNotNull/ifNull templates
+
+The Java editor now offers default templates for creating "== null" and "!= null" checks.
+
+image::images/if-null-template.png[]
+
+==== New Info severity level
+
+You can now specify _Info_ as a severity level for the problems detected by the Eclipse
+Java compiler.
+
+image::images/info-severity.png[]
+
+A new decorator has been added to indicate information severity problems detected by the
+Eclipse Java Compiler.
+
+image::images/info-problem-decorator.png[]
+
+You can now configure the severity of a compiler problem by invoking the new _Quick Fix_
+(`Ctrl+1`) which opens the `Java > Compiler > Errors/Warnings` preference page and
+highlights the configurable problem.
+
+image::images/configure-problem-severity.png[]
+
+==== Substring code completion
+
+Content Assist now supports substring patterns. Enter any part of the desired proposal's
+text, and Content Assist will find it! For example, completing on `selection` proposes
+all results containing `selection` as a substring.
+
+image::images/substring-code-completion.png[]
+
+This feature can be disabled using the `Show substring matches` option on the
+`Java > Editor > Content Assist` preference page.
+
+==== Clean Up to remove redundant type arguments
+
+A new option to remove redundant type arguments has been added under the
+_Unnecessary Code_ group of the Clean Up profile.
+
+image::images/remove-redundant-type-arguments.png[]
+
+==== New options in code formatter
+
+In the new _Parentheses_ tab, you can order the formatter to keep
+parentheses of various Java elements on separate lines, i.e. put a
+line break after the opening parenthesis and before the closing
+parenthesis. This can be done always, only when parentheses are
+not empty, or when their content is wrapped. There's also an option
+to preserve existing positions, if you want to manually manage parentheses
+positions on a case-by-case basis.
+
+image::images/formatter-parentheses.png[]
+
+In the _Line Wrapping_ tab, you can set the wrapping policy for parameterized
+types, you can decide to wrap before or after operators in assignments and
+conditional expressions, and you can control the wrapping policy of
+`'for' loop headers`.
+
+image::images/formatter-wrap-for.png[]
+
+The _Align fields in columns_ feature in the _Indentation_ section can now
+be configured to _recognize groups separated by empty lines_ and align them
+independently.
+
+image::images/formatter-align-groups.png[]
+
+In the _New lines_ section, you can control if new lines should be added
+after annotations on `enum` constants.
+
+image::images/formatter-enum-constants.png[]
+
+==== Create new fields from method parameters
+
+You can now assign all parameters of a method or constructor to new fields
+at once using the new _Quick Assist_ (`Ctrl+1`):
+
+image::images/assign-all-params-to-new-fields.png[]
+
+=== Java Views, Wizards, and Other UI
+
+==== Project Explorer Improvements
+
+The _Project Explorer_ view now groups referenced libraries in a new container node.
+
+image::images/show-referenced-libraries-node-project-explorer.png[]
+
+You can now hide empty library containers in the _Project Explorer_ view by selecting
+the new filter in its _Customize View..._ dialog.
+
+image::images/hide-empty-library-containers-project-explorer.png[]
+
+==== Add meta-annotations while creating a new Java annotation type
+
+You can now choose to add `@Retention`, `@Target` and `@Documented` meta-annotations
+along with their applicable values while creating a new Java annotation type.
+
+image::images/add-meta-annotations.png[]
+
+==== Search on multi-selections
+
+You can now select multiple elements in views like _Package Explorer_ and
+_Outline_ and then search for _References_, _Declarations_, _Implementors_,
+and _Read/Write Access_ (where applicable):
+
+image::images/search-on-multi-selections.png[]
+
+You can even select results in the _Search_ view and start a new search for those
+elements. To follow method call chains, you'd probably use _Open Call Hierarchy_,
+though.
+
+==== JUnit Support
+
+Assertions are now enabled by default for new JUnit launch configurations. You can
+disable this on 1Preferences > Java > JUnit` page.
+
+=== Debug
+
+==== Installing breakpoints from unrelated projects
+
+Multiple versions of the same Java type can be available in a workspace, and
+each version can have breakpoints configured at different source locations. When
+debugging, JDT tries to determine the "right" set of breakpoints to install in
+the target VM. This analysis now uses Java project dependencies by default.
+
+To always install all enabled breakpoints, you can disable the new option
+`Preferences > Java > Debug > Do not install breakpoints from unrelated projects`.
+
+=== Null Analysis
+
+==== Multiple sets of null annotations
+
+You can now configure annotation-based null analysis to use multiple sets of
+annotation types. This is relevant if your project uses 3rd party libraries
+that already use null annotations in their API, where the annotations used in
+a library may be different from those used in the current project.
+
+Please open the dialog for configuring null annotation types from the project
+properties at `Java Compiler > Errors/Warnings > Null analysis`:
+
+image::images/prefs-errors-warnings.png[]
+
+In the dialog that opens, only one primary set of annotations is supported;
+these are the annotations which JDT actively uses in _Quick Fixes_, error
+messages etc. These annotations must be present on the project's build path.
+
+You can now add an arbitrary number of secondary null annotation types, to
+be evaluated when reading class files external to the project. Within the
+configuration dialog, Content Assist is offered based on accessible annotation
+types, but for secondary annotation types unresolved names will be tolerated.
+This avoids the need to bloat the build path with transitive compile-time
+dependencies.
+
+image::images/annotation-selection.png[]
+
+==== Improved null analysis with generics
+
+The interplay of null annotations and generics has been improved in several
+regards.
+
+The basic concepts had already been documented in the online help, but not
+all that was documented was actually checked by JDT's null analysis. With
+the changes outlined below, null analysis based on type annotations is even
+more capable than previous versions.
+
+(1) The first batch of contributed improvements implements what we call
+"pessimistic analysis for free type variables", which affects implementors
+of generic types.
+
+image::images/pessimistic-analysis.png[]
+
+In order to allow clients to instantiate such a generic class with either
+a `@NonNull` or a `@Nullable` type as substitution for the "free type variable"
+`<T>`, the implementation of that class must account for the worst in both
+directions:
+
+* To anticipate a `@NonNull` type, each field typed to a free type variable
+must be initialized with a non-`null` value, and passing `null` where `T` is
+expected is illegal; and
+* To anticipate a `@Nullable` type, each dereference must be preceded by a `null` check.
+
+At the bottom of each problem hover, you will find a link to the corresponding
+configuration option, should you like to change the severity of this diagnostic.
+Note that configurability is mainly given for smooth migration from previous
+JDT version; conceptually, problems detected by pessimistic analysis should be
+treated as errors, because they invalidate the null-guarantees given by a generic
+type.
+
+image::images/configure-pessimistic-analysis.png[]
+
+(2) The second improvement concerns consumption of generic types from a library,
+more specifically: invocations of library methods whose return type is given by
+a free type variable.
+
+If the library type is instantiated with a `@NonNull` type as the type argument,
+we generally want to interpret the mentioned return type as non-`null`, too.
+This is problematic only for some "legacy" methods, which may return `null`
+without declaring so. The most prominent example is `java.util.Map.get(K)`.
+
+The analysis cannot see whether absence of a null annotation for such a return
+type is intentional (in the above sense of "free type variables"), or an omission
+that should be fixed. For that reason a new warning has been implemented to alert
+about this situation.
+
+image::images/unsafe-nonnull-interpretation.png[]
+
+In the above example, both fields list and map provide `@NonNull` `String` as a type
+argument, hence the return types of both _get_ methods are interpreted as non-`null`.
+For `List` this is desired, for `Map` it is a bug.
+
+The dilemma can be resolved by adding a (possibly empty) external annotation file
+(`.eea`) to each affected library class. By using an empty annotation file, the user
+signals that all types in this class should be interpreted verbatim (like in the
+`List` case - use with care). In the other case, the missing `@Nullable` annotation
+should be added as an external annotation (like in the `Map` case).
+
+In a project that is not yet configured to use external annotations for the
+library in question, the warning is demoted to level "information". Generally, the
+severity of this problem is configured using the option right below the one mentioned
+above, titled `Unsafe '@NonNull'` interpretation of free type variable from library.
+
+(3) Finally, a small utility class, `org.eclipse.jdt.annotation.Checks`, has been
+included in the bundle `org.eclipse.jdt.annotation_2.1.0` containing helper methods
+for typical idioms for improving and documenting `null` safety.
+
+==== Quick Fix to add @NonNull to local variable
+
+When a "potential null pointer access" problem is raised against a local variable,
+the reason is not always obvious. Perhaps `null` is assigned somewhere deep inside
+a complex control flow. If annotation-based `null` analysis is enabled, a new
+_Quick Fix_ is offered (`Ctrl+1`), that adds a `@NonNull` annotation to the local
+variable.
+
+image::images/add-nonnull1.png[]
+
+While this may not produce correct code, it tells the compiler your intention to
+not allow `null` in this variable, and subsequently the compiler will answer with more
+helpful warnings or errors pointing to the root problem. In the given example,
+it will alert you of subtleties about using unconstrained type variables.
\ No newline at end of file
diff --git a/noteworthy/noteworthy.adoc b/noteworthy/noteworthy.adoc
index b337758..1a7ebb2 100644
--- a/noteworthy/noteworthy.adoc
+++ b/noteworthy/noteworthy.adoc
@@ -9,12 +9,15 @@
* Wayne Beaton (Eclipse Foundation)- initial API and implementation
//////////////////////////////////////////
+:toc:
+:toc-placement: auto
+:icons: font
+
:jeePackageUrl: https://www.eclipse.org/downloads/packages/eclipse-ide-java-ee-developers/marsr
:cdtPackageUrl: https://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/marsr
:pdtPackageUrl: https://www.eclipse.org/downloads/packages/eclipse-php-developers/marsr
-Eclipse Neon New and Noteworthy
--------------------------------
+= Eclipse Neon New and Noteworthy
Here are some of the noteworthy features in the Eclipse Neon Simultaneous Release.
diff --git a/noteworthy/noteworthy.html b/noteworthy/noteworthy.html
index 7c1b6bf..cd059d7 100644
--- a/noteworthy/noteworthy.html
+++ b/noteworthy/noteworthy.html
@@ -54,19 +54,52 @@
box-shadow: 10px 10px 5px #888888;*/
}
</style>
+<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.2.0/css/font-awesome.min.css">
</head>
<body class="article">
<div id="header">
+<h1>Eclipse Neon New and Noteworthy</h1>
+<div id="toc" class="toc">
+<div id="toctitle">Table of Contents</div>
+<ul class="sectlevel1">
+<li><a href="#platform">Platform</a>
+<ul class="sectlevel2">
+<li><a href="#_general">General</a></li>
+<li><a href="#_look_and_feel">Look and Feel</a></li>
+<li><a href="#_other_improvements">Other Improvements</a></li>
+</ul>
+</li>
+<li><a href="#java">Java™</a>
+<ul class="sectlevel2">
+<li><a href="#_java_editor">Java Editor</a></li>
+<li><a href="#_java_views_wizards_and_other_ui">Java Views, Wizards, and Other UI</a></li>
+<li><a href="#_debug">Debug</a></li>
+<li><a href="#_null_analysis">Null Analysis</a></li>
+</ul>
+</li>
+<li><a href="#cdt">C/C++</a>
+<ul class="sectlevel2">
+<li><a href="#_general_2">General</a></li>
+<li><a href="#other">Stuff</a></li>
+<li><a href="#_sources">Sources</a></li>
+</ul>
+</li>
+</ul>
+</div>
</div>
<div id="content">
-<div class="sect1">
-<h2 id="_eclipse_neon_new_and_noteworthy">Eclipse Neon New and Noteworthy</h2>
+<div id="preamble">
<div class="sectionbody">
<div class="paragraph">
<p>Here are some of the noteworthy features in the Eclipse Neon Simultaneous Release.</p>
</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="platform">Platform</h2>
+<div class="sectionbody">
<div class="sect2">
-<h3 id="platform">Platform</h3>
+<h3 id="_general">General</h3>
<div class="sect3">
<h4 id="_improved_interactive_performance_and_reduced_memory_consumption">Improved interactive performance and reduced memory consumption</h4>
<div class="paragraph">
@@ -107,6 +140,36 @@
</div>
</div>
<div class="sect3">
+<h4 id="_search_in_binary_files">Search in binary files</h4>
+<div class="paragraph">
+<p>The Search > File... dialog has a new option to search in binary files as well.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/search-binary-files.png" alt="search binary files">
+</div>
+</div>
+<div class="paragraph">
+<p>By default, the option is disabled, and matches are only reported in files that
+have the <strong>Text</strong> content type, or in files that have no content type and don’t
+contain the null character (\u0000).</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_automatic_save_of_dirty_editors">Automatic Save of dirty editors</h4>
+<div class="paragraph">
+<p>Auto-save of dirty editors is now available in Eclipse. The autosave option is disabled by default. A new autosave preference page (Preferences > General > Editors > Autosave) is available and allows to enable/disable the autosave and change the interval of autosave. The countdown is reset on keyboard activity, mouse click, or when a popup is displayed (e.g. content assist, preference page, …​).</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/autosave-preference-page.png" alt="autosave preference page">
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_look_and_feel">Look and Feel</h3>
+<div class="sect3">
<h4 id="_resolution_based_image_auto_scaling">Resolution-based image auto-scaling</h4>
<div class="paragraph">
<p>Images now automatically scale on high-DPI monitors on Windows and Linux,
@@ -135,22 +198,6 @@
</div>
</div>
<div class="sect3">
-<h4 id="_search_in_binary_files">Search in binary files</h4>
-<div class="paragraph">
-<p>The Search > File... dialog has a new option to search in binary files as well.</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="images/search-binary-files.png" alt="search binary files">
-</div>
-</div>
-<div class="paragraph">
-<p>By default, the option is disabled, and matches are only reported in files that
-have the <strong>Text</strong> content type, or in files that have no content type and don’t
-contain the null character (\u0000).</p>
-</div>
-</div>
-<div class="sect3">
<h4 id="_full_screen">Full Screen</h4>
<div class="paragraph">
<p>The Full Screen feature is now also available on Windows and Linux. You can toggle
@@ -190,17 +237,6 @@
</div>
</div>
<div class="sect3">
-<h4 id="_automatic_save_of_dirty_editors">Automatic Save of dirty editors</h4>
-<div class="paragraph">
-<p>Auto-save of dirty editors is now available in Eclipse. The autosave option is disabled by default. A new autosave preference page (Preferences > General > Editors > Autosave) is available and allows to enable/disable the autosave and change the interval of autosave. The countdown is reset on keyboard activity, mouse click, or when a popup is displayed (e.g. content assist, preference page, …​).</p>
-</div>
-<div class="imageblock">
-<div class="content">
-<img src="images/autosave-preference-page.png" alt="autosave preference page">
-</div>
-</div>
-</div>
-<div class="sect3">
<h4 id="_word_wrap_in_text_editors">Word wrap in text editors</h4>
<div class="paragraph">
<p>A Toggle Word Wrap button has been added to the workbench toolbar.
@@ -246,7 +282,7 @@
<table>
<tr>
<td class="icon">
-<div class="title">Note</div>
+<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
SWT currently only supports these gestures on OS X and on Windows systems
@@ -306,7 +342,7 @@
<table>
<tr>
<td class="icon">
-<div class="title">Note</div>
+<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
It’s possible to assign an editor for an <em>unassociated</em>
@@ -345,7 +381,29 @@
</div>
</div>
<div class="sect3">
-<h4 id="_other_improvements">Other Improvements</h4>
+<h4 id="_new_welcome_screen">New Welcome Screen</h4>
+<div class="paragraph">
+<p>The Welcome/Intro introduces a new <em>Solstice</em> theme that provides a new modern
+appearance and enhanced functionality.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/eclipse-welcome-solstice.png" alt="eclipse welcome solstice">
+</div>
+</div>
+<div class="paragraph">
+<p>In Eclipse 3.x, the <em>Go to Workbench</em> button on the Welcome page would minimize
+the Welcome page to the window status bar. This behavior has been restored.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/eclipse-welcome-launchbar.png" alt="eclipse welcome launchbar">
+</div>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_other_improvements">Other Improvements</h3>
<div class="paragraph">
<p>The look of the toolbar in the MacOS default theme was adjusted to align with
other MacOS applications.</p>
@@ -370,18 +428,392 @@
</div>
</div>
</div>
-<div class="sect2">
-<h3 id="java">Java™</h3>
+</div>
+<div class="sect1">
+<h2 id="java">Java™</h2>
+<div class="sectionbody">
<div class="paragraph">
<p>Eclipse Neon includes numerous bug fixes and improvements in the Java 8
support, along with a lot of other useful features.</p>
</div>
+<div class="sect2">
+<h3 id="_java_editor">Java Editor</h3>
+<div class="sect3">
+<h4 id="_ifnotnull_ifnull_templates">ifNotNull/ifNull templates</h4>
+<div class="paragraph">
+<p>The Java editor now offers default templates for creating "== null" and "!= null" checks.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/if-null-template.png" alt="if null template">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_new_info_severity_level">New Info severity level</h4>
+<div class="paragraph">
+<p>You can now specify <em>Info</em> as a severity level for the problems detected by the Eclipse
+Java compiler.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/info-severity.png" alt="info severity">
+</div>
+</div>
+<div class="paragraph">
+<p>A new decorator has been added to indicate information severity problems detected by the
+Eclipse Java Compiler.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/info-problem-decorator.png" alt="info problem decorator">
+</div>
+</div>
+<div class="paragraph">
+<p>You can now configure the severity of a compiler problem by invoking the new <em>Quick Fix</em>
+(<code>Ctrl+1</code>) which opens the <code>Java > Compiler > Errors/Warnings</code> preference page and
+highlights the configurable problem.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/configure-problem-severity.png" alt="configure problem severity">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_substring_code_completion">Substring code completion</h4>
+<div class="paragraph">
+<p>Content Assist now supports substring patterns. Enter any part of the desired proposal’s
+text, and Content Assist will find it! For example, completing on <code>selection</code> proposes
+all results containing <code>selection</code> as a substring.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/substring-code-completion.png" alt="substring code completion">
+</div>
+</div>
+<div class="paragraph">
+<p>This feature can be disabled using the <code>Show substring matches</code> option on the
+<code>Java > Editor > Content Assist</code> preference page.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_clean_up_to_remove_redundant_type_arguments">Clean Up to remove redundant type arguments</h4>
+<div class="paragraph">
+<p>A new option to remove redundant type arguments has been added under the
+<em>Unnecessary Code</em> group of the Clean Up profile.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/remove-redundant-type-arguments.png" alt="remove redundant type arguments">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_new_options_in_code_formatter">New options in code formatter</h4>
+<div class="paragraph">
+<p>In the new <em>Parentheses</em> tab, you can order the formatter to keep
+parentheses of various Java elements on separate lines, i.e. put a
+line break after the opening parenthesis and before the closing
+parenthesis. This can be done always, only when parentheses are
+not empty, or when their content is wrapped. There’s also an option
+to preserve existing positions, if you want to manually manage parentheses
+positions on a case-by-case basis.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/formatter-parentheses.png" alt="formatter parentheses">
+</div>
+</div>
+<div class="paragraph">
+<p>In the <em>Line Wrapping</em> tab, you can set the wrapping policy for parameterized
+types, you can decide to wrap before or after operators in assignments and
+conditional expressions, and you can control the wrapping policy of
+<code>'for' loop headers</code>.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/formatter-wrap-for.png" alt="formatter wrap for">
+</div>
+</div>
+<div class="paragraph">
+<p>The <em>Align fields in columns</em> feature in the <em>Indentation</em> section can now
+be configured to <em>recognize groups separated by empty lines</em> and align them
+independently.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/formatter-align-groups.png" alt="formatter align groups">
+</div>
+</div>
+<div class="paragraph">
+<p>In the <em>New lines</em> section, you can control if new lines should be added
+after annotations on <code>enum</code> constants.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/formatter-enum-constants.png" alt="formatter enum constants">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_create_new_fields_from_method_parameters">Create new fields from method parameters</h4>
+<div class="paragraph">
+<p>You can now assign all parameters of a method or constructor to new fields
+at once using the new <em>Quick Assist</em> (<code>Ctrl+1</code>):</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/assign-all-params-to-new-fields.png" alt="assign all params to new fields">
+</div>
+</div>
+</div>
</div>
<div class="sect2">
-<h3 id="cdt">C/C++</h3>
+<h3 id="_java_views_wizards_and_other_ui">Java Views, Wizards, and Other UI</h3>
+<div class="sect3">
+<h4 id="_project_explorer_improvements">Project Explorer Improvements</h4>
+<div class="paragraph">
+<p>The <em>Project Explorer</em> view now groups referenced libraries in a new container node.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/show-referenced-libraries-node-project-explorer.png" alt="show referenced libraries node project explorer">
+</div>
+</div>
+<div class="paragraph">
+<p>You can now hide empty library containers in the <em>Project Explorer</em> view by selecting
+the new filter in its <em>Customize View…​</em> dialog.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/hide-empty-library-containers-project-explorer.png" alt="hide empty library containers project explorer">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_add_meta_annotations_while_creating_a_new_java_annotation_type">Add meta-annotations while creating a new Java annotation type</h4>
+<div class="paragraph">
+<p>You can now choose to add <code>@Retention</code>, <code>@Target</code> and <code>@Documented</code> meta-annotations
+along with their applicable values while creating a new Java annotation type.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/add-meta-annotations.png" alt="add meta annotations">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_search_on_multi_selections">Search on multi-selections</h4>
+<div class="paragraph">
+<p>You can now select multiple elements in views like <em>Package Explorer</em> and
+<em>Outline</em> and then search for <em>References</em>, <em>Declarations</em>, <em>Implementors</em>,
+and <em>Read/Write Access</em> (where applicable):</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/search-on-multi-selections.png" alt="search on multi selections">
+</div>
+</div>
+<div class="paragraph">
+<p>You can even select results in the <em>Search</em> view and start a new search for those
+elements. To follow method call chains, you’d probably use <em>Open Call Hierarchy</em>,
+though.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_junit_support">JUnit Support</h4>
+<div class="paragraph">
+<p>Assertions are now enabled by default for new JUnit launch configurations. You can
+disable this on 1Preferences > Java > JUnit` page.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_debug">Debug</h3>
+<div class="sect3">
+<h4 id="_installing_breakpoints_from_unrelated_projects">Installing breakpoints from unrelated projects</h4>
+<div class="paragraph">
+<p>Multiple versions of the same Java type can be available in a workspace, and
+each version can have breakpoints configured at different source locations. When
+debugging, JDT tries to determine the "right" set of breakpoints to install in
+the target VM. This analysis now uses Java project dependencies by default.</p>
+</div>
+<div class="paragraph">
+<p>To always install all enabled breakpoints, you can disable the new option
+<code>Preferences > Java > Debug > Do not install breakpoints from unrelated projects</code>.</p>
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_null_analysis">Null Analysis</h3>
+<div class="sect3">
+<h4 id="_multiple_sets_of_null_annotations">Multiple sets of null annotations</h4>
+<div class="paragraph">
+<p>You can now configure annotation-based null analysis to use multiple sets of
+annotation types. This is relevant if your project uses 3rd party libraries
+that already use null annotations in their API, where the annotations used in
+a library may be different from those used in the current project.</p>
+</div>
+<div class="paragraph">
+<p>Please open the dialog for configuring null annotation types from the project
+properties at <code>Java Compiler > Errors/Warnings > Null analysis</code>:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/prefs-errors-warnings.png" alt="prefs errors warnings">
+</div>
+</div>
+<div class="paragraph">
+<p>In the dialog that opens, only one primary set of annotations is supported;
+these are the annotations which JDT actively uses in <em>Quick Fixes</em>, error
+messages etc. These annotations must be present on the project’s build path.</p>
+</div>
+<div class="paragraph">
+<p>You can now add an arbitrary number of secondary null annotation types, to
+be evaluated when reading class files external to the project. Within the
+configuration dialog, Content Assist is offered based on accessible annotation
+types, but for secondary annotation types unresolved names will be tolerated.
+This avoids the need to bloat the build path with transitive compile-time
+dependencies.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/annotation-selection.png" alt="annotation selection">
+</div>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_improved_null_analysis_with_generics">Improved null analysis with generics</h4>
+<div class="paragraph">
+<p>The interplay of null annotations and generics has been improved in several
+regards.</p>
+</div>
+<div class="paragraph">
+<p>The basic concepts had already been documented in the online help, but not
+all that was documented was actually checked by JDT’s null analysis. With
+the changes outlined below, null analysis based on type annotations is even
+more capable than previous versions.</p>
+</div>
+<div class="paragraph">
+<p>(1) The first batch of contributed improvements implements what we call
+"pessimistic analysis for free type variables", which affects implementors
+of generic types.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/pessimistic-analysis.png" alt="pessimistic analysis">
+</div>
+</div>
+<div class="paragraph">
+<p>In order to allow clients to instantiate such a generic class with either
+a <code>@NonNull</code> or a <code>@Nullable</code> type as substitution for the "free type variable"
+<code><T></code>, the implementation of that class must account for the worst in both
+directions:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>To anticipate a <code>@NonNull</code> type, each field typed to a free type variable
+must be initialized with a non-<code>null</code> value, and passing <code>null</code> where <code>T</code> is
+expected is illegal; and</p>
+</li>
+<li>
+<p>To anticipate a <code>@Nullable</code> type, each dereference must be preceded by a <code>null</code> check.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>At the bottom of each problem hover, you will find a link to the corresponding
+configuration option, should you like to change the severity of this diagnostic.
+Note that configurability is mainly given for smooth migration from previous
+JDT version; conceptually, problems detected by pessimistic analysis should be
+treated as errors, because they invalidate the null-guarantees given by a generic
+type.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/configure-pessimistic-analysis.png" alt="configure pessimistic analysis">
+</div>
+</div>
+<div class="paragraph">
+<p>(2) The second improvement concerns consumption of generic types from a library,
+more specifically: invocations of library methods whose return type is given by
+a free type variable.</p>
+</div>
+<div class="paragraph">
+<p>If the library type is instantiated with a <code>@NonNull</code> type as the type argument,
+we generally want to interpret the mentioned return type as non-<code>null</code>, too.
+This is problematic only for some "legacy" methods, which may return <code>null</code>
+without declaring so. The most prominent example is <code>java.util.Map.get(K)</code>.</p>
+</div>
+<div class="paragraph">
+<p>The analysis cannot see whether absence of a null annotation for such a return
+type is intentional (in the above sense of "free type variables"), or an omission
+that should be fixed. For that reason a new warning has been implemented to alert
+about this situation.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/unsafe-nonnull-interpretation.png" alt="unsafe nonnull interpretation">
+</div>
+</div>
+<div class="paragraph">
+<p>In the above example, both fields list and map provide <code>@NonNull</code> <code>String</code> as a type
+argument, hence the return types of both <em>get</em> methods are interpreted as non-<code>null</code>.
+For <code>List</code> this is desired, for <code>Map</code> it is a bug.</p>
+</div>
+<div class="paragraph">
+<p>The dilemma can be resolved by adding a (possibly empty) external annotation file
+(<code>.eea</code>) to each affected library class. By using an empty annotation file, the user
+signals that all types in this class should be interpreted verbatim (like in the
+<code>List</code> case - use with care). In the other case, the missing <code>@Nullable</code> annotation
+should be added as an external annotation (like in the <code>Map</code> case).</p>
+</div>
+<div class="paragraph">
+<p>In a project that is not yet configured to use external annotations for the
+library in question, the warning is demoted to level "information". Generally, the
+severity of this problem is configured using the option right below the one mentioned
+above, titled <code>Unsafe '@NonNull'</code> interpretation of free type variable from library.</p>
+</div>
+<div class="paragraph">
+<p>(3) Finally, a small utility class, <code>org.eclipse.jdt.annotation.Checks</code>, has been
+included in the bundle <code>org.eclipse.jdt.annotation_2.1.0</code> containing helper methods
+for typical idioms for improving and documenting <code>null</code> safety.</p>
+</div>
+</div>
+<div class="sect3">
+<h4 id="_quick_fix_to_add_nonnull_to_local_variable">Quick Fix to add @NonNull to local variable</h4>
+<div class="paragraph">
+<p>When a "potential null pointer access" problem is raised against a local variable,
+the reason is not always obvious. Perhaps <code>null</code> is assigned somewhere deep inside
+a complex control flow. If annotation-based <code>null</code> analysis is enabled, a new
+<em>Quick Fix</em> is offered (<code>Ctrl+1</code>), that adds a <code>@NonNull</code> annotation to the local
+variable.</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="images/add-nonnull1.png" alt="add nonnull1">
+</div>
+</div>
+<div class="paragraph">
+<p>While this may not produce correct code, it tells the compiler your intention to
+not allow <code>null</code> in this variable, and subsequently the compiler will answer with more
+helpful warnings or errors pointing to the root problem. In the given example,
+it will alert you of subtleties about using unconstrained type variables.</p>
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="cdt">C/C++</h2>
+<div class="sectionbody">
<div class="paragraph">
<p>C/C++ support is provided by the <a href="https://www.eclipse.org/downloads/packages/eclipse-ide-cc-developers/marsr">Eclipse IDE for C/C++ Developers</a>.</p>
</div>
+<div class="sect2">
+<h3 id="_general_2">General</h3>
<div class="sect3">
<h4 id="_import_projects_2">Import Projects</h4>
<div class="paragraph">
@@ -438,7 +870,7 @@
</div>
<div id="footer">
<div id="footer-text">
-Last updated 2016-05-31 15:54:11 -04:00
+Last updated 2016-06-01 15:11:10 -04:00
</div>
</div>
</body>
diff --git a/noteworthy/platform.adoc b/noteworthy/platform.adoc
index bc19a0e..199141a 100644
--- a/noteworthy/platform.adoc
+++ b/noteworthy/platform.adoc
@@ -10,18 +10,17 @@
//////////////////////////////////////////
[[platform]]
-Platform
-~~~~~~~~
+== Platform
-Improved interactive performance and reduced memory consumption
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+=== General
+
+==== Improved interactive performance and reduced memory consumption
This and earlier milestones contain a multitude of fixes to enhance interactive and startup performance of the Eclipse IDE, and to reduce overall memory consumption.
TBD: insert some benchmarks
-Import Projects
-^^^^^^^^^^^^^^^
+==== Import Projects
A new *Import Projects* wizard is available via the `File > Open Projects...`
menu and via the general `Import...` command under `General > Projects` from Folder
@@ -43,28 +42,7 @@
+org.eclipse.ui.ide.projectConfigurator+, so that other IDE components can contribute
detection and configuration specific to the technology they're supporting.
-Resolution-based image auto-scaling
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Images now automatically scale on high-DPI monitors on Windows and Linux,
-similar to the Mac's Retina support on OS X. In the absence of high-resolution
-images, available images are automatically scaled proportionately to the
-resolution of the monitor.
-
-image::images/swt-high-dpi.png[]
-
-Preference setting to disable CSS based theming
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-You can disable the CSS-based styling of the Eclipse IDE via
-+Preferences > General > Appearance > Enable theming+. This will prevent the Eclipse
-Workbench from rendering custom colors, shades, and borders, and may result in better
-performance.
-
-image::images/enable-disable-theming.png[]
-
-Search in binary files
-^^^^^^^^^^^^^^^^^^^^^^
+==== Search in binary files
The +Search > File...+ dialog has a new option to search in binary files as well.
@@ -74,16 +52,40 @@
have the *Text* content type, or in files that have no content type and don't
contain the null character (+\u0000+).
-Full Screen
-^^^^^^^^^^^
+==== Automatic Save of dirty editors
+
+Auto-save of dirty editors is now available in Eclipse. The autosave option is disabled by default. A new autosave preference page (Preferences > General > Editors > Autosave) is available and allows to enable/disable the autosave and change the interval of autosave. The countdown is reset on keyboard activity, mouse click, or when a popup is displayed (e.g. content assist, preference page, ...).
+
+image::images/autosave-preference-page.png[]
+
+=== Look and Feel
+
+==== Resolution-based image auto-scaling
+
+Images now automatically scale on high-DPI monitors on Windows and Linux,
+similar to the Mac's Retina support on OS X. In the absence of high-resolution
+images, available images are automatically scaled proportionately to the
+resolution of the monitor.
+
+image::images/swt-high-dpi.png[]
+
+==== Preference setting to disable CSS based theming
+
+You can disable the CSS-based styling of the Eclipse IDE via
++Preferences > General > Appearance > Enable theming+. This will prevent the Eclipse
+Workbench from rendering custom colors, shades, and borders, and may result in better
+performance.
+
+image::images/enable-disable-theming.png[]
+
+==== Full Screen
The Full Screen feature is now also available on Windows and Linux. You can toggle
the mode via shortcut (+pass:[Alt+F11]+) or menu (+Window > Appearance > Toggle Full Screen+).
When Full Screen is activated, you'll see a dialog which tells you how to turn it off again.
-Hide the window toolbars
-^^^^^^^^^^^^^^^^^^^^^^^^
+==== Hide the window toolbars
You can use the Toggle Visibility of all Toolbars command (via Quick Access:
+Ctrl+3+ or +Command+3+) to hide all currently visible toolbars of the currently
@@ -102,15 +104,7 @@
image::images/ide-full-screen.png[]
-Automatic Save of dirty editors
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Auto-save of dirty editors is now available in Eclipse. The autosave option is disabled by default. A new autosave preference page (Preferences > General > Editors > Autosave) is available and allows to enable/disable the autosave and change the interval of autosave. The countdown is reset on keyboard activity, mouse click, or when a popup is displayed (e.g. content assist, preference page, ...).
-
-image::images/autosave-preference-page.png[]
-
-Word wrap in text editors
-^^^^^^^^^^^^^^^^^^^^^^^^^
+==== Word wrap in text editors
A Toggle Word Wrap button has been added to the workbench toolbar.
Shortcut: +Alt+Shift+Y+.
@@ -119,8 +113,7 @@
By default, text editors are opened with word wrap disabled.
-Commands and shortcuts to zoom in text editors
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+==== Commands and shortcuts to zoom in text editors
In text editors, you can now use Zoom In (+pass:[Ctrl++]+ or +pass:[Ctrl+=]+)
and Zoom Out (+pass:[Ctrl+-]+) commands to increase and decrease the font size.
@@ -130,8 +123,7 @@
If the editor type's font is configured to use a default font, then that
default font will be zoomed.
-Pinch to zoom in text editors
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+==== Pinch to zoom in text editors
To temporarily zoom the editor font in text editors, use a "pinch" gesture on a
touchpad. Put two fingers on the touchpad and move them apart or together.
@@ -146,8 +138,7 @@
that use the native multi-touch support. Touchpads that emulate mouse move/scroll
events don't support gestures. Gesture support on GTK is not implemented yet.
-Directly start previously selected workspaces in the launcher
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+==== Directly start previously selected workspaces in the launcher
The workspace selection dialog now allows you to start a previously selected
workspace directly via a link. The path to the workspace is shortened. The full
@@ -157,8 +148,7 @@
You can remove existing entries via the context menu.
-Selecting the text editor for unassociated file types
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+==== Selecting the text editor for unassociated file types
On the +Preferences > General > Editors > File Association+ page, you can now
define an editor selection strategy for unassociated file types. Three strategies
@@ -182,8 +172,7 @@
The implementation comes with a new extension-point +org.eclipse.ui.ide.unknownEditorStrategy+
that allows external contributions of additional strategies.
-Quick Access improvements
-^^^^^^^^^^^^^^^^^^^^^^^^^
+==== Quick Access improvements
Quick Access (+pass:[Ctrl+3]+) is a small text field in the toolbar. You can use it to
trigger any command in the Eclipse Workbench.
@@ -199,8 +188,19 @@
window, and the list with previous choices already opens when you click the field
with the mouse.
-Other Improvements
-^^^^^^^^^^^^^^^^^^
+==== New Welcome Screen
+
+The Welcome/Intro introduces a new _Solstice_ theme that provides a new modern
+appearance and enhanced functionality.
+
+image::images/eclipse-welcome-solstice.png[]
+
+In Eclipse 3.x, the _Go to Workbench_ button on the Welcome page would minimize
+the Welcome page to the window status bar. This behavior has been restored.
+
+image::images/eclipse-welcome-launchbar.png[]
+
+=== Other Improvements
The look of the toolbar in the MacOS default theme was adjusted to align with
other MacOS applications.
