Netbeans 22 & gradle: anyway to use Gradle's source/target compatibility?
Is there any way to have NB use source/target compatibility declared in build.gradle to select a 'matching' (already configured in NB) java platform (w/o ? So as to avoid having NB hammer in netbeans.hint.jdkPlatform= into gradle.properties (which , for us, is under SCCS). (Seems silly or petty, but 'we' strive to have build.gradle and related artifacts, devoid of any sort of IDE-isms) Alternatively, maybe some .gitignorable file could track this bread crumb in the projectDir/.gradle or projectDir/.gradle/nb-cache or something like that? TIA, -Fred
NB 21, GIT & Linux: duplicate password entries in keyring?
Long time NB user on linux. Notice recently that in my linux keyring, had duplicate entries created for NB/GIT credentials, when I do authenticated GIT activities from Netbeans 21. Yes, I use the 'save password' feature on NB/GIT operations. The entries seem identical, except: one entry has no password, the other one has a password. I don't know what criteria NB uses to select the key-ring entry to use, but it seems to 'like' to select the one w/o a password, inevitably causing an auth failure. Has anyone seen this? Have a work around for this? Yes, purging the bogus/empty entry, is a bit of work around. It is only when NB creates the keyring entry, do the dupes appear. Another thought/note: I have 90day PWD rotation, which hit last week. I purge my keyring and start over after a PWD rotation. Prior to the last PWD rotation, I was on NB20 during a rotation; NB20 didn't seem to have this issue. AND/OR, I'd be content if NB would delegate to .netrc when doing GIT/JGIT operations, is that an option? TIA! - Env stuff, if relevant: Fedora 38, all latest updates, Running either GNOME or xfce -- happens on both. Product Version: Apache NetBeans IDE 21 Java: 17.0.10; OpenJDK 64-Bit Server VM 17.0.10+7 Runtime: OpenJDK Runtime Environment 17.0.10+7 System: Linux version 6.8.7-100.fc38.x86_64 running on amd64; UTF-8; en_US (nb)
Re: NetBeans release notes?
an interesting surprise I don't know if this is the official release notes, but this has some info on it: https://github.com/apache/netbeans/releases/tag/16 On Wed, Dec 7, 2022 at 3:00 PM Thad Humphries wrote: > I see that NetBeans 16 is out. I only started using NetBeans a few weeks > ago. Are there release notes somewhere online so I can evaluate if I want > to upgrade at this time, and what obstacles and/or bugs I might expect? > > -- > "Hell hath no limits, nor is circumscrib'd In one self-place; but where we > are is hell, And where hell is, there must we ever be" --Christopher > Marlowe, *Doctor Faustus* (v. 111-13) >
Project->Run Gradle->Tasks dialog 'missing'?
Hi, Been running NB 12.5Final (OpenJDK 16.0.1, Linux/Fedora) mostly works quite well. I use gradle almost 100% of the time. I used to have the ability to create a 'task' via RtClick on a project node and then select "Run Gradle" and then "Tasks..."That would popup a dialog and I can tinker with some custom gradle CLI. That would 'hold on to' those and I can select and re-run a task, etc etc etc. Not perfect but helpful. Anyways that dialog won't come up.No error in the IDE logs or other indicators of something wrong. Where did it go? (Current project is a gradle 7.2 project) FWIW: I just fired up NB 12.4 (same JDK, etc) and the same gradle build and that dialog comes up etc etc etc. Also FWIW: since older 12.4 would 'save' custom CLIs to gradle.properties, the newer 12.5 would see them and actually built the right click menu with the custom task; but dialog doesn't work, still. - Also, The older 8.2 gradle plugin had some smarts somehow with regards to tests and some simple conventions. It knew (well, made a good guess) how to map to a task based location of a file when you used the 'run test' (ctl-f6). So for example, for a ctl-f6 on/in a file located at: src/integrationTest/groovy/com/blah/someSpec.groovy It would (effectively) execute: ./gradlew integrationTest --tests com.blah.someSpec Of course the build.gradle would need a matching sourceSet and task of type Test, but that is pretty common/simple/convention oriented -- so it all just worked. That kinda feature would be great to add.
Re: Avoid cluttering gradle.properties
I agree with this! On Wed, Jun 2, 2021 at 7:26 AM Thomas Kellerer wrote: > I am using NetBeans 12.4 with several gradle projects that use SpringBoot. > > When I configure the "Build Actions" in the NetBeans Properties to e.g. > include "--args='--spring.profiles.active=my_profile'" then NetBeans puts > this into the project's "gradle.properties" which would be committed to Git > so it would affect other members of the team. > > With Maven, NetBeans creates e.g. nbactions*.xml or nbconfiguration.xml > which can be included in .gitignore so that other team members are not > affected by my local configuration. > > Is there a way to customize the Gradle "Build Actions" in NetBeans in a > way that it doesn't touch the gradle.properties? > > Or do I have to remove those settings each time, before I commit changes > to the file? > > Regards > Thomas > > - > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
Re: Gradle - displaying dependency graph like Maven
Outside of netbeans, and just in gradle-space, there are a few plugins that assist with dep visualizaiton. There is also gradle build scans, which provide lots of good information about a build, including data on deps. On Mon, May 3, 2021 at 10:29 AM Laszlo Kishalmi wrote: > That's the best thing you can do now. There is no UI Graph > representation of dependencies implemented for Gradle. > > On 5/3/21 12:00 AM, Giles Winstanley wrote: > > `gradle dependencies` is a good starting place (I typically also use the > > -q option to remove the cruft). > > > > There's also, for example: > > `gradlew -q dependencies --configuration runtimeClasspath` > > which will give you depdencencies just a specific configuration. > > > > With regard to Netbeans integration, you can set this up as a saved task > > by right-clicking the build.gradle file in the project view, then > > defining the options (just omit the "gradle" or "gradlew" part at the > > beginning). Output will be to the standard output window. > > > > Hope that helps, > > Stan > > > > On 03/05/2021 07:16, Thomas Kellerer wrote: > >> When debugging problems with transitively included libraries in Maven, > I find the graph display of the POM extremely helpful. > >> > >> But I can't find anything similar when using a Gradle project. > >> > >> Am I missing something, or does this simply not exist? > >> > >> I am using NetBeans 12.3 > >> > >> Regards > >> Thomas > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > >> For additional commands, e-mail: users-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: users-unsubscr...@netbeans.apache.org > > For additional commands, e-mail: users-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: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
Gradle 7 support?
*Product Version:* Apache NetBeans IDE 12.3 *Java:* 14.0.2; OpenJDK 64-Bit Server VM 14.0.2+12 *Runtime:* OpenJDK Runtime Environment 14.0.2+12 *System:* Linux version 5.8.18-100.fc31.x86_64 running on amd64; UTF-8; en_US (nb) I am getting the following warning from NB: Reason: groovy.lang.MissingPropertyException: Could not get unknown property 'compileConfigurationName' for source set 'main' of type org.gradle.api.internal.tasks.DefaultSourceSet. groovy.lang.MissingPropertyException: Could not get unknown property 'compileConfigurationName' for source set 'main' of type org.gradle.api.internal.tasks.DefaultSourceSet. This happens after a project "clean and build".Build seems to 'work' and I haven't' noticed anything broken in NB, yet. Any suggestions? Gradle 7, supported in NB 12.3?I use 'prefer gradle wrapper' in NB.
Re: Thanks for v12.3
I switched over Yesterday too. So far, pretty good. Few or little differences than 12.2. Very heavy gradle user, also my NB runs under Open JDK 14 under Fedora 31; gradle projects are generally run with JDK8 or JDK 11. Thanks for all the hard work. On Thu, Mar 11, 2021 at 9:59 PM Malcolm Fitzgerald < malc...@notyourhomework.net> wrote: > Thanks to everyone who has worked so hard to bring version 12.3 to life. > > I'm running on Mac and it looks great. > > Editing actions are quick and responsive. In earlier versions the GUI > was slower, now it feels like the response to actions are immediate. > > I look forward to using it a lot more, > > Malcolm > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
Re: How to turn off formal parameter hints in Netbeans 12.2 editor?
OMG! Nailed it. Totally not where I was lookingsigh... Thanks!!! On Tue, Mar 2, 2021 at 10:47 AM Geertjan Wielenga < geertjan.wiele...@googlemail.com> wrote: > View | Show Inline Hint > > Gj > > On Tue, Mar 2, 2021 at 4:39 PM Fred Welland > wrote: > >> I did something or installed a plugin and now in my editor windows (for >> .java file) display hints for method calls that show the formal parameter >> names in smaller font, to the left of the actual parameter. >> >> I'd like to turn this off. >> >> I've rifled through various menus and settings to enable/disable this >> display, but really haven't come up with anything. >> >> Any suggestions? >> >> (NB 12.2 running under JDK 14, under Fedora 31) >> >>
How to turn off formal parameter hints in Netbeans 12.2 editor?
I did something or installed a plugin and now in my editor windows (for .java file) display hints for method calls that show the formal parameter names in smaller font, to the left of the actual parameter. I'd like to turn this off. I've rifled through various menus and settings to enable/disable this display, but really haven't come up with anything. Any suggestions? (NB 12.2 running under JDK 14, under Fedora 31)
Re: [POLL] Gradle Task Navigator with Favorite Task UI
I prefer the 2nd one! (Thanks for the great work!) On Mon, Dec 14, 2020 at 11:30 PM Laszlo Kishalmi wrote: > Well, I've created two UI implementation of displaying Favorite Task in > Gradle Navigator. > > The implementations: > > > https://issues.apache.org/jira/secure/attachment/13017035/GradleFavoritesCut.mp4 > > > https://issues.apache.org/jira/secure/attachment/13017110/GradleFavoritesCut2.mp4 > > > You can vote on your favorite implementation at: > > - Here in the mailing list. > > - Twitter: https://twitter.com/KishalmiLaszlo > > - Telegram: https://t.me/apache_netbeans > > The poll is open for 3 days. > > > - > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
Files tab not display gradle sub-project root folders
(NB and JDK versions data below) I have a gradle multi-subproject build. Two of the subs do not apply normal java-like plugins: one only does 'ear' the only applies 'base'. Normally, or in the past, I would be able to navigate and interact with files from these types of projects using Files tab. Currently, the project roots do not show up in Files window.Further, the root project's directory doesn't show up in Files tab either. Is there a way to enable this? Product Version: Apache NetBeans IDE DEV (Build dev-da730a6bc4fe09c621b0aa93bb8ea1e806c20c13) Java: 14.0.2; OpenJDK 64-Bit Server VM 14.0.2+12 Runtime: OpenJDK Runtime Environment 14.0.2+12 System: Linux version 5.8.13-100.fc31.x86_64 running on amd64; UTF-8; en_US (nb) User directory: /home/fwelland/.netbeans/dev Cache directory: /home/fwelland/.cache/netbeans/dev
Re: nightlies?
When I pulled; unzipped there were 2 exes in ../bin directory; along with the linux sh/bootstrapper... ...I presume they work... On Thu, Oct 1, 2020 at 3:37 PM Christoph Theis wrote: > Half offtopic: where would I find the nightly artifacts for Windows, if > they exist? > > > Christoph > > - > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
Re: nightlies?
Thanks -- haven't tried the snap one yet -- may give it a try. On Thu, Oct 1, 2020 at 12:19 PM Laszlo Kishalmi wrote: > Yes, that's how it works. If you happen to be on Linux you might use the > netbeans-dev Snap package as of: > > sudo snap install --edge --classic netbeans-dev > > Get a new dev build automatically every Thursday > > There are more Gradle fixes on the way, I hope 12.2 will be able to load > and parse the full JavaFX source code. > > On 10/1/20 4:50 AM, Fred Welland wrote: > > Hi Ya, > > > > 12.1 working OK for me...sigh well was. I am HUGE Gradle user & > > Lombok too!Saw 'noise' on this list about something busted related > > to gradle and lombok and then encountered it yesterday. Also > > thought I saw a note about it being addressed already in a nightly. > > > > So, for example, is this the approximate location to grab a nightly from: > > > > > https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux/84/artifact/nbbuild/NetBeans-dev-Netbeans/ > > > > Build 84 is just latest, could pull whatever, -- salient point > > ''artifact/nbbuild/NetBeans-dev-Netbeans" & grab the zip? > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
nightlies?
Hi Ya, 12.1 working OK for me...sigh well was. I am HUGE Gradle user & Lombok too!Saw 'noise' on this list about something busted related to gradle and lombok and then encountered it yesterday. Also thought I saw a note about it being addressed already in a nightly. So, for example, is this the approximate location to grab a nightly from: https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux/84/artifact/nbbuild/NetBeans-dev-Netbeans/ Build 84 is just latest, could pull whatever, -- salient point ''artifact/nbbuild/NetBeans-dev-Netbeans" & grab the zip?
Re: GRADLE: 'Web Pages' project node gone in NB 12.1?
You fixed it! Hehe. So thinking about how I'd get you the project; I just fired up 12.1 again.Still no "Web Pages" node. Interestingly, "Generated Sources" was gone -- but that isn't really important. I figured I'd rifle thru options and plugins one last time.I noticed Plugins->Installed->Java Web and EE was not activated.I activated that; and that really didn't change anything. Closed project; then shutdown 12.1; restarted 12.1 and then re-opened project -- BOOM -- 'Web Pages' is there.Sources [generated] is gone - but one SHIFT-F11 it was back. I can deal with that. NOTE: Project in question is a POC and a bit of an odd-duck: JSF using hollowed Bootable Wildfly 21beta. Sadly bootable WF is only in form of maven plugin -- so this project has a pom.xml too; only for making the hollowed WF jar -- all the heavy lifting is in gradle (including gradle exec calls to 'mvnw').I can still make it available to you if you'd like. On Thu, Sep 24, 2020 at 11:42 PM Laszlo Kishalmi wrote: > Well, actually I do need your setup or a sample project which does not > work for you. Just have the time check the web projects and found that the > Web Pages node is actually there. Even when creating an application from > the Wizard. > > The only issue I see with 12.1 (and before) that if you right click on the > web pages, then select JSP the web pages is not offered a root folder for > the JSP. > > That is fixed in the development builds. > > As of the gererated sources. Unfortunately Gradle generates their folder > regardless if it is being used or not. I have not find the time to hide > them when they are empty. Probably in 12.2 ... > On 9/24/20 12:19 PM, Fred Welland wrote: > > Oh ok. > > Lemme know if you need any more data about my setup. Also -- in 12.1 I > do see the generated sources project node -- although that doesn't apply > for this project (be nice to suppress when not needed). > > On Thu, Sep 24, 2020 at 2:18 PM Laszlo Kishalmi > wrote: > >> That's a good question. I'm afraid I have to debug what's happened with >> the Web Pages node. >> >> On 9/24/20 11:09 AM, Fred Welland wrote: >> > Kicking tires on NB12.1, I have a simple gradle build that applies >> > 'war' plugin. >> > >> > In NB 12.0; this pretty much works and has a nice 'Web Pages' node in >> > the project window: it lets me navigate src/main/webapp/. >> > >> > Load the same project in NB 12.1 and that node is gone. >> > >> > Is there a way to make it come back? Do I gotta re-enable something >> > in NB 12.1? >> > >> > NOTE: I let NB 12.1 copy over all my settings/plugins from my NB 12 >> > config. >> > >> > FWIW: running NB12 & 12.1 under JDK 14 -- that said this project is >> > a JDK 8 project so I use that in the compile/build step. Oh and >> > Gradle 6.6 (oh and running under fedora 31) -- geeze ok: >> > >> > to run NB 12.0/12.1: Java: 14.0.2; OpenJDK 64-Bit Server VM 14.0.2+12 >> > to build: openjdk version "1.8.0_265" >> >> - >> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org >> For additional commands, e-mail: users-h...@netbeans.apache.org >> >> For further information about the NetBeans mailing lists, visit: >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >> >>
Re: GRADLE: 'Web Pages' project node gone in NB 12.1?
Oh ok. Lemme know if you need any more data about my setup. Also -- in 12.1 I do see the generated sources project node -- although that doesn't apply for this project (be nice to suppress when not needed). On Thu, Sep 24, 2020 at 2:18 PM Laszlo Kishalmi wrote: > That's a good question. I'm afraid I have to debug what's happened with > the Web Pages node. > > On 9/24/20 11:09 AM, Fred Welland wrote: > > Kicking tires on NB12.1, I have a simple gradle build that applies > > 'war' plugin. > > > > In NB 12.0; this pretty much works and has a nice 'Web Pages' node in > > the project window: it lets me navigate src/main/webapp/. > > > > Load the same project in NB 12.1 and that node is gone. > > > > Is there a way to make it come back? Do I gotta re-enable something > > in NB 12.1? > > > > NOTE: I let NB 12.1 copy over all my settings/plugins from my NB 12 > > config. > > > > FWIW: running NB12 & 12.1 under JDK 14 -- that said this project is > > a JDK 8 project so I use that in the compile/build step. Oh and > > Gradle 6.6 (oh and running under fedora 31) -- geeze ok: > > > > to run NB 12.0/12.1: Java: 14.0.2; OpenJDK 64-Bit Server VM 14.0.2+12 > > to build: openjdk version "1.8.0_265" > > - > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org > For additional commands, e-mail: users-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
GRADLE: 'Web Pages' project node gone in NB 12.1?
Kicking tires on NB12.1, I have a simple gradle build that applies 'war' plugin. In NB 12.0; this pretty much works and has a nice 'Web Pages' node in the project window: it lets me navigate src/main/webapp/. Load the same project in NB 12.1 and that node is gone. Is there a way to make it come back? Do I gotta re-enable something in NB 12.1? NOTE: I let NB 12.1 copy over all my settings/plugins from my NB 12 config. FWIW: running NB12 & 12.1 under JDK 14 -- that said this project is a JDK 8 project so I use that in the compile/build step. Oh and Gradle 6.6 (oh and running under fedora 31) -- geeze ok: to run NB 12.0/12.1: Java: 14.0.2; OpenJDK 64-Bit Server VM 14.0.2+12 to build: openjdk version "1.8.0_265"
Re: NetBeans 12 Distribution URL Certificate
It's funny and a round about way on how I got to NB12 and JDK14. My remote situation is just easier if I RDC -- so my fedora workstation runs XRDP. To conserve bandwidth I generally run my rdc client (remmina on F31 laptop) in 16 bit color depth. Many/Most Java/Swing like programs; including NB 10,11,12; running under JDK > 8 would draw empty windows (running on my workstation in xrdp, but displaying on my laptop via remmina; also true in rare cases where I actually use Windows RDC client to my F31 workstation). Anyway, when NB 12 dropped a few weeks ago, I had thought I read somewhere that it would run under JDK 8 but recommended a newer JDK, I even thought there were words somewhere saying JDK14 is recommended. so... I fiddled with lots of JAVA_OPTs tweaking gui stuff (gtk, dpiaware, java2d, etc) -- nothing. Long story short, I happened to reconnect to my workstation but UPPED the color depth from 16 to 24bitsand then NB 12 (w/o java_opt tweaks) started to draw using JDK14 So does NB12 officially run under JDK8 -- no idea. That said, I did observe NB12 running seemingly fine under jdk8 -- but didn't really use that config as a daily driver once I got NB12 + JDK14 rolling ok.FWIW: I routinely run builds from NB12 -- all gradle -- using JDK 8 as a configured JDK platform -- I have a few JDK11 gradle builds too. HTH... On Tue, Jun 23, 2020 at 2:15 PM Jordan Conner wrote: > Thank you for the reply. I am not behind any http proxies. Interesting > point about the JDK version you use with NB 12. Does NB 12 support JDK 8? I > looked around but don’t see any information on that. Am I missing something > obvious? > > > > Thanks > > > > *From:* Fred Welland > *Sent:* Tuesday, June 23, 2020 1:49 PM > *To:* Jordan Conner > *Cc:* users@netbeans.apache.org > *Subject:* Re: NetBeans 12 Distribution URL Certificate > > > > Are you behind a DLP http proxy?I am and the DLP I am behind messes > with HTTPS traffic and certs. > > > > I've had to import a trusted cert at system level (also Fedora 31, but > running selinux and firewalld). > > > > A few java programs I've run had this problem; just had this with JMeter a > week or so ago. I used keytool to import my DLP cert and the issue went > away (JDK8). > > > > That said, I am running NB 12 under JDK 14, and don't recall this with > NB12; when I started using it a couple of weeks ago (and don't' recall > importing my DLP cert into my JDK14 install). > > > > HTH > > > > > > > > On Tue, Jun 23, 2020 at 1:15 PM Jordan Conner > wrote: > > Hello, > > > > Excited to try out NetBeans 12. I’ve downloaded the latest LTS release > this morning. > > > > When selecting the ‘Check for Updates’ under Plugins menu I am receiving > this error… > > > > > > *Unable to connect to the NetBeans Distribution because of > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target* > > > > The URL https://netbeans.apache.org/nb/updates/12.0/updates.xml.gz under > Settings for my “NetBeans Distribution” portal works fine in the browser. I > can download the .gz file no problem. > > > > The same cert issue occurs with the NetBeans Plugin Portal. > > > > > > My environment: > > Fedora 31 - SELinux disabled, stopped firewalld > > java version "1.8.0_45" > > > > > > The only thing I’ve tried, is importing *.apache.org .pem certificate > into cacerts. > > > > Is there a way to gather more information from the exception? I am behind > a company firewall, but I figured if the URL worked in the browser then I’d > be fine there. Also, checking for updates/plugins works fine in Netbeans > 10, and 11.2. > > > > Does anyone know what the issue may be? > > > > Thank you > > > > > > > > > >
Re: NetBeans 12 Distribution URL Certificate
Are you behind a DLP http proxy?I am and the DLP I am behind messes with HTTPS traffic and certs. I've had to import a trusted cert at system level (also Fedora 31, but running selinux and firewalld). A few java programs I've run had this problem; just had this with JMeter a week or so ago. I used keytool to import my DLP cert and the issue went away (JDK8). That said, I am running NB 12 under JDK 14, and don't recall this with NB12; when I started using it a couple of weeks ago (and don't' recall importing my DLP cert into my JDK14 install). HTH On Tue, Jun 23, 2020 at 1:15 PM Jordan Conner wrote: > Hello, > > > > Excited to try out NetBeans 12. I’ve downloaded the latest LTS release > this morning. > > > > When selecting the ‘Check for Updates’ under Plugins menu I am receiving > this error… > > > > > > *Unable to connect to the NetBeans Distribution because of > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target* > > > > The URL https://netbeans.apache.org/nb/updates/12.0/updates.xml.gz under > Settings for my “NetBeans Distribution” portal works fine in the browser. I > can download the .gz file no problem. > > > > The same cert issue occurs with the NetBeans Plugin Portal. > > > > > > My environment: > > Fedora 31 - SELinux disabled, stopped firewalld > > java version "1.8.0_45" > > > > > > The only thing I’ve tried, is importing *.apache.org .pem certificate > into cacerts. > > > > Is there a way to gather more information from the exception? I am behind > a company firewall, but I figured if the URL worked in the browser then I’d > be fine there. Also, checking for updates/plugins works fine in Netbeans > 10, and 11.2. > > > > Does anyone know what the issue may be? > > > > Thank you > > > > > > > > >
Re: NB 11.3 + Gradle 6x + integrationTest and Test File (ctlr-f6)
Thanks!
Just here: https://issues.apache.org/jira/projects/NETBEANS/issues ? I
have to make an account? (didn't see add issue button)
FWIW: Got a reasonable solution that ties me over for now: made a Task
and just hard coded a specific spec name to that. It mostly works; and
available right click menu; so speeds up repetitive work on a specific
spec. Note: the ${selectedClass} macro wouldn't expand for me. Having
that work, would have been like 3/4ths what I need. The other 1/4, and
this has probably been missing forever: comprehensive macro & ide
automation feature triggerable by hot-keys.
On Thu, Apr 30, 2020 at 8:04 PM Laszlo Kishalmi
wrote:
> I'd recommend to add an improvement request into JIRA. I do not think
> that it can be solved in 11.3, some cumbersome workaround could be
> overriding the test action.
>
> Unfortunately 12.0 is almost ready so most probably this can be released
> in August or some daily builds.
>
>
> On 4/30/20 11:54 AM, Fred Welland wrote:
> > The older G4NB plugin had smarts or something such that it looked at
> > pathing of where a test file was and adjusted the gradle invocation
> > accordingly.
> >
> > So for example, a Spock spec in:
> > src/test/groovy/com/blah/blah/SomeSpec.groovy
> >
> > would invoke gradle a bit like like:
> >
> > ./gradlew tests --tests com.blah.blah.SomeSpec
> >
> > And if the Spock spec was here:
> > src/integrationTest/groovy/com/blah/blah/OtherSpec.groovy
> >
> > would invoke gradle a bit like like:
> >
> > ./gradlew integrationTest --tests com.blah.blah.OtherSpec
> >
> > Basically, it seemed to do some simple matching of the path against
> > tasks in the build file and away it went.
> >
> > Can the 11.3, using builtin gradle support support this kind of
> > behavior? If so how?
> >
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
NB 11.3 + Gradle 6x + integrationTest and Test File (ctlr-f6)
The older G4NB plugin had smarts or something such that it looked at pathing of where a test file was and adjusted the gradle invocation accordingly. So for example, a Spock spec in: src/test/groovy/com/blah/blah/SomeSpec.groovy would invoke gradle a bit like like: ./gradlew tests --tests com.blah.blah.SomeSpec And if the Spock spec was here: src/integrationTest/groovy/com/blah/blah/OtherSpec.groovy would invoke gradle a bit like like: ./gradlew integrationTest --tests com.blah.blah.OtherSpec Basically, it seemed to do some simple matching of the path against tasks in the build file and away it went. Can the 11.3, using builtin gradle support support this kind of behavior? If so how?
Re: Gradle based project won't load. How to investigate it or see compiler output?
Not sure if this will helpI did point this out to this list a while back -- it didn't get traction. Comment applies to 11.3 - probably covers 12 too. It seems 11.3 using Gradle 6x tooling api for stuff including build file parsing/ingest. My inventory of gradle projects in 20+; some are old using like g3x. There are some gradle constructs used in older builds that are NOT compatible with G6. G6 wouldn't deal with it, and NB11.3 was even worse -- just really nothing useful to say about the project/build when it couldn't load it. I just got in habit of making sure G6x would at least tolerate my build files (via CLI) before trying to load in NB 11.3. (It would be great of NB could tolerate a wider set of G versions) On Wed, Apr 29, 2020 at 2:30 AM Emilian Bold wrote: > Hello, > > I have a Gradle based project that won't load in any version of > NetBeans, including the 12 beta. The notification shown says: > > > Compilation failed; see the compiler output for details. > > Execution failed for task: '' > > Execution failed for task: '' > > Could not run build action using Gradle installation ' wrapper dists/ folder>' > > How does one go about investigating this problem? > > For starters, I don't see anything in the output window or messages.log. > > Where is the compiler output with the details? > > A minor issue: the notification itself (being a Swing component) doesn't > allow you to copy-paste the error message. > > --emi >
Netbeans 11.3 and older gradle builds
So +1 for NB 11.3. This is the first NB using native gradle support where I think I can use this as a daily driver for much of my work (prior 11.3 the only working combo for me was NB10 + gradle plugin). That said, I work on lots of gradle projects with gradles as old as 3.4.x to as new as 6.2.2. There are some constructs in older 3.x builds that are simply not supported in gradle 6.x. These projects will not really load at all in NB 11.3 (FWIW: nb10 + plugin is ok with these). I exclusively use 'wrapper that comes with project'. I have played around Options->Java->Gradle->Execution->Gradle Distribution and use Standard Version and Custom. Neither of those seem to affect the loading of the project.I am guessing, since tooling API 6x is burned into NB11.3; that is what is used during project load only -- and thus will choke on earlier build files with some older constructs (no longer part of gradle 6.x). Any way to work around this? -Fred
[gradle/spock] Netbeans 11.2 run test greyed out
Expect: right click in source window on a groovy/spock spec file to support "Test File" as well and ctrl-f6 to work Result: right click option is greyed out -- and nothing happened when one uses ctrl-f6 Is this just a bug or is there some tweak or setting I can flip to get this to work? FWIW: This was also the case in 11. 1. Using NB 10, using the older gradle project plugin, this feature (and debug test) works really well. In NB 11.2, running a project level test operation works OK. FWIW, Some specifics: *Product Version:* Apache NetBeans IDE 11.2 *Java:* 1.8.0_232; OpenJDK 64-Bit Server VM 25.232-b09 *Runtime:* OpenJDK Runtime Environment 1.8.0_232-b09 *System:* Linux version 5.3.16-300.fc31.x86_64 running on amd64; UTF-8; en_US (nb)
Netbeans 11.1 + Gradle + Spock Unit Tests
Just started using NB 11.1 (OpenJDK 1.8 202). I am using the built in gradle project support on a project with some Spock unit specs. NB 11.1 loads the specs ok into editor window.Right clicking in the editor window brings up the context menu. There are some test related actions that could happen, like "Test File", "Debug File" and so on. "Test File" and "Debug File" are disabled. "Run Focused Test Method" (and the debug variant) are active, but do not seem to do anything. Are any of these supported? FWIW: I can open same project in NB 10.0 (same JDK). The NB install uses the gradle plugin (not built-in stuff). These context menu items work fine under NB10.0 + gradle plugin.
