Tanks for the info. I fixed it the NBM maven plugin the same way. Now it
works there as well.
On Sat, Jan 15, 2022 at 5:19 AM Jaroslav Tulach
wrote:
> FYI: https://github.com/apache/netbeans/commit/1b96b56 & co.
>
> It gets interpreted by the NetBeans runtime system.
> -jt
>
>
> čt 13. 1. 2022
FYI: https://github.com/apache/netbeans/commit/1b96b56 & co.
It gets interpreted by the NetBeans runtime system.
-jt
čt 13. 1. 2022 v 21:30 odesílatel Jean-Marc Borer
napsal:
>
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
>
> But still, it is a very special
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:
>
>
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
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
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
>
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.*,
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
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
>
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]
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
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
12 matches
Mail list logo
