Bug 533730 - N&N for Photon (4.8)I20180521-0800I20180520-2000I20180520-0800I20180519-1500I20180519-0800I20180518-2000

- Updated with sharper images in "Java™ 10 Support" section
- Moved few items from "Java Editor" and "Java Views and Dialogs" to
"Java™ 9 Support" section
- Fixed HTML validation error in jdt_whatsnew.html

Change-Id: Ib98b53cbf68e152ef09d5b55adbf952c58775634
Signed-off-by: Niraj Modi <niraj.modi@in.ibm.com>

3 files changed, 87 insertions, 86 deletions

diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.compliance.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.compliance.png
index f12e4c6a8..e28b535d1 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.compliance.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.compliance.png
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.png b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.png
index 931298881..0f1b3834f 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.png
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/images/j10.png
diff --git a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
index 7da03e240..efc38cb98 100644
--- a/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
+++ b/bundles/org.eclipse.jdt.doc.user/whatsNew/jdt_whatsnew.html
@@ -285,6 +285,90 @@ document for changes in the Platform.</p>
 
     </td>
   </tr>
+  <tr id="module-info-paste">
+    <td class="title">Paste module-info.java code in Package Explorer</td>
+    <td class="content">
+      You can now paste a snippet of code representing module-info.java directly into a source folder to create a module-info.java file. 
+      For example, copy this code:
+<pre>
+import java.sql.Driver;
+module hello {
+	exports org.example;
+	requires java.sql;
+	provides Driver with org.example.DriverImpl;
+}
+</pre>
+	Then, select a source folder in a Java 9 project in the <b>Package Explorer</b> view and use <b>Ctrl+V (Edit &gt; Paste)</b> to paste it.
+	This automatically creates a module-info.java file in the source folder with the copied content.      
+    </td>
+  </tr>
+  
+  <tr id="content-assist-module-declaration-name">
+    <td class="title">Content assist for module declaration name</td>
+    <td class="content">
+      Content assist <b>(Ctrl+Space)</b> support is now available for module declaration name. 
+      <p><img src="images/content-assist-module-declaration-name.png" alt=""/></p>
+    </td>
+  </tr>
+  
+  <tr id="quickfix-javadoc">
+    <td class="title">Quick Fix for <code>unresolved module</code> on module name in <code>requires directive</code></td>
+    <td class="content">
+      A new quick fix  is offered on <b>requires</b> statements in the <b>module-info.java</b> file to fix issues that are reported due to unresolved module.
+      The below quick fix will be provided if the module related to the unresolved module error has its related classpath added to the classpath and not to the module path.
+      <p>This quick fix is applicable if the project is a Java 9 project and has a module-info.java file</p>
+      <p>This quick fix can be invoked from the editor.</p> 
+      <p><img src="images/java9-module-requires-move-from-classpath-to-modulepath-quickfix.png" alt=""/></p>
+      <p>Before the quick fix is applied the classpath entries look as below: </p>
+      <p><img src="images/java9-module-requires-move-from-classpath-to-modulepath-CPE-before-quickfix.png" alt=""/></p>
+      <p>After the quick fix is applied the classpath entries look as below: </p>
+      <p><img src="images/java9-module-requires-move-from-classpath-to-modulepath-CPE-after-quickfix.png" alt=""/></p>
+    </td>
+  </tr>
+
+  <tr>
+    <td class="title">Quick fix for <code>Non-existing or empty package</code> on <code> exports directive</code></td>
+    <td class="content">
+    <p>A new quick fix is available when you have a <code> non-existing or an empty package</code> in an <code>exports directive</code> in module-info.java file.</p>
+	<p>This quick fix is applicable if the project is a Java9 project or above and has a <code>module-info.java</code> file.</p>
+    <p>The quick fix can be invoked from the editor:</p>
+    <p><img src="images/java9_quickfix_empty_nonexistant_package_on_exports_directive.png" alt=""/></p>
+    <p>A quick fix is provided to create either a Class, or an Interface or an Annotation or an Enum in the given package.</p>
+    <p>If the package does not exist, a new package is created and the new element is created in the package.</p>
+    </td>
+  </tr>
+
+  <tr id="newproject-modulefile">
+    <td class="title">Creation of <code>module-info.java file</code> on creation of a new Java9 Project</td>
+    <td class="content">
+      When creating a Java project with compliance Java 9 or above, a new option is offered for the creation of the <code>module-info.java</code> file.
+      <p>A new checkbox has been added in the Java Settings page (Page 2) of the <b>New Java Project</b> wizard. See images below. </p>
+      Page 1:
+      <p><img src="images/create_Java_Project_1.png" alt=""/></p>
+      Page 2:
+      <p><img src="images/create_Java_Project_2.png" alt=""/></p>
+      <p>The new checkbox for the creation of module-info.java file is checked by default.</p>
+      <p>When this checkbox is checked, upon project creation, the dialog for creation of a new <code> module-info.java </code> file will appear.</p>
+      <p><img src="images/create_module_info.png" alt=""/></p>
+      <p>Selecting <b>Don't Create</b> in the above dialog does not create the <code>module-info.java</code> file, but creates the project.</p>
+    </td>
+  </tr>
+  
+  <tr id="override-dependencies">
+    <td class="title">Overriding modular build path dependencies for launching</td>
+    <td class="content">
+      Based on Java build path, a Java 9 module can have command line options. These options from build path can be overridden for launching programs in the module.
+      <b>Override Dependencies</b> button has been added to <b>Dependencies</b> tab:
+      <p>
+        <img src="images/override-dependencies-button.png" alt="Override Dependencies button" />
+      </p>
+      Dialog can be used to override modular dependencies:
+      <p>
+        <img src="images/override-dependencies-dialog.png" alt="Override Dependencies dialog" />
+      </p>
+    </td>
+  </tr>
+
   <!-- ******************* JUnit ************************************* -->
   <tr>
     <td id="JUnit" class="section" colspan="2">
@@ -418,47 +502,6 @@ document for changes in the Platform.</p>
     </td>
   </tr>
   
-  <tr id="module-info-paste">
-    <td class="title">Paste module-info.java code in Package Explorer</td>
-    <td class="content">
-      You can now paste a snippet of code representing module-info.java directly into a source folder to create a module-info.java file. 
-      For example, copy this code:
-<pre>
-import java.sql.Driver;
-module hello {
-	exports org.example;
-	requires java.sql;
-	provides Driver with org.example.DriverImpl;
-}
-</pre>
-	Then, select a source folder in a Java 9 project in the <b>Package Explorer</b> view and use <b>Ctrl+V (Edit &gt; Paste)</b> to paste it.
-	This automatically creates a module-info.java file in the source folder with the copied content.      
-    </td>
-  </tr>
-  
-  <tr id="content-assist-module-declaration-name">
-    <td class="title">Content assist for module declaration name</td>
-    <td class="content">
-      Content assist <b>(Ctrl+Space)</b> support is now available for module declaration name. 
-      <p><img src="images/content-assist-module-declaration-name.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="quickfix-javadoc">
-    <td class="title">Quick Fix for <code>unresolved module</code> on module name in <code>requires directive</code></td>
-    <td class="content">
-      A new quick fix  is offered on <b>requires</b> statements in the <b>module-info.java</b> file to fix issues that are reported due to unresolved module.
-      The below quick fix will be provided if the module related to the unresolved module error has its related classpath added to the classpath and not to the module path.
-      <p>This quick fix is applicable if the project is a Java 9 project and has a module-info.java file</p>
-      <p>This quick fix can be invoked from the editor.</p> 
-      <p><img src="images/java9-module-requires-move-from-classpath-to-modulepath-quickfix.png" alt=""/></p>
-      <p>Before the quick fix is applied the classpath entries look as below: </p>
-      <p><img src="images/java9-module-requires-move-from-classpath-to-modulepath-CPE-before-quickfix.png" alt=""/></p>
-      <p>After the quick fix is applied the classpath entries look as below: </p>
-      <p><img src="images/java9-module-requires-move-from-classpath-to-modulepath-CPE-after-quickfix.png" alt=""/></p>
-    </td>
-  </tr>
-  
   <tr id="quickfix-nnbd-on-package">
     <td class="title">Quick Fix to add <code>@NonNullByDefault</code> to packages</td>
     <td class="content">
@@ -517,17 +560,6 @@ module hello {
     </td>
   </tr>
 
-  <tr>
-    <td class="title">Quick fix for <code>Non-existing or empty package</code> on <code> exports directive</code></td>
-    <td class="content">
-    <p>A new quick fix is available when you have a <code> non-existing or an empty package</code> in an <code>exports directive</code> in module-info.java file.</p>
-	<p>This quick fix is applicable if the project is a Java9 project or above and has a <code>module-info.java</code> file.</p>
-    <p>The quick fix can be invoked from the editor:</p>
-    <p><img src="images/java9_quickfix_empty_nonexistant_package_on_exports_directive.png" alt=""/></p>
-    <p>A quick fix is provided to create either a Class, or an Interface or an Annotation or an Enum in the given package.</p>
-    <p>If the package does not exist, a new package is created and the new element is created in the package.</p>
-    </td>
-  </tr>
   <!-- ******************* Java Views and Dialogs ************************************* -->
   <tr>
     <td id="JavaViewsAndDialogs" class="section" colspan="2">
@@ -583,37 +615,6 @@ These command line options are part of what can be overridden using the new <a h
     </td>
   </tr>
   
-  <tr id="newproject-modulefile">
-    <td class="title">Creation of <code>module-info.java file</code> on creation of a new Java9 Project</td>
-    <td class="content">
-      When creating a Java project with compliance Java 9 or above, a new option is offered for the creation of the <code>module-info.java</code> file.
-      <p>A new checkbox has been added in the Java Settings page (Page 2) of the <b>New Java Project</b> wizard. See images below. </p>
-      Page 1:
-      <p><img src="images/create_Java_Project_1.png" alt=""/></p>
-      Page 2:
-      <p><img src="images/create_Java_Project_2.png" alt=""/></p>
-      <p>The new checkbox for the creation of module-info.java file is checked by default.</p>
-      <p>When this checkbox is checked, upon project creation, the dialog for creation of a new <code> module-info.java </code> file will appear.</p>
-      <p><img src="images/create_module_info.png" alt=""/></p>
-      <p>Selecting <b>Don't Create</b> in the above dialog does not create the <code>module-info.java</code> file, but creates the project.</p>
-    </td>
-  </tr>
-  
-  <tr id="override-dependencies">
-    <td class="title">Overriding modular build path dependencies for launching</td>
-    <td class="content">
-      Based on Java build path, a Java 9 module can have command line options. These options from build path can be overridden for launching programs in the module.
-      <b>Override Dependencies</b> button has been added to <b>Dependencies</b> tab:
-      <p>
-        <img src="images/override-dependencies-button.png" alt="Override Dependencies button" />
-      </p>
-      Dialog can be used to override modular dependencies:
-      <p>
-        <img src="images/override-dependencies-dialog.png" alt="Override Dependencies dialog" />
-      </p>
-    </td>
-  </tr>
-  
   <tr id="sort-library-entries-jdt">
     <td class="title">Sort library entries alphabetically in Package Explorer</td>
     <td class="content">
@@ -730,7 +731,8 @@ These command line options are part of what can be overridden using the new <a h
       <b>Java Compiler > Annotation Processing</b> as <b>Generated test source directory</b>.
       <p><img src="images/testsources-apt-531072.png" alt=""/></p>
     </td>
-    
+ 	</tr>
+
     <tr id="jdt-complier-building-preference">
     <td class="title">New preference added "Compiler Compliance does not match used JRE"</td>
     <td class="content">
@@ -744,8 +746,7 @@ These command line options are part of what can be overridden using the new <a h
      <p> This preference can be set as shown below: </p>
      <p><img src="images/jdt_compiler_compliance_mismatch_JRE.png" alt=""/></p>
     </td>
-  </tr>
-  </tr>
+    </tr>
   
   <!-- ******************* Java Formatter ************************************* -->
   <tr>