JDK9Support

(Difference between revisions)
 
(11 intermediate revisions not shown)
Line 1: Line 1:
-
<h1>JDK9 EA Support</H1>
+
NetBeans has been donated by Oracle to Apache, where it continues to be actively developed. Go to [https://netbeans.apache.org netbeans.apache.org] for the latest details, go to [https://netbeans.apache.org/download/nb90/ https://netbeans.apache.org/download/nb90] in particular.
 +
 
 +
<!--
 +
 
 +
<h1>Oracle NetBeans</h1>
 +
 
 +
<h3>JDK9 EA Support</h3>
'''NOTE''' Always use latest JDK9 EA build when working with NetBeans Daily development builds. Refer to [[#not_working|What does not Work chapter]] for latest updates on compatibility issues.
'''NOTE''' Always use latest JDK9 EA build when working with NetBeans Daily development builds. Refer to [[#not_working|What does not Work chapter]] for latest updates on compatibility issues.
Line 26: Line 32:
NetBeans JDK 9 builds support:  
NetBeans JDK 9 builds support:  
* NB Java SE project support one JDK9/Jigsaw module - Single module project.  
* NB Java SE project support one JDK9/Jigsaw module - Single module project.  
 +
* Java SE Multi module project - Ant based project containing several modules and compiling them at once.
* Maven projects  
* Maven projects  
* module-info.java support: editing works and using its statement to set module boundaries for projects
* module-info.java support: editing works and using its statement to set module boundaries for projects
Line 45: Line 52:
Particular class/field/module might vary. NetBeans IDE JavaSE and JS distributions were fixed since daily build 201701130001 (Jan 13th) and now opens several packages for reflection. It might happen than when running daily dev build on top of JDK9 EA with additional modules/clusters installed then setAccessible to some other field might be used. It might be also invoked from bundled 3rd party library we even cannot fix. In such a case add a statement like this, e.g. '''-J--add-opens java.base/java.util=ALL-UNNAMED''' (provide your module and package) to netbeans.conf '''netbeans_default_options=''' and run IDE again. For modules in standard netbeans distros (Java EE,...) report the bug to NB Bugzilla using JDK_9 keyword. We will fix that in netbeans.conf in upcoming daily build.
Particular class/field/module might vary. NetBeans IDE JavaSE and JS distributions were fixed since daily build 201701130001 (Jan 13th) and now opens several packages for reflection. It might happen than when running daily dev build on top of JDK9 EA with additional modules/clusters installed then setAccessible to some other field might be used. It might be also invoked from bundled 3rd party library we even cannot fix. In such a case add a statement like this, e.g. '''-J--add-opens java.base/java.util=ALL-UNNAMED''' (provide your module and package) to netbeans.conf '''netbeans_default_options=''' and run IDE again. For modules in standard netbeans distros (Java EE,...) report the bug to NB Bugzilla using JDK_9 keyword. We will fix that in netbeans.conf in upcoming daily build.
-
===Other features===
 
-
* Multiple JDK9 modules in one NB project
 
== How to start ==
== How to start ==
Line 89: Line 94:
[[image: JunitTestsInModule.png]]
[[image: JunitTestsInModule.png]]
-
The structure is very similar to non-modular Java development. Simply add JUnit tests into Test Packages or leverage existing JUnit tests in a project. Then run the tests using ''project'' context menu '''Test  Alt+F6'' or ''Test File'' (Ctrl+F6) for single Java file.
+
The structure is very similar to non-modular Java development. Simply add JUnit tests into Test Packages or leverage existing JUnit tests in a project. Junit jar file needs to be added to Test Libraries. Then run the tests using ''project'' context menu '''Test  Alt+F6'' or ''Test File'' (Ctrl+F6) for single Java file.
==== JUnit tests in own module ====
==== JUnit tests in own module ====
Line 115: Line 120:
[[image:add_dependency_2_nodule_info.png]]
[[image:add_dependency_2_nodule_info.png]]
-
NetBeans Maven support is under development to provide other productivity features for Maven projects.
+
==== Unit testing ====
 +
Unit testing is possible as of Apache Maven Compiler Pluging v 3.6.1
-
==== maven-surefire-plugin ====
+
=== What does not work  ===
-
* Unit tests are not working, waiting for Maven Surefire plugin to support JDK9.
+
NetBeans Maven support is under development to provide other productivity features for Maven projects.
-
* has  to support modulepath
+
==== maven-javadoc-plugin ====
==== maven-javadoc-plugin ====
Line 147: Line 152:
====Changing NetBeans JDK runtime platform====
====Changing NetBeans JDK runtime platform====
How to change a JDK NetBeans uses for runtime is specified [[FaqJdkHome]] or in [[FaqNetbeansConf]].
How to change a JDK NetBeans uses for runtime is specified [[FaqJdkHome]] or in [[FaqNetbeansConf]].
 +
 +
-->

Current revision as of 08:28, 21 July 2018

NetBeans has been donated by Oracle to Apache, where it continues to be actively developed. Go to netbeans.apache.org for the latest details, go to https://netbeans.apache.org/download/nb90 in particular.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo