Re: felix bundles
I'm back to experimenting with bundles to run on Felix and ran into this message ERROR: Bundle yrs.contractor.LedgerReportsBundle [88] Error starting atomos:boot:file:///sata2/modules/felix/LedgerReportsBundle-1.0.0 .jar (org.osgi.framework.BundleException: Unable to resolve yrs.contractor.LedgerReportsBundle [88](R 88.0): missing requirement [yrs. contractor.LedgerReportsBundle [88](R 88.0)] osgi.ee; (osgi.ee=UNKNOWN) Unresolved requirements: [[yrs.contractor.LedgerReportsBundle [88](R 88.0)] osgi.ee; (osgi.ee=UNKNOWN)]) org.osgi.framework.BundleException: Unable to resolve yrs.contractor.LedgerReportsBundle [88](R 88.0): missing requirement [yrs.contra ctor.LedgerReportsBundle [88](R 88.0)] osgi.ee; (osgi.ee=UNKNOWN) Unresolved requirements: [[yrs.contractor.LedgerReportsBundle [88](R 88.0)] osgi.ee; (osgi.ee=UNKNOWN)] at org.apache.felix.framework@7.0.0 /org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4398) at org.apache.felix.framework@7.0.0 /org.apache.felix.framework.Felix.startBundle(Felix.java:2308) at org.apache.felix.framework@7.0.0 /org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1566) at org.apache.felix.framework@7.0.0 /org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308) at java.base/java.lang.Thread.run(Thread.java:831) Attempting to find out what is producing the message I looked in the manifest Netbeans (12.3) is producing. Some Googling I found a message regarding eclipse from 2 years ago that indicated the bnd tools are too old (in 2019!) The offending entry is apparently the Require-Capability: osgi.ee entry in the manifest. Unfortunately, I can't find a way to fix it via Netbeans. Manifest-Version: 1.0 Bnd-LastModified: 1620784684373 Build-Jdk: 16.0.1 Built-By: chuck Bundle-Activator: yrs.contractor.ledgerreports.Activator Bundle-ManifestVersion: 2 Bundle-Name: LedgerReportsBundle OSGi Bundle Bundle-SymbolicName: yrs.contractor.LedgerReportsBundle Bundle-Version: 1.0.0 Created-By: Apache Maven Bundle Plugin Export-Package: yrs.contractor.ledgerreports;uses:="org.osgi.framework ";version="1.0.0" Import-Package: com.yakridge.jfxbase;version="[3.0,4)",com.yakridge.jf xbase.interfaces;version="[3.0,4)",javafx.scene,javafx.scene.control, javafx.scene.layout,org.osgi.framework;version="[1.8,2)" Require-Capability: osgi.ee;filter:="(osgi.ee=UNKNOWN)" Tool: Bnd-3.5.0.201709291849 And I noticed, creating a new OSGi Bundle project uses VERY old versions in the POM file. Thanks to anybody who knows a work-around until Netbeans can produce a Manifest without the offending entry.
Re: netbeans 12.3 doesn't support gradle 7.0.1? (keeps trying to use 6.7 for something)
Well, more properly NetBeans 12.3 bundles Gradle 6.7 tooling API which does not support Java 16. Actually NetBeans 12.3 does not officially supports Java 16. Though you do not need to worry that much. NetBeans 12.4 will support Java 16, including Gradle 7.x The 12.4-rc3 is in the pipeline, 12.4-rc2 is looking good, so probably won't have to wait for the final too long! On 5/11/21 6:33 PM, Wiegley, Jeffrey wrote: I’m trying to migrate to Java 16 and it seems to need gradle >=7.0 (A simple Hello World with gradle 6.7 throws an exception: java.lang.IllegalArgumentException: Unsupported class file major version 60, So apparently gradle 6.7 can’t handle Java 16) But if I change the Tools->Options->Gradle to 7.0.1 it seems to compile but doesn’t allow me to run. The “Notifications tab” has a warning: Cannot load: C:\...\gradleproject6 Priority LOW Category: Warning Unsupported class file major version 60 Bug! Exception in phase ‘semantic analysis’ in source unit ‘_BUildScript_’ Unsupported class file major version 60 Could not open cp_init generic class cache for initialization script ‘C:\Program Files\Netbeans-12.3\netbeans\extide\modules\gradle\nb-tooling.gradle’ (C:\...\.gradle\cache\6.7\scripts\775509g0wn2dvwyx898pf3241). Could not open cp_init generic class cache for initialization script ‘C:\Program Files\Netbeans-12.3\netbeans\extide\modules\gradle\nb-tooling.gradle’ (C:\...\.gradle\cache\6.7\scripts\775509g0wn2dvwyx898pf3241). Could not run build action using connection to Gradle installation ‘C:\...\.gradle\wrapper\dists\gradle-6.7-bin\efvqh8uyq79v2n7crncuhu9sv\gradle-6.7’. I’m guessing this is because Netbeans 12.3 was released before Java 16 and doesn’t support Java 16. Now that Java 16 is official is there a way to fix this problem? Thanks, Jeff Wiegley
netbeans 12.3 doesn't support gradle 7.0.1? (keeps trying to use 6.7 for something)
I'm trying to migrate to Java 16 and it seems to need gradle >=7.0 (A simple Hello World with gradle 6.7 throws an exception: java.lang.IllegalArgumentException: Unsupported class file major version 60, So apparently gradle 6.7 can't handle Java 16) But if I change the Tools->Options->Gradle to 7.0.1 it seems to compile but doesn't allow me to run. The "Notifications tab" has a warning: Cannot load: C:\...\gradleproject6 Priority LOW Category: Warning Unsupported class file major version 60 Bug! Exception in phase 'semantic analysis' in source unit '_BUildScript_' Unsupported class file major version 60 Could not open cp_init generic class cache for initialization script 'C:\Program Files\Netbeans-12.3\netbeans\extide\modules\gradle\nb-tooling.gradle' (C:\...\.gradle\cache\6.7\scripts\775509g0wn2dvwyx898pf3241). Could not open cp_init generic class cache for initialization script 'C:\Program Files\Netbeans-12.3\netbeans\extide\modules\gradle\nb-tooling.gradle' (C:\...\.gradle\cache\6.7\scripts\775509g0wn2dvwyx898pf3241). Could not run build action using connection to Gradle installation 'C:\...\.gradle\wrapper\dists\gradle-6.7-bin\efvqh8uyq79v2n7crncuhu9sv\gradle-6.7'. I'm guessing this is because Netbeans 12.3 was released before Java 16 and doesn't support Java 16. Now that Java 16 is official is there a way to fix this problem? Thanks, Jeff Wiegley
Re: Re: NetBeans 8 app flickering/uncontrolled window movement on Alienware Dell - anyone seen this ?
Possible solution: Add -J-Dsun.java2d.noddraw=true to startup JVM arguments. We did try to run Nb8.2 out-of-the-box on the Alienware and it did not show the flickering/window-dropping as with the RCP app. Checking the netbeans.conf we did see the -J-Dsun.java2d.noddraw=true which the RCP did not have. Googling the argument did show it had some connection to Windows/graphic-cards/Swing. Adding -J-Dsun.java2d.noddraw=true to the JVM args of for RCP did for now over 48 hrs keep it from doing the wicket flickering We have taken it out of the netbeans.conf to see if Nb starts going ballistic (which would be the proof of the pudding) but that has not happened yet. We will see maybe this is a red Herring Just wanted to keep you updated thanx for the interest in this question. Really appreciate the feedback given. Bernd On Sat, May 8, 2021 at 5:51 PM bruehlicke wrote: > All Swing. > > On Sat, May 8, 2021 at 11:33 AM Eric Bresie wrote: > >> Wanted to confirm...is this Swing or JFX? If jfx that was deprecated >> along the line. >> >> Eric Bresie >> ebre...@gmail.com >> >> On May 7, 2021 at 11:35:17 AM CDT, bruehlicke >> wrote: >> I was able to capture the behavior on video ... attached. Currently it >> only happens on a m15r2 Alienware. >> >> >> >> On Fri, May 7, 2021 at 9:41 AM Admin @ Goodun >> wrote: >> >>> On Fri, 2021-05-07 at 07:26 -0500, bruehlicke wrote: >>> > Bummer, still happens with jdk 11. It is the entire outer window >>> > which jumps and leaves droppings/copies of itself when fx moving >>> > mouse accross I start wondering if there is a problem with the >>> > laptop. On the other hand it only happens with the NetBeans RPC app. >>> > Regardless if using Nvidea card or Intels integrated. >>> >>> I'm getting something that seems to me similar, but with the new >>> Android Studio release (4.2.0) under Linux (Fedora 33). >>> >>> What I'm seeing is that the entire outer (IDE) window flashes with all >>> mouseover actions. More than that, popup boxes of many (but not all) >>> types take up the entire outer window even though they only have the >>> normal, very small, content. >>> >>> I'm using OpenJDK 11. I tried changing my JAVA_HOME setting to >>> explicitly reference the JDK rather than the generic link, but both >>> suffer from the same thing. >>> >>> D'you think it's related? If it is, does it help? :-( >>> >>> Mark >>> >>> > Will try jdk17 if possible mysterious >>> > >>> > On Thu, May 6, 2021, 14:01 bruehlicke wrote: >>> > > Laszlo,, you are a hero ! I downloaded the OpenJDK 11 and just >>> > > copied the entire folder into my NetBeans 8.2 RCP app (build on >>> > > jdk8) and renamed the jkd11 folder to "jre" - Voila ! I just >>> > > love Java, it surprises me even again and again even after >>> > > coding for 2 decades with it. Of course, lots of testing needs to >>> > > be done but so far it looks like a work-around. We will have the >>> > > app running all day tomorrow on jdk11 to see if it "creeps back to >>> > > the flicker madness". >>> > > >>> > > Of course the biggest thanks is to all the people involved making >>> > > jdk11 (and later versions) and keeping it compatible and allowing >>> > > normal mortals like me to stay "clueless" - as Jaroslav so nicely >>> > > puts it - about all the underlying plumbing which was changed. >>> > > >>> > > Thanks ! >>> > > Bernd >>> > > >>> > > On Thu, May 6, 2021 at 10:35 AM bruehlicke >>> > > wrote: >>> > > > Ahh, ok good point ! I will try running NetBeans with jdk 11 >>> > > > (OpenJdk) on the Alienware and see how it goes. Thank you for >>> > > > your interest and suggestion. >>> > > > >>> > > > Bests >>> > > > Bernd >>> > > > >>> > > > On Thu, May 6, 2021 at 10:24 AM Laszlo Kishalmi < >>> > > > laszlo.kisha...@gmail.com> wrote: >>> > > > > I'd put my bet on the JDK AWT VRAM handling, so when I >>> > > > > suggested upgrade JDK, I meant upgrading it to a more recent >>> > > > > version than 1.8. I'd Try JDK 11 first, if that's still do not >>> > > > > work I'd test more recent ones... >>> > > > > On 5/6/21 8:02 AM, Geertjan Wielenga wrote: >>> > > > > >>> > > > > > Maybe Swing-specific, so try reproduce with another Swing app >>> > > > > > or create a new small Swing app yourself to reproduce the >>> > > > > > problem. >>> > > > > > >>> > > > > > Gj >>> > > > > > >>> > > > > > On Thu, 6 May 2021 at 16:55, bruehlicke >>> > > > > > wrote: >>> > > > > > >>> > > > > > > Thanx. Tried 1.8u202 (latest I can use without commercial >>> > > > > > > license) and it happened as well after a while. Hmm ... >>> > > > > > > currently only on Alienware laptop. ... wicket. Anyhow >>> > > > > > > here running NetBeans on a Gaming laptop having trouble ? >>> > > > > > > It looks like a generic problem and hence just running >>> > > > > > > NetBeans should cause the same issue. >>> > > > > > > >>> > > > > > > Anyhow, thank you for your suggestion >>> > > > > > > Bernd >>> > > > > > > >>> > > > > > > On Wed, May 5,
