Re: [VOTE] Release Apache NetBeans 17
[X] yes / +1 [ ] no / -1 (please justify -1) [ ] binding (member of PMC) My vote is based on [X] I have built and tested the source with OpenJDK 17.0.5 on Ubuntu 22.10 (required) [X] I have tested the binary zip with OpenJDK 17.0.5 on Ubuntu 22.10 [X] I have tested the DEB installer(s) with OpenJDK 17.0.5 on Ubuntu 22.10 [X] I have tested the Windows installer(s) with OpenJDK 11.0.7 on Windows 10 [ ] I have tested the Maven artefacts [ ] I have tested the VSCode extension Additional info (optional) - any specifics on what you've tested - NetBeans IDE logo in Windows installer appears as having low resolution Thanks everybody. Tom On 16. 02. 23 16:13, Neil C Smith wrote: This is our first voting candidate for the release of Apache NetBeans 17. Please follow the NEW voting template at the bottom of this email, and note all requirements below for validating sources and convenience binaries before voting. Apache NetBeans 17 constitutes all clusters in the Apache NetBeans Git repository, which together provide the NetBeans Platform (i.e., the underlying application framework), as well as all the modules that provide the Java SE, Java EE, PHP, JavaScript and Groovy features of Apache NetBeans. Build artefacts are available here : https://dist.apache.org/repos/dist/dev/netbeans/netbeans/17/ They were built by the Jenkins pipeline : https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release170/21/ NB. ignore the build showing as aborted - caused by cancelling push to nightlies. We are primarily voting on : https://dist.apache.org/repos/dist/dev/netbeans/netbeans/17/netbeans-17-source.zip SHA512 : 0a40d0ff3b736ee7b433fec5b5ad4468d5ab2afe68bd284daf3ed135776db773ac91c8f61ebefe6e5101ea16dc7a2407769345108546946f7a218d30416df794 KEYS file : https://downloads.apache.org/netbeans/KEYS Associated with the primary source item we have, generated with the pipeline mentioned above : -- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans/17/ Binaries associated with the source - netbeans-17-bin.zip as well as update content under the nbms folder. -- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/17/ An installer for macOS handcrafted using build resources on a PMC member's macOS machine. An installer for Windows signed by a PMC member using binaries created during the build process. Packages for Linux signed by a PMC member using binaries created with NBPackage during the build process. -- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/17.0/ The VSCode extension signed by a PMC member using binaries created during the build process. Maven Artefacts The Maven artefacts for Apache NetBeans 17 are ready on staging associated to this vote. https://repository.apache.org/content/repositories/orgapachenetbeans-1125/ The version is : RELEASE170 Voting requirements Before voting +1 you are required to download the signed source code package, compile it as provided, and test the resulting executable on your own platform, along with also verifying that the package meets the requirements of the ASF policy on releases - http://www.apache.org/legal/release-policy.html#management In particular, you should (at least) follow these steps. 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files (there are branding folders with the name *.jar). 3. Verify the cryptographic signatures, the NOTICE and LICENSE file 4. Build it using the README provided by the artefact. 5. Look in nbbuild/netbeans for the NetBeans installation created by the build process and try running it. In addition to checking the sources, you may check the associated convenience binary zip, installers, nbms and maven staging at the links above. You are not expected to check every convenience binary. As well as checking any artefact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source being voted on is sufficient to build the relevant binary. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. (Please justify -1) Please mark your vote as binding only if you're an Apache NetBeans PMC member to help with voting admin. Only respond if you are going to vote - this is NOT a discussion thread. Apache NetBeans 17 will be released if and when this vote passes. --- Voting template Please copy and paste the answer form below into your email. Fill the checkboxes as appropriate (eg. [X]). Replace , and as appropriate. -- Answer form [ ] yes / +1 [ ] no / -1 (please justify -1) [ ] binding (member of PMC) My vote is based on [ ] I have built and tested the source with on (required) [ ] I have tested the binary zip with on [ ] I have tested the
Re: [LAZY CONSENSUS] single vote thread for NetBeans 17
Hi, I have voted using the template, I think we should rephrase it somewhow. It's too verbose to clearly understand. Maybe next time we want to clarify what are mandatory actions (should I check signatures of the main thing being voted on? Any others?) and optional ones. A clear checklist would indeed help, something like this: [ ] Mandatory: Check that https://./netbeans.zip is well signed. 1. Download https://...KEYS. 2. Use "gpg --import KEYS" to import gpt keys. 3. Download https://netbeans.asc 4. Verify using "gpg --verify netbeans.asc netbeans.zip" [ ] Mandatory: Check that netbeans.zip compiles 1. Unzip netbeans.zip somewhere. 2. Run "ant" there. 3. Run "ant tryme" there. [ ] Optional: Build a Maven app to print "Hello, World!" to the console 1. You know how to do this. Or something like that. The easier we make this to understand for friday-night, very-tired, eyestrained voters the more the voters we're gonna have. Cheers, Antonio P.S.: I don't know how to test maven artifacts / vscode. Can take a look at the generated files, though. On 10/2/23 19:43, Neil C Smith wrote: Eric and I have put together a vote email template here - https://cwiki.apache.org/confluence/display/NETBEANS/Voting+template - 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: Junit5 @Nested
Hi Chris, On 16.02.23 11:22, Chris Luff wrote: I saw this PR[1] from some time ago but it looks to have been abandoned. Was there any other work on this or should I have a look at getting this working? I am not sure, but since it isn't working as intended I would guess that there wasn't any follow up after this closed PR from 2019. jira issue is also still open: https://issues.apache.org/jira/browse/NETBEANS-1744 From a surefire pov it looks to simply be a case of class scanning for the nested annotation and ensuring the inner class is inserted into the command? If you think you have a way of fixing it - sure! It makes sense to me at least :) best regards, michael Thoughts welcome. Chris [1]: https://github.com/apache/netbeans/pull/1069 - 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
Re: [VOTE] Release Apache NetBeans 17
[X] yes / +1 [ ] no / -1 (please justify -1) [ ] binding (member of PMC) My vote is based on [X] I have built and tested the source with OpenJDK Runtime Environment Corretto-11.0.17.8.1 on GNU/Linux 5.15.0 [X] I have tested the binary zip with OpenJDK Runtime Environment Corretto-11.0.17.8.1 on GNU/Linux 5.15.0 [ ] I have tested the installer(s) with on [ ] I have tested the Maven artefacts [ ] I have tested the VSCode extension Great job! Congratulations! Antonio On 16/2/23 16:13, Neil C Smith wrote: This is our first voting candidate for the release of Apache NetBeans 17. Please follow the NEW voting template at the bottom of this email, and note all requirements below for validating sources and convenience binaries before voting. Apache NetBeans 17 constitutes all clusters in the Apache NetBeans Git repository, which together provide the NetBeans Platform (i.e., the underlying application framework), as well as all the modules that provide the Java SE, Java EE, PHP, JavaScript and Groovy features of Apache NetBeans. Build artefacts are available here : https://dist.apache.org/repos/dist/dev/netbeans/netbeans/17/ They were built by the Jenkins pipeline : https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release170/21/ NB. ignore the build showing as aborted - caused by cancelling push to nightlies. We are primarily voting on : https://dist.apache.org/repos/dist/dev/netbeans/netbeans/17/netbeans-17-source.zip SHA512 : 0a40d0ff3b736ee7b433fec5b5ad4468d5ab2afe68bd284daf3ed135776db773ac91c8f61ebefe6e5101ea16dc7a2407769345108546946f7a218d30416df794 KEYS file : https://downloads.apache.org/netbeans/KEYS Associated with the primary source item we have, generated with the pipeline mentioned above : -- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans/17/ Binaries associated with the source - netbeans-17-bin.zip as well as update content under the nbms folder. -- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/17/ An installer for macOS handcrafted using build resources on a PMC member's macOS machine. An installer for Windows signed by a PMC member using binaries created during the build process. Packages for Linux signed by a PMC member using binaries created with NBPackage during the build process. -- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/17.0/ The VSCode extension signed by a PMC member using binaries created during the build process. Maven Artefacts The Maven artefacts for Apache NetBeans 17 are ready on staging associated to this vote. https://repository.apache.org/content/repositories/orgapachenetbeans-1125/ The version is : RELEASE170 Voting requirements Before voting +1 you are required to download the signed source code package, compile it as provided, and test the resulting executable on your own platform, along with also verifying that the package meets the requirements of the ASF policy on releases - http://www.apache.org/legal/release-policy.html#management In particular, you should (at least) follow these steps. 1. Download the artefact to be voted on and unzip it. 2. Check that the artefact does not contain any jar files (there are branding folders with the name *.jar). 3. Verify the cryptographic signatures, the NOTICE and LICENSE file 4. Build it using the README provided by the artefact. 5. Look in nbbuild/netbeans for the NetBeans installation created by the build process and try running it. In addition to checking the sources, you may check the associated convenience binary zip, installers, nbms and maven staging at the links above. You are not expected to check every convenience binary. As well as checking any artefact functions correctly, you should check that it has been correctly signed by a PMC member, and that the source being voted on is sufficient to build the relevant binary. This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as usual. (Please justify -1) Please mark your vote as binding only if you're an Apache NetBeans PMC member to help with voting admin. Only respond if you are going to vote - this is NOT a discussion thread. Apache NetBeans 17 will be released if and when this vote passes. --- Voting template Please copy and paste the answer form below into your email. Fill the checkboxes as appropriate (eg. [X]). Replace , and as appropriate. -- Answer form [ ] yes / +1 [ ] no / -1 (please justify -1) [ ] binding (member of PMC) My vote is based on [ ] I have built and tested the source with on (required) [ ] I have tested the binary zip with on [ ] I have tested the installer(s) with on [ ] I have tested the Maven artefacts [ ] I have tested the VSCode extension Additional info (optional) - any specifics on what you've
Re: [External] : No communication from plugin portal verifiers (do we need to drop plugin portal?)
Hi Matthias, first of all sorry for not reacting to your question sooner but I was busy lately so I didn't check the list and the direct message for some reason didn't end up in the Inbox too. :( Anyway, I can give the context here. :) About two months ago Mani (Cc:ed here) joined the team of plugin verifiers as a new volunteer and during the introductory call with him we talked about whether plugins should be signed. As per the Plugin Verification specification [1] the installation instructions only mention: 1.8 If validation warning about self-signed certificate is displayed, accept it by clicking Continue button. [1] https://synergy.netbeans.apache.org/#/title/verification_of_apache_netbeans_plugin/ It says nothing about not signed plugins but we came to the conclusion that if self-signed plugins are explicitly tolerated then not-signed one should not. However, if you and Neil think that the signature check should be excluded completely and NetBeans community supports it, let's remove it. And even more if the whole verification process is seen as useless then let's have an official community voting and then get rid of it! As an immediate fix I have changed my NoGo to Go for all your 3 plugins and hereby ask Carlos/Geertjan/Mani to do the same if they agree. Hope this helps, -Jirka Dne 16. 02. 23 v 19:46 Matthias Bläsing napsal(a): Hi again, this is getting ridiculous. There are zero replies here (apart from telling me things I already now) and no verifiers reacts. I'm currently thinking, that we need a different approach to the Plugin Portal, as there is zero communication. This is the place authors are pointed and here they don't get an anwser. There is still no statement why my plugins suddenly get rejected, although they were fine for multiple releases. Greetings Matthias Am Montag, dem 30.01.2023 um 19:03 +0100 schrieb Matthias Bläsing: Hi, I asked for reverification of three plugins. These plugins: - PlantUML-NB - LDIF Editor - LDAP Explorer are verified for NB 11.0/12.0 till NB 16 version. Nothing was changed on the plugins for 17 and now the plugins are not good enough anymore. So what is going on? They are rejected, because they are not signed, fine, but then why is that an issue? The signatures gain you nothing as there is no trust anchor, we don't distribute blocked author certificates and the download from plugin portal is protected by the checksums. This is bogus, so what changed and why was this not communicated? I assume, that I was not the only one suprised by this. What is more, I'd need to do a full release cycle without any code changes, without any benefit. Greetings Matthias PS: Jiří I added you to direct CC as I'm not sure how closely you monitor dev@ - 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://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!ACWV5N9M2RV99hQ!PcyUPMpXuAas86TyrZC0toy3VlmwB6aBFovbYVDr0XdF2x3OJ7Skt1rQE-bvnuO9TqMAAjLACQxXq1QFyU2_8NR8lyiSxg$ - 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: 17 blocker? — [apache/netbeans] no library found for namespace http://omnifaces.org/ui (Issue #4976)
On 2/16/23 09:01, Michael Bien wrote: > we should consider to put it on the release notes that Jakarta support > is in early stages and that the enterprise cluster in general is > currently WIP. > > the JDK8 commit validation tests issue delayed the big Jakarta PR so > much that there was basically no time left for proper stabilization of > the PR once it was merged. I think it was still right to merge it so > that there is at least some support, but we should do a bit "expectation > management". Good god. Are you saying that keeping JDK8 was at the cost of breaking EE support? That's completely unacceptable. We need to do as Papa Java says: "In my opinion, JDK8 must die... Stop the unholy contortions to coexist. Kill it. Nail its coffin closed. Do not look back." -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." - 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: Lets talk about JDK 8 (new year edition)
On 2/13/23 21:28, Laszlo Kishalmi wrote: > Java 8 is becoming a dead weight on this project. +1 > Help me understand, that those projects which are stuck on Java 8 for > whatever reason, why can't stuck on a specific NetBeans version as well? To me, that's the crux of the problem. If you need an old version of the JDK, run an old version of NetBeans. Don't try and hold back the current version. -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe." - 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: Launchers enhancement: extra clusters
On 17. 02. 23 11:17, Neil C Smith wrote: Definitely in favour of the command line parameter. But, does it absolutely need launcher changes to achieve it? Not achievable by parsing the command line argument in MainImpl like you're doing with the system property? The thing is that the --clusters (+netbeans_extra_clusters config option) is processed into "netbeans.dirs" system property by launcher(s). That property is read from many places, sadly and is public/documented (arch.xml) alghouth as "friend" category. The implementation could possibly read "--add-clusters" at the very start of the bootstrap, using custom code as we need (IMHO) to patch the combined value back as soon as possible so that even CLIHandlers observe the correct value. No existing code is really prepared for this value to be mutable. That's partially why I/Dusan considered the quickfix just temporary: it patches the system property back. A mirroring subtractive cluster parameter might be useful? I could imagine it could be - but would be also more tough i.e. we can run into path normalization + comparison, in win / shellscript. Q4: are there other pending issues that could be addressed in the new launcher release ? I've searched GH issues and didn't found much. [...] Would you file those as issues ? -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: Rust, anyone?
On Fri, 17 Feb 2023 at 11:32, Michael Bien wrote: > we could hide the feature a little bit during beta, e.g keep the modules > disabled by default and print a warning notification that this is an > experimental feature when someone enables the modules. Possibly. Make that b.5 though! :-) I actually meant to have in a cluster that is not built by default or included in releases at all - similar to contrib, but for our own in-development things. Unless rust deserves its own cluster anyway in future? Could still publish from there to an update centre? In the process, we should probably make the cluster.properties file more relevant for us now - eg. beta, experimental, contrib sections probably not useful as is. https://github.com/apache/netbeans/blob/master/nbbuild/cluster.properties 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
Re: Rust, anyone?
me too. Would prefer to have it in NB rather than as plugin since language support is a core feature of IDEs IMO. Having it in the main repo during dev time has also its benefits, CI, potentially more eyes on the code etc. we could hide the feature a little bit during beta, e.g keep the modules disabled by default and print a warning notification that this is an experimental feature when someone enables the modules. best regards, michael On 16.02.23 23:46, László Kishalmi wrote: I'd vote for b.4 by Neil. On Thu, Feb 16, 2023 at 12:02 PM Chris wrote: Hey all, as far as I can remember, under oracle there was a time where we had a similar process to continous deployment. That means, that it was also possible, to release bugfixes inside the core and updates of plugins from the core between releases. Sometimes I opened NetBeans 7.1 and after weeks I got the info "there are updates" no 3rd-party-plugins, no 7.1 to 7.2. It was just that I had the HTML editor 1.1.1 -> 1.1.2 (just an example, not the correct version). So what is with those approaches? I would like to see as many stuff as possible inside the core and yes we have problems of updating stuff, when we wait for a new release. So is it possible to have such continous deployment after a PR was merged and all tests are green, in between releases? That means for me, we can have everything inside the code, rust, go, whatever and have also bugfixes and new small features. Is this not possible under apache? Cheers Chris Am 16.02.2023 um 10:20 schrieb Neil C Smith: Hi, On Thu, 16 Feb 2023 at 07:02, Antonio wrote: a) I don't think Rust support is ready yet to be merged with core: ... b.2) Create a repo of ours and let "rust" be an experimental plugin, and keep on improving it there. b.4) might be to merge into master as a separate cluster, or in an experimental cluster, and not include in the release list of clusters? Can see pros and cons to both approaches. Having somewhere we could develop and release (experimental) plugins from might be good. Having the development happen here also good. Personally see far more reason to eventually include Rust in core than some of the more product oriented things we do have in there that should have been kept as plugins IMO. 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 - 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
Re: Interruption of the Votethread for NB 17 (was: Re: [VOTE] Release Apache NetBeans 17)
Ok, you are like a closed group so NB is dying. The process of making nb videos on youtube are stopped several years ago and also there is no NB on winget repo. What do you think? There is roadmap? [image: image.png] пт, 17 февр. 2023 г. в 13:21, Neil C Smith : > Thanks Matthias. Let's please consider removing / moderating this > person on the list. > > Thanks, > > Neil > > On Thu, 16 Feb 2023 at 19:57, Matthias Bläsing > wrote: > > > > Hi, > > > > this is not funny and not a joke. > > > > The check of the release artifacts and the voting are an essential act > > of the release process and quality assurance. Misuse of the vote thread > > and disturbing the voting are not welcome here. > > > > Please don't repeat this. > > > > Matthias > > > > PS: This is CC to priv...@netbeans.apache.org, so that the PMC is > > aware, that there was a reaction to this. > > > > Am Donnerstag, dem 16.02.2023 um 22:46 +0300 schrieb name name2: > > > [] yes / +1 > > > *[V] no / -1 (please justify -1)* > > > [] binding (member of PMC) > > > > > > My vote is based on > > > > > > [V] There is a lot of critical bugs in new functionality > > > [V] I have a notepad instead > > > [V] I have tested the slow single thread style ant tasks > > > [] I have tested the Maven artefacts > > > [ ] I have tested the VSCode extension > > > > > > its just a joke )) > > > > > > чт, 16 февр. 2023 г. в 22:41, Matthias Bläsing > > > : > > > > > > > [X] yes / +1 > > > > [ ] no / -1 (please justify -1) > > > > [X] binding (member of PMC) > > > > > > > > My vote is based on > > > > > > > > [X] I have built and tested the source with Ubuntu OpenJDK 11 on > Ubuntu > > > > 22.10 > > > > [X] I have tested the binary zip with Amazon Corretto 17.0.4.1+9-LTS > on > > > > Ubuntu 22.10 > > > > [X] I have tested the DEB installer(s) with Ubuntu OpenJDK 11 > > > > (default-jdk) on Ubuntu 22.04 > > > > [ ] I have tested the Maven artefacts > > > > [ ] I have tested the VSCode extension > > > > > > > > > > > > Additionally checked, that ZIP file contents and repository contents > > > > matched (as far as can be expected). > > > > > > > > The DEB installer worked nicely and is well integrated into > gnome-shell > > > > (icon, naming). Nice! > > > > > > > > - > > > > 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: Launchers enhancement: extra clusters
On Fri, 17 Feb 2023 at 08:42, Svata Dedic wrote: > Q1: is there a strong opinion AGAINST using commandline parameter - and > to use rather a system property (or other technique) ? Please elaborate. Definitely in favour of the command line parameter. But, does it absolutely need launcher changes to achieve it? Not achievable by parsing the command line argument in MainImpl like you're doing with the system property? A mirroring subtractive cluster parameter might be useful? > Q4: are there other pending issues that could be addressed in the new > launcher release ? I've searched GH issues and didn't found much. I have a few things on my to-do list around jdkhome that might be worth considering in an update. - the IDE launchers should support relative setting of jdkhome in the same way as the platform launchers. We have to work around this in NBPackage, which complicates slightly the bundled JDK scenario we use in the community installers. - jdkhome parsing should not break if the path ends with a slash. eg. it's possible to configure a Windows shortcut with --jdkhome %JAVA_HOME%, except that it's usually set with an end \ so doesn't work. - the Windows launchers used to be able to locate a JDK when jdkhome isn't set IIRC, which the others can. 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
Re: Launchers enhancement: extra clusters
On Fri, 17 Feb 2023 at 09:46, Eric Barboni wrote: > Q3: > 12.5 is for june 2021 github releasenote were discovered later and we had a > vote cancel because of the version name. > I find it hard to be a NetBeans version as per construction it's made before > or after a milestone . .MM version was not a good idea. > The only point is it should be greater than 12.5 to ease maven version > comparison Well, we only had one non-PMC -1 on the version format, which seemed not to understand why it was being done in the first place. I have no strong opinion as long as there is absolutely no way it can be confused with the IDE version. 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
RE: Launchers enhancement: extra clusters
Hi, Q4: The repo is here, [1] we have a commited but not released launcher with eirikbakke fixes for paths and unicode It's windows centered but maybe all the script for linux/mac should be put there too. (not able to see clearly) Q1: I have no clear opinion Q2: we do a vote https://lists.apache.org/list?dev@netbeans.apache.org:2022-11:vote artefact are prepared like for mavenutiliies given a settings.xml set configured with apache credential you basicaly do n mvn release:prepare -Dusername= https://cwiki.apache.org/confluence/display/NETBEANS/Releasing+Apache+NetBeans+maven+utilities (need review) and artefacts will go to the apache nexus, you have to copy to dist/release the sources and after vote it goes live. Can serve as RM if you want. Q3: 12.5 is for june 2021 github releasenote were discovered later and we had a vote cancel because of the version name. I find it hard to be a NetBeans version as per construction it's made before or after a milestone . .MM version was not a good idea. The only point is it should be greater than 12.5 to ease maven version comparison Best Regards Eric [1] https://github.com/apache/netbeans-native-launchers -Message d'origine- De : Svata Dedic Envoyé : vendredi 17 février 2023 09:42 À : dev@netbeans.apache.org Objet : Launchers enhancement: extra clusters Hi, all, This e-mail is to solicit possible comments/opinions to the approach ... and to get some help as I don't seem to have enough info about the launcher release process :) I'd like to add a small enhancements to the binary launchers, as a follow-up to https://github.com/apache/netbeans/pull/5350 that somehow has to land in the master and future netbeans releases. I would like to add --add-clusters commandline option with a path-list of cluster based directories as a parameter, that allows to add additional code to the NB IDE (vsnetbeans server) runtime temporarily, without changing the configuration files. The option would be *additive* with contents of the current netbeans_extra_clusters config file value and netbeans.conf configuration file. Reasons for the change: Currently NB launchers read netbeans.clusters (or app.clusters) and netbeans.conf files for list of clusters in NB installation or possible other clusters respectively. But both files are static. In the "vsnetbeans" headless LSP server case, the NB process is started in the background, and should respect the current _runtime_ environment of the LSP client. Specifically in vscode, the extensions can be enabled/disabled per workspace, and there can be multiple NetBeans servers running for different workspace configurations. But the extension's code - that is configuration files like netbeans.clusters and netbeans.conf - remain on a shared location. A command-line argument allows the wrapper (initiating client) to launch NB process and pass apropriate requirements to it. An alternative would be, for example, a system property, as in the remporary fix (https://github.com/apache/netbeans/pull/5350). We discussed this approach with Dusan Balek and decided that a commandline parameter would be more appropriate. Now the questions come: Q1: is there a strong opinion AGAINST using commandline parameter - and to use rather a system property (or other technique) ? Please elaborate. Q2: what's the release process for the binary launchers (since they need to be published to maven central) ? Q3: what is the versioning scheme (launchers released in Nov 2022 are versioned 12.5) for the launchers artifact ? Q4: are there other pending issues that could be addressed in the new launcher release ? I've searched GH issues and didn't found much. Thanks, -Svata - 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
Launchers enhancement: extra clusters
Hi, all, This e-mail is to solicit possible comments/opinions to the approach ... and to get some help as I don't seem to have enough info about the launcher release process :) I'd like to add a small enhancements to the binary launchers, as a follow-up to https://github.com/apache/netbeans/pull/5350 that somehow has to land in the master and future netbeans releases. I would like to add --add-clusters commandline option with a path-list of cluster based directories as a parameter, that allows to add additional code to the NB IDE (vsnetbeans server) runtime temporarily, without changing the configuration files. The option would be *additive* with contents of the current netbeans_extra_clusters config file value and netbeans.conf configuration file. Reasons for the change: Currently NB launchers read netbeans.clusters (or app.clusters) and netbeans.conf files for list of clusters in NB installation or possible other clusters respectively. But both files are static. In the "vsnetbeans" headless LSP server case, the NB process is started in the background, and should respect the current _runtime_ environment of the LSP client. Specifically in vscode, the extensions can be enabled/disabled per workspace, and there can be multiple NetBeans servers running for different workspace configurations. But the extension's code - that is configuration files like netbeans.clusters and netbeans.conf - remain on a shared location. A command-line argument allows the wrapper (initiating client) to launch NB process and pass apropriate requirements to it. An alternative would be, for example, a system property, as in the remporary fix (https://github.com/apache/netbeans/pull/5350). We discussed this approach with Dusan Balek and decided that a commandline parameter would be more appropriate. Now the questions come: Q1: is there a strong opinion AGAINST using commandline parameter - and to use rather a system property (or other technique) ? Please elaborate. Q2: what's the release process for the binary launchers (since they need to be published to maven central) ? Q3: what is the versioning scheme (launchers released in Nov 2022 are versioned 12.5) for the launchers artifact ? Q4: are there other pending issues that could be addressed in the new launcher release ? I've searched GH issues and didn't found much. Thanks, -Svata - 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
