Re: Did you notice that the Netbeans JavaDoc site is not properly generated

2022-01-13 Thread Jean-Marc Borer
Hi Geertjan, Unfortunately I know nothing about the website generation. Hopefully, Eric Barboni seems to have taken the point. It seems related to JDK 11. Cheers, JMB On Thu, Jan 13, 2022 at 9:37 AM Geertjan Wielenga wrote: > Will you investigate and propose a solution? I can too, but I know

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Jean-Marc Borer
True. Then the issue lies in the maven nbm plugin that doesn't understand the URL escaping. I tested by manually modifying the manifest to restore the old values. The warning message is gone. On Thu, Jan 13, 2022 at 7:04 PM Matthias Bläsing wrote: > Hi, > > Am Donnerstag, dem 13.01.2022 um

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Jean-Marc Borer
https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath But still, it is a very special case here since I have never seen URL such as "%24%7Bjava.home%7D%2F/lib/ext/jfxrt.jar". ${xxx} is a dynamic value that shall be replaced at runtime. I really wonder if the manifest gets

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Jean-Marc Borer
Reported in https://issues.apache.org/jira/browse/NETBEANSINFRA-262 And already fixed in master of https://github.com/apache/netbeans-mavenutils-nbm-maven-plugin On Thu, Jan 13, 2022 at 8:29 PM Jean-Marc Borer wrote: > >

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Geertjan Wielenga
Hmmm. That's strange. (And as an Azul employee, I'd like to share with you that we'd love to promote your usage of Zulu. :-) ) Gj On Thu, Jan 13, 2022 at 6:54 PM Jean-Marc Borer wrote: > Hello, > > When building my NB RCP application with Maven, I get: > > Could not resolve Class-Path item in

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Geertjan Wielenga
So what does {java.home} resolve to? Gj On Thu, Jan 13, 2022 at 7:08 PM Jean-Marc Borer wrote: > Sure. You can send me a private message. > > Back to the topic: I checked the sources and indeed the source Manifest of > this JavaFX lib wrapper module reads: > > Manifest-Version: 1.0 >

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Jean-Marc Borer
OK so I have the 12.1 sources and when building with JDK 8 the NBM gets generated and the manifest is: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.10.7 Created-By: 1.8.0_302-b08 (Azul Systems, Inc.) OpenIDE-Module-Public-Packages: javafx.animation.*, javafx.application .*, javafx.beans.*,

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Jean-Marc Borer
Sure. You can send me a private message. Back to the topic: I checked the sources and indeed the source Manifest of this JavaFX lib wrapper module reads: Manifest-Version: 1.0 OpenIDE-Module: org.netbeans.libs.javafx OpenIDE-Module-Package-Dependencies: javafx.application[Application]

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Jean-Marc Borer
I suppose it should resolve to the JRE lib, but as such, Maven classpath checker doesn't understand the encoded version. I am currently trying to reproduce by building NB from the sources and generating the NMBs. On Thu, Jan 13, 2022 at 6:10 PM Geertjan Wielenga wrote: > So what does

JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Jean-Marc Borer
Hello, When building my NB RCP application with Maven, I get: Could not resolve Class-Path item in org.netbeans.api:org-netbeans-libs-javafx:nbm-file:RELEASE124, path is:%24%7Bjava.home%7D/lib/ext/jfxrt.jar, skipping I checked the manifest of module org-netbeans-libs-javafx.jar And actually I

Re: JavaFX classpath warning when building NB RCP with Maven

2022-01-13 Thread Matthias Bläsing
Hi, Am Donnerstag, dem 13.01.2022 um 17:54 + schrieb Jean-Marc Borer: > When building my NB RCP application with Maven, I get: > > Could not resolve Class-Path item in > org.netbeans.api:org-netbeans-libs-javafx:nbm-file:RELEASE124, path > is:%24%7Bjava.home%7D/lib/ext/jfxrt.jar, skipping >

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

2022-01-13 Thread antonio
Hi all, Regarding the adoption of JDK 11 and the future stragety we want to follow, I have several questions: 1. Question I: "sun.awt/sun.swing" classes. We're using sun.awt and sun.swing classes in one "dlight" module we're receiving in the 4th/5th donation. This is because there is an

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

2022-01-13 Thread Brett Ryan
Unfortunately due to https://issues.apache.org/jira/browse/NETBEANS-6273 we still need to start NetBeans 12.3 and above on JDK 1.8 due to keyboard mapping issues. With 12.2 and lower this issue is not present. On Fri, 1 Oct 2021 at 16:28, Jaroslav Tulach wrote: > JDK17 is out and Geertjan told

Fwd: Did you notice that the Netbeans JavaDoc site is not properly generated

2022-01-13 Thread Jean-Marc Borer
Hello all, I was browsing through the documentation site looking for information. I noticed that many links to useful docs are simply not working. I opened a bug https://issues.apache.org/jira/browse/NETBEANS-6386, but I have to say this is particularly annoying and doesn't facilitated the

[VOTE] Release Apache NetBeans VSCode extension 12.6.301

2022-01-13 Thread Martin Balin
Dear community, let's update the Apache NetBeans Language Server extension on VSCode Marketplace with significantly improved version 12.6.301 https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/ The primary voting artifact is the source

Re: Did you notice that the Netbeans JavaDoc site is not properly generated

2022-01-13 Thread Geertjan Wielenga
Will you investigate and propose a solution? I can too, but I know as much about this as you, as anyone. Gj On Thu, Jan 13, 2022 at 9:36 AM Jean-Marc Borer wrote: > Hello all, > > I was browsing through the documentation site looking for information. I > noticed that many links to useful docs

Re: [VOTE] Release Apache NetBeans VSCode extension 12.6.301

2022-01-13 Thread Jaroslav Tulach
+1 (binding) Checked SHA signatures. Checked .asc signatures. Used the complementary binary successfully. I also built from the source with (slightly changed ant command) successfully: ```bash $ ant build -Dmetabuild.branch=release1263 -Dmetabuild.jsonurl=