Re: Maven Daemon
On 27.10.20 16:27, Jaroslav Tulach wrote: po 26. 10. 2020 v 9:43 odesílatel Alessandro napsal: Hi all, I remember some time ago a discussion on improving Maven projects build speed in NetBeans. Stumbled upon this yesterday: https://github.com/mvndaemon/mvnd . It tries to port to Maven the same concept behind the Gradle daemon. Could an integration with the above daemon be worth pursuing to improve Maven build speed? Yes, very likely it could. Noted in https://issues.apache.org/jira/browse/NETBEANS-4746 - no we just need one thing: somebody to do it ;-) -jt quickly hacked something together to try it out (ignore the failed builds please, overlooked a non-jdk8 method call) https://github.com/apache/netbeans/pull/3210 having a warmed up JVM in the background feels a bit faster for sure. -michael - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
NetBEans 12.5 not happy running on JDK 11 with Gradle projects using JDK 17
I’m using NetBeans 12.5 running with JDK 11 on macOS 11.6
My project is configured in the build script to use the JDK 17 toolchain.
The NetBeans project properties have:
Sources -> Source/Binary format: 17
Build -> Compile -> Java Platform: JDK 17
The Navigator view is stuck at “Please wait…” for every file in the project.
Various newer constructs,. like:
if (x instance of Region r) {
r.blah();
}
are not parsed properly - The "Action Items” view shows various parsing errors
like:
')’ expected
‘;’ expected
‘not a statement
cannot find symbol symbol: variable r location: my.fully.qualified.Thing
I do have nb-javac installed because I have to work any many projects that are
stuck on Java 8.
If I change NB to run with JDK 17 (Zulu build with JavaFX):
The parsing issues go away. But there are still a few issues...
NB reported:
An error occurred during parsing of
‘javafx.controls/javafx/scene/control/SplitPane.java in
/Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home/lib/src.zip’.
Please report a bug against java/source and attach dump file
‘/Users/scott/Library/Application
Support/NetBeans/12.5/var/log/SplitPane_3.dump’
(tried to report this but couldn’t get Jira to attach the dump file.)
NB 12.5 fails to properly load some Gradle projects when it is running on JDK
17.
Even though the projects will build and run fine from within NetBeans it seems
the Gradle APIs that initially load the project are using Gradle 7.0 but I have
Gradle 7.2 set for what to use with the projects.
At least one project reports:
- Could not run build action using connection to Gradle installation ‘'
- Supplied javaHome must be a valid directory. You supplied:
/Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home
I have no idea where it is getting that path. It may be the default for Oracle
Java 17 on macOS, but it isn’t where my Java 17 is. My path (and this is the
path returned by the '/usr/libexec/javahome’ tool) is
/Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home
Scott
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: travis build unstable
Dne 04. 10. 21 v 15:20 Eric Barboni napsal(a): But now the sub job "Test Java modules with nb-javac on Java 8" fail with the following on regular basis on several PR. "hide-logs.sh ant $OPTS -f java/gradle.java test" exited with 1. In several of my PRs the Gradle's JavaExecToken* test is failing. Will fix as soon as I finish my current task. -S. - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread
On 04.10.21 15:59, Neil C Smith wrote:
On Mon, 4 Oct 2021 at 13:31, Michael Bien wrote:
On 04.10.21 12:38, Neil C Smith wrote:
On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote:
My proposal would be that 12.6 is the last release of Apache NetBeans
that supports building on JDK 8, ...
Also, I realise the other thing that needs to be considered there if
we're going to do this .. 12.6 is the first release to drop all uses
of JDK 8 for release builds, etc.? We should probably make sure we're
ready for this on the infrastructure side while we can still fall back
to JDK 8 in an emergency?!
it has to be tested on 8, otherwise it will become incompatible fast. My
understanding was that the minimum build JDK would be bumped to 11, so
that selected 11-only modules can be built, but the requirement to run
on 8 is *still* there.
I'm not sure anyone is saying otherwise right now? (at least for the
modules that aren't upgraded to 11-only over time).
ok, nevermind then, i just misunderstood - sorry.
Whether those parts can be tested to the same extent as now is another
question. We can't just keep loading on infrastructure. There will
need to be consideration of what needs testing where, and how.
yep. The php cluster uses up almost 2h on two nodes per PR push. Most of
the rest does not look so bad in comparison. Taking a look at the tests
or making php a conditional build in the workflow (e.g via PR labels*
or slash commands) would have the potential for big speedups.
* e.g: if: ${{ github.event.label.name == 'php' }} might work
regards,
michael
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Looking for a portable version
Good day. Help me pls find portable version of the netbeans. Thanks.
Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread
On Mon, 4 Oct 2021 at 13:31, Michael Bien wrote: > On 04.10.21 12:38, Neil C Smith wrote: > > On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote: > >> My proposal would be that 12.6 is the last release of Apache NetBeans > >> that supports building on JDK 8, ... > > Also, I realise the other thing that needs to be considered there if > > we're going to do this .. 12.6 is the first release to drop all uses > > of JDK 8 for release builds, etc.? We should probably make sure we're > > ready for this on the infrastructure side while we can still fall back > > to JDK 8 in an emergency?! > > it has to be tested on 8, otherwise it will become incompatible fast. My > understanding was that the minimum build JDK would be bumped to 11, so > that selected 11-only modules can be built, but the requirement to run > on 8 is *still* there. I'm not sure anyone is saying otherwise right now? (at least for the modules that aren't upgraded to 11-only over time). Whether those parts can be tested to the same extent as now is another question. We can't just keep loading on infrastructure. There will need to be consideration of what needs testing where, and how. The point above is that if we're proposing to drop support for building on JDK 8 with 13(.0) then we should make sure we're using JDK 11 in 12.6 for all convenience binaries, etc. so that we're sure we're ready for it. I'd also point out that ASF releases sources. More people are voting based on building those sources with JDK 11 than JDK 8 already. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
travis build unstable
Hi, Some fixes last week make travis happy with groovy test failure. But now the sub job "Test Java modules with nb-javac on Java 8" fail with the following on regular basis on several PR. "hide-logs.sh ant $OPTS -f java/gradle.java test" exited with 1. Would be nice to identify and fix. Best Regards Eric - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: [VOTE] Release Apache Netbeans Standalone Java Hints Tool 12.5 [vote candidate 1]
+1 (binding)
Best Regards
Eric
-Message d'origine-
De : Matthias Bläsing
Envoyé : dimanche 3 octobre 2021 21:46
À : dev@netbeans.apache.org
Objet : Re: [VOTE] Release Apache Netbeans Standalone Java Hints Tool 12.5
[vote candidate 1]
+1 (binding)
- checked Signatures and SHA512 sums
- eyeballed LICENSE and NOTICE files, look sane in source and binary case
- build from source (would have been helpful if it would be clearly spelled
out, that build has to happen with JDK-8 and JDK-11 referenced, building with
JDK-11 alone failed hard)
Am Sonntag, dem 03.10.2021 um 11:13 +0200 schrieb Jan Lahoda:
> Dear all,
>
> I'd like to release the standalone Java Hints tool ("jackpot") based
> on Apache NetBeans 12.5.
>
> The release is here:
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-jackpot/netbe
> ans-jackpot-12.5-vc1/apache-netbeans-jackpot-12.5.zip
>
> Signature file:
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-jackpot/netbe
> ans-jackpot-12.5-vc1/apache-netbeans-jackpot-12.5.zip.asc
>
> SHA512:
> 1ff544f9c24f79e2835c43303d826b6e1fcee700fc14772141adf9302a8a74299ec0c3
> 3a29476964323a637572b62619f21453fa6ffcdcee34aac4440103362d
> ./apache-netbeans-jackpot-12.5.zip
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
> Apache NetBeans Jackpot 3.0 Git Repo tag:
> https://github.com/apache/netbeans-jackpot30/releases/tag/netbeans-jac
> kpot-12.5-vc1
>
> Convenience binaries:
> -built standalone tool:
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-jackpot/netbe
> ans-jackpot-12.5-vc1/apache-netbeans-jackpot-12.5-bin.zip
>
> Its signature file:
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-jackpot/netbe
> ans-jackpot-12.5-vc1/apache-netbeans-jackpot-12.5-bin.zip.asc
>
> and its SHA512:
> 4905d2c044cd0251854046d042586ffb7ea092d09a495a8b605a640e9c4f45d45b7a60
> 026af4a6ef9b26ffe054d676d8768d106d5e62b119ad9f9546f56c9551
> ./apache-netbeans-jackpot-12.5-bin.zip
>
> -there is also a plugin staging Maven repository here:
> https://repository.apache.org/content/repositories/orgapachenetbeans-1
> 091/
>
> This vote is going to be open at least 72 hours, please vote with +1,
> 0, and -1 as usual.
>
> Thanks for any feedback!
>
> Jan
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
UTF-8
its probably known but just in case it fell under the radar: JDK 18 makes UTF-8 default, but the flag -Dfile.encoding=COMPAT can be used to force the legacy behavior. 17+ has a new "native.encoding" property which can be used to figure out what the platform encoding is (since Charset.defaultCharset() is going to return UTF-8), if there is a need for that. article on JEP 400: https://inside.java/2021/10/04/the-default-charset-jep400/ best regards, michael - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread
On 04.10.21 12:38, Neil C Smith wrote: On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote: My proposal would be that 12.6 is the last release of Apache NetBeans that supports building on JDK 8, ... Also, I realise the other thing that needs to be considered there if we're going to do this .. 12.6 is the first release to drop all uses of JDK 8 for release builds, etc.? We should probably make sure we're ready for this on the infrastructure side while we can still fall back to JDK 8 in an emergency?! it has to be tested on 8, otherwise it will become incompatible fast. My understanding was that the minimum build JDK would be bumped to 11, so that selected 11-only modules can be built, but the requirement to run on 8 is *still* there. it might be easier to invert the whole situation and keep building with 8, but only build/test the selected 11-only modules on 11+ nodes, until NB is *actually* able to drop support for 8. -michael - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread
On Fri, 1 Oct 2021 at 10:08, Neil C Smith wrote: > My proposal would be that 12.6 is the last release of Apache NetBeans > that supports building on JDK 8, ... Also, I realise the other thing that needs to be considered there if we're going to do this .. 12.6 is the first release to drop all uses of JDK 8 for release builds, etc.? We should probably make sure we're ready for this on the infrastructure side while we can still fall back to JDK 8 in an emergency?! Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
