I'm in need of some help!
I'm working on cleaning up uses of deprecated API usages and when I do
this, there are impacts on the public API because an exception that was
previously being thrown is now no longer.
For example, in
*ide/image/src/org/netbeans/modules/image/ImageDataObject.java* there
+1 (binding)
- Verified signature and SHA512 of sourde
- Built using OpenJDK Runtime Environment (Zulu 8.42.0.23-CA-macosx) (build
1.8.0_232-b18)
- Tested Java EE: Activated, added Payara Server, opened project
- NOTICE and LICENSE look good
Thanks!
Josh Juneau
juneau...@gmail.com
+1 (binding)
- Verified signature of source
- Checked SHA512 of source
- build Apache Netbeans 12.1 from Source with OpenJDK 11.0.8
- Tested opening an Angular project and verified, that typescript
editing works
- LICENSE and NOTICE file for source and binary releases look sane
(netbeans)
-
I think that your conclusions are reasonable.
I've built your test project, that confirms the startup delay hypothesis.
However performances must be evaluated on specific test cases :
building a 10 *.java program is different from building CXF (maven) or
derby (ant).
Maybe that also the goals
Hi all,
Clearly JDK 8 works for building NetBeans.
However, we also have this flag:
-Dpermit.jdk9.builds=true
For which JDKs can that be used and what do we need to do to avoid needing
that.
Here I get the impression that either JDK 8 or 11 is needed:
+1 (binding)
Build succeeded.
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (Zulu 8.46.0.19-CA-macosx) (build 1.8.0_252-b14)
OpenJDK 64-Bit Server VM (Zulu 8.46.0.19-CA-macosx) (build 25.252-b14,
mixed mode)
I then did my personal three most important scenarios:
1. Ran on the above
+1 (binding)
SHA512 is OK.
Builds OK with JDK8[1]:
$ JAVA_HOME=~/bin/jdk-8/ ant build
Executes OK with GraalVM 20.2:
$ JAVA_HOME=~/bin/graalvm-ce-java8-20.2.0/ ant tryme
I can open Maven project and debug it - including execution of a JavaScript
file. I can open a JavaScript file and debug it
