...
- Java EE 8 support, for the first time since 11.1, for Maven-based and Gradle-based Web applications. The new Java EE 8 support provides the ability to create Java EE 8 applications and deploy to a Java EE 8 container, with new "webapp-javaee8" Maven archetype created for use with Apache NetBeans.
Support for JSF 2.3; CDI Changes for JSF Artifact Injection (introduced in 11.3), e.g., f:websocket is now supported:
Payara integration out of the box for the first time, including Payara Platform 5.194/5.201 support and Payara Server Hot Deploy support. - Support for GlassFish 5.0.1.
JavaFX
- The two OpenJFX Gluon Maven samples are now registered in the New Project dialog (from 11.2) – JavaFX test spec should be enhanced to try out these two samples and make sure they work.
Maven
- Impacted NetCAT test spec: Maven/Java EE Support Test Specification - javaee, cloned to 12.0: https://netbeans-vm.apache.org/synergy/client/app/#/title/maven%252Fjava_ee_support_test_specification_-_javaee/12.0
Task to be added to test spec:
Status: To be done. - Support for JSF 2.3; CDI Changes for JSF Artifact Injection (introduced in 11.3), e.g., f:websocket is now supported:
Impacted NetCAT test spec: Maven/Java EE Support Test Specification - javaee, cloned to 12.0: https://netbeans-vm.apache.org/synergy/client/app/#/title/maven%252Fjava_ee_support_test_specification_-_javaee/12.0
Task to be added to test spec:
Status: To be done. - Payara integration out of the box for the first time, including Payara Platform 5.194/5.201 support and Payara Server Hot Deploy support.
Impacted NetCAT test spec: Maven/Java EE Support Test Specification - javaee, cloned to 12.0: https://netbeans-vm.apache.org/synergy/client/app/#/title/maven%252Fjava_ee_support_test_specification_-_javaee/12.0
Task to be added to test spec:
Status: To be done. - Enabling Java preview features in a Maven project – new task needed in a Maven-related test spec, after creating new Java Maven project, the following must be added and then check whether one or more preview features (see above) can be used in the Java editor.
<build> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>3.8.0</version> <configuration> <compilerArgs> <arg>--enable-preview</arg> </compilerArgs> </configuration> </plugin> </plugins> </build>Support for GlassFish 5.0.1.
Impacted NetCAT test spec: Maven/Java EE Support Test Specification - javaee, cloned to 12.0: https://netbeans-vm.apache.org/synergy/client/app/#/title/mavenmaven%252Fjava_ee_support_test_specification_-_javaee/12.0
Tasks Task to be added to test spec: Add above to the POM of a Maven application and verify that preview features can be used.
Status: To be done. New test case to be added to section 11, "Edit pom.xml file".
Related to the above, new hint in Java Editor to turn on Preview Features in Maven-based Java projects:
When the above is clicked, i.e., this happens when a preview feature is recognized but the POM hasn't yet been updated to support it, the following is added to the POM:<build>
Impacted NetCAT test spec: Java Hints, cloned to 12.0: https://netbeans-vm.apache.org/synergy/client/app/#/specification/449
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<compilerArgs>
<arg>--enable-preview</arg>
</compilerArgs>
</configuration>
</plugin>
</plugins>
</build>
Task to be added to test spec: Run 12.0 on JDK 12, 13, or 14, make sure to uninstall nb-javac if installed, create a Maven application and add a Java source file. Type String text = """ """, at which point the hint should appear, prompting the POM entry above to be generated.
Status: Done. Added as test case 3 in the new section 5, "Java Language Preview Features", of the above Java Hint test spec.
JaCoCo integration with Maven works again, make sure to check that during NetCAT 12.0 by adding a task around this in the Maven test spec.
Impacted NetCAT test spec: Maven Support Test Specification, https://netbeans-vm.apache.org/synergy/client/app/#/title/maven_support_test_specification/.<plugin> <groupId>org.jacoco</groupId> <artifactId>jacoco-maven-plugin</artifactId> <version>0.8.3</version> <executions> <execution> <goals> <goal>prepare-agent</goal> </goals> </execution> <execution> <id>report</id> <phase>prepare-package</phase> <goals> <goal>report</goal> </goals> <configuration> <outputDirectory>${project.reporting.outputDirectory}/jacoco_test</outputDirectory> </configuration> </execution> </executions> </plugin>
Task to be added to test spec: Run 12.0, create a Maven application and add a Java source file. Add the above to the POM and then verify that the JaCoCo functionality is available on the Maven project's context menu.
Status: To be done. New test case to be added to section 11, "Edit pom.xml file".
Maven-based NetBeans modules can be created again, this was broken, make sure this works again correctly.
Impacted NetCAT test spec: Maven Support Test Specification - Maven Platform support, https://netbeans-vm.apache.org/synergy/client/app/#/title/maven_support_test_specification_-_maven_platform_support/
Tasks to be added to test spec:
-- Run 12.0, create a new Maven NetBeans module, add a Window Component, run it. Should result in NetBeans starting up and having a new window.
-- Run 12.0, create a new Maven NetBeans application, run it, add a module, add a Window Component, run it. Should result in new NetBeans application starting up and having a new window.
Status: Done, both these test cases are already in the Maven Support Test Specification - Maven Platform support test spec.
Default JDK for Maven projects can be set.
Gradle
...
tasks.withType(JavaCompile).each {
it.options.compilerArgs.add('--enable-preview')
}
run.jvmArgs(['--enable-preview'])
-
Status: To be done.
JavaFX
- The two OpenJFX Gluon Maven samples are now registered in the New Project dialog (from 11.2) – JavaFX test spec should be enhanced to try out these two samples and make sure they work.
Impacted NetCAT test spec: JavaFX Create Projects, cloned to 12.0: https://netbeans-vm.apache.org/synergy/client/app/#/specification/452
Task to be added to test spec:
-- Create new FXML JavaFX Maven Archetype (Gluon)
-- Create new Simple JavaFX Maven Archetype (Gluon)
Status: To be done.
Maven
- Enabling Java preview features in a Maven project – new task needed in a Maven-related test spec, after creating new Java Maven project, the following must be added and then check whether one or more preview features (see above) can be used in the Java editor.
<build> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>3.8.0</version> <configuration> <compilerArgs> <arg>--enable-preview</arg> </compilerArgs> </configuration> </plugin> </plugins> </build>
Impacted NetCAT test spec: Maven Support Test Specification, https://netbeans-vm.apache.org/synergy/client/app/#/title/maven_support_test_specification/.
Tasks to be added to test spec: Add above to the POM of a Maven application and verify that preview features can be used.
Status: To be done. New test case to be added to section 11, "Edit pom.xml file". - Related to the above, new hint in Java Editor to turn on Preview Features in Maven-based Java projects:
When the above is clicked, i.e., this happens when a preview feature is recognized but the POM hasn't yet been updated to support it, the following is added to the POM:<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.3</version>
<configuration>
<compilerArgs>
<arg>--enable-preview</arg>
</compilerArgs>
</configuration>
</plugin>
</plugins>
</build>
Impacted NetCAT test spec: Java Hints, cloned to 12.0: https://netbeans-vm.apache.org/synergy/client/app/#/specification/449
Task to be added to test spec: Run 12.0 on JDK 12, 13, or 14, make sure to uninstall nb-javac if installed, create a Maven application and add a Java source file. Type String text = """ """, at which point the hint should appear, prompting the POM entry above to be generated.
Status: Done. Added as test case 3 in the new section 5, "Java Language Preview Features", of the above Java Hint test spec. - JaCoCo integration with Maven works again, make sure to check that during NetCAT 12.0 by adding a task around this in the Maven test spec.
<plugin> <groupId>org.jacoco</groupId> <artifactId>jacoco-maven-plugin</artifactId> <version>0.8.3</version> <executions> <execution> <goals> <goal>prepare-agent</goal> </goals> </execution> <execution> <id>report</id> <phase>prepare-package</phase> <goals> <goal>report</goal> </goals> <configuration> <outputDirectory>${project.reporting.outputDirectory}/jacoco_test</outputDirectory> </configuration> </execution> </executions> </plugin>
Impacted NetCAT test spec: Maven Support Test Specification, https://netbeans-vm.apache.org/synergy/client/app/#/title/maven_support_test_specification/.
Task to be added to test spec: Run 12.0, create a Maven application and add a Java source file. Add the above to the POM and then verify that the JaCoCo functionality is available on the Maven project's context menu.
Status: To be done. New test case to be added to section 11, "Edit pom.xml file". - Maven-based NetBeans modules can be created again, this was broken, make sure this works again correctly.
Impacted NetCAT test spec: Maven Support Test Specification - Maven Platform support, https://netbeans-vm.apache.org/synergy/client/app/#/title/maven_support_test_specification_-_maven_platform_support/
Tasks to be added to test spec:
-- Run 12.0, create a new Maven NetBeans module, add a Window Component, run it. Should result in NetBeans starting up and having a new window.
-- Run 12.0, create a new Maven NetBeans application, run it, add a module, add a Window Component, run it. Should result in new NetBeans application starting up and having a new window.
Status: Done, both these test cases are already in the Maven Support Test Specification - Maven Platform support test spec. - Default JDK for Maven projects can be set.
Gradle
Enabling Java preview features in a Gradle project – new task needed in a new Gradle-related test spec, after creating new Java Gradle project, the following must be added and then check whether one or more preview features (see above) can be used in the Java editor.
Code Block language groovy theme Midnight title build.gradle snippet tasks.withType(JavaCompile).each { it.options.compilerArgs.add('--enable-preview') } run.jvmArgs(['--enable-preview'])
- Gradle JavaEE Support
PHP
- PHP 7.4 Language Features and some new hints: see 11.2 Feature: PHP
- Autocomplete for PHP property and method without $this→
HiDPI and Painting Bugfixes
- In the editor, fix incorrectly positioned line-width marker (e.g. shown at 82 characters instead of 80 characters), and inaccurate tab alignments. This bug existed at certain editor zoom levels on Windows, Linux, and MacOS, including on non-HiDPI screens.
- Fix clipped file names in "Projects" pane on Windows on HiDPI screens.
Reference: Complete Listing of Closed PRs for 12.0
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
PHP
...