[NOTICE] Apache NetBeans 19 release candidate 3 available for testing

The third** release candidate build for Apache NetBeans 19 is available (links below). Changes since NetBeans 19-rc1 can be seen at https://github.com/apache/netbeans/releases/tag/19-rc3 ** the eagle-eyed might notice we skipped the 19-rc2 build! :-) Please help with testing, and file issues in

[NOTICE] Apache NetBeans 19 release candidate 1 available for testing

The first release candidate build for Apache NetBeans 19 is available (links below). Changes since NetBeans 18 can be seen at https://github.com/apache/netbeans/releases/tag/19-rc1 Please help with testing, and file issues in GitHub as necessary - https://github.com/apache/netbeans/issues If

Re: [NOTICE] Apache NetBeans 19 feature freeze / release branches

Hi, Module spec versions on master have now been updated for Apache NetBeans 20 and the master branch is reopened. Pull requests for NB20 can now be merged, with the usual care while we're syncing delivery every week. Thanks all, Neil On Tue, 18 Jul 2023 at 14:09, Neil C Smith wrote: > &

[NOTICE] Apache NetBeans 19 feature freeze / release branches

Hi All, As per earlier email, today is feature freeze for NetBeans 19, and the delivery and release branches are being set up. **Master is closed for a few hours - please don't merge anything until the spec version increment is in and a follow up email sent.** All open pull requests for NB19

Re: NetBeans Blog vs Start Page

On Mon, 17 Jul 2023 at 15:54, Michael Bien wrote: > but there is a higher level issue, essentially asking if NB will > continue to have some form of a dev blog or not: > https://github.com/apache/netbeans/issues/6200 And a second higher level issue, should it continue to use the Start Page at

Re: [NOTICE] - Freeze and branch for Apache NetBeans 19 on July 18th

tomorrow while we handle branching and update module versions - I'll keep you posted! Best wishes, Neil On Wed, 5 Jul 2023 at 18:01, Neil C Smith wrote: > > Hi All, > > This is advance notice that we're intending to freeze and branch for > NetBeans 19 on July 18th. > > As

Re: No proper way to report website issues

Hi, On Mon, 17 Jul 2023 at 11:44, Junichi Yamamoto wrote: > > We receive issues via this mailing list, so far, I think. > > It might be nice if we can use Issues of the netbeans-website repo [1] > > [1] https://github.com/apache/netbeans-website Agreed. Eric pointed this out on

Re: [VOTE] Release Apache NetBeans parent pom 4

+1 (binding) Looks good, checked hash and sig. Thanks, Neil On Wed, 5 Jul 2023 at 15:18, Eric Barboni wrote: > > Dear members of Apache NetBeans community. > > I want to call a vote on releasing Apache NetBeans parent pom 4. This is a > technical artefact. > > This is a maven pom containing

Re: [DISCUSS] Moving to NBPackage created installer for macOS from NB19?

On Thu, 6 Jul 2023 at 10:16, Eric Barboni wrote: > Maybe we could extend to all installer including windows one (linux already > there). Well, I've been in favour of that move for a while - in general moving to native OS options. The installer code in the repo is quite outdated and causing

[NOTICE] - Freeze and branch for Apache NetBeans 19 on July 18th

Hi All, This is advance notice that we're intending to freeze and branch for NetBeans 19 on July 18th. As we wind down towards NetBeans 19, please help with reviewing remaining pending pull requests by July 17th. Please be release aware - merged PRs should be ready for release and not require

[DISCUSS] Moving to NBPackage created installer for macOS from NB19?

Hi, There are a bunch of issues that have been raised recently about our ASF macOS packages, including - https://github.com/apache/netbeans/issues/6052 https://github.com/apache/netbeans/issues/6104 Aside from the problems that at the moment only John can create and sign the ASF installer (and

Re: [External] : Will there be an 18-u1?

On Fri, 16 Jun 2023 at 09:47, Chris Luff wrote: > Hey Neil, I am particularly keen to see #5993 dropped into an update release. > I am happy to do the cherry pick, but this would be my first time inside the > apache/netbeans repo. Thanks, Chris. Unfortunately, that's only part of the puzzle -

Re: Will there be an 18-u1?

On Fri, 16 Jun 2023 at 17:15, Martin Balin wrote: > there are some fixes in NetBeans I would like to release soon, by end of > June, at least like VSNetBeans 18.0.301 namely: > #5978: Maven/priming optimization by sdedic · Pull Request #5998 · > apache/netbeans > github.com > OCI library

Re: Contrib Repo

On Mon, 12 Jun 2023 at 11:26, Antonio wrote: > - CDDL binaries can indeed be used in Apache Projects. In fact we do use > many CDDL binaries in NetBeans. So can GPL+CPE binaries, and we currently ship with at least one. It currently requires permission on a case by case basis, to ensure all of

Will there be an 18-u1?

Hi, We have three PRs that have merged recently with Cherry Pick labels. https://github.com/apache/netbeans/issues?q=label%3A%22Cherry+Pick%22+is%3Aclosed+milestone%3ANB19 There are also one or two other potential fixes, (eg. maybe https://github.com/apache/netbeans/pull/6049 ), that come to

Re: Proposal: Bi-weekly 30 minute NetBeans clinic

On Wed, 7 Jun 2023 at 13:08, Eric Barboni wrote: > It could be done but we need minutes in asf slack / confluence / mail to keep > trace for people that can't be there. > And any fast loop decision in zoom should be notified to mailing list . > > It's cool idea to smooth confusion too. Yes,

Re: GitHub New Issue Form

On Fri, 2 Jun 2023 at 08:57, Vano Beridze wrote: > GitHub New Issue Form does not contain Netbeans 17 in the drop down menu of > "Did this work correctly in an earlier version?" Sorry, my fault - forgot to update that section when I switched the current version - will fix it now. Thanks for

[VOTE][RESULT] Release Apache NetBeans 18

://people.apache.org/phonebook.html?uid=gholmer Emmanuel Hugonnet https://people.apache.org/phonebook.html?uid=ehsavoie Josh Juneau https://people.apache.org/phonebook.html?uid=javajuneau Laszlo Kishalmi https://people.apache.org/phonebook.html?uid=lkishalmi Neil C Smith https://people.apache.org/phonebook.html

Re: [VOTE] Release Apache NetBeans 18

and macOS 12 [X] I have tested the DEB, RPM, Windows and macOS installer(s) with JDK 17 or 20 on Ubuntu 22.04, Fedora 36, Windows 11 and macOS 12. [ ] I have tested the Maven artefacts [ ] I have tested the VSCode extension On Tue, 23 May 2023 at 16:00, Neil C Smith wrote: > > This is our first

Re: [DISCUSS] Release Apache NetBeans 18: ConcurrentModificationException from javascript scanning

> oh nameless one, want to say who you are? But in general I agree. Seconded. We've had an anonymous message like this before, so I'd be interested in who, and how? > > On 5/24/23 01:25, Neil C Smith wrote: > > Voting candidates should not need to be tested for functionality. >

Re: [DISCUSS] Release Apache NetBeans 18: ConcurrentModificationException from javascript scanning

On Tue, 23 May 2023 at 20:20, Matthias Bläsing wrote: > testing the voting candidate, I noticed, that the JS scanning can run > into a ConcurrentModificationException. ... > For me this is not a big problem as described above, but people using > plain JS in the IDE might face bigger problems. At

[VOTE] Release Apache NetBeans 18

This is our first voting candidate for the release of Apache NetBeans 18. 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 18 constitutes all clusters in the Apache

Re: [LAZY CONSENSUS] Managing archetype for javaEE in house

A not required, but very happy so see this move, +1! Neil On Mon, 22 May 2023 at 10:30, Eric Barboni wrote: > > This is to propose the creation of new repository to manage javaEE archetype > that we use in Apache NetBeans on Apache NetBeans infrastructure. > > We already have some archetype for

[NOTICE] Apache NetBeans 18 release candidate 4 available for testing

The fourth release candidate build for Apache NetBeans 18 is available (links below). This will be our final release candidate unless high/critical priority issues or pull requests are flagged. Please kick the tyres well over the coming week or so! This includes testing building from source and

Re: Another release candidate for NB18

On Fri, 12 May 2023 at 14:06, Neil C Smith wrote: > Speak up before Monday if there are other high priority issues / PRs > that might deserve being addressed in 18-rc4. OK, nothing raised, so I'm syncing and triggering 18-rc4 now.

Another release candidate for NB18

Hi, Due to a minor critical issue (if that isn't an oxymoron!) we're going to be triggering another release candidate early next week. The issue affects the Maven repository generation, rather than the IDE itself, so we should still be on track to move to a vote in the week of May 22nd.

[NOTICE] Apache NetBeans 18 release candidate 3 available for testing

The third release candidate build for Apache NetBeans 18 is available (links below). This will be our final release candidate unless high/critical priority issues or pull requests are flagged. Please kick the tyres well over the coming week or so! This includes testing building from source and

Re: [RELEASES] Preparing for 18-rc3

On Tue, 9 May 2023 at 17:46, Svata Dedic wrote: > Pls. also consider the memory settings fix here: > https://github.com/apache/netbeans/pull/5914 It was already merged before we synced to release180 for the rc3 build. Let's try not to cherry pick from master too often! :-) This one isn't

Re: [RELEASES] Preparing for 18-rc3

On Tue, 9 May 2023 at 09:08, Neil C Smith wrote: > I'm going to let all the branch and sync tests run before merging the > other pending PRs. All green! Sync PR to release branch merged. Delivery now closed until we sync to master, although hopefully this will be our last rc anyway.

Re: [RELEASES] Preparing for 18-rc3

On Fri, 5 May 2023 at 10:11, Neil C Smith wrote: > > On Tue, 2 May 2023 at 16:09, Neil C Smith wrote: > > We don't have much in delivery for 18-rc3 yet, and are still waiting > > on #5842 to be ready for merging. > > Well, https://github.com/apache/netbeans/pull/5842

Re: Javahelp broken after update from NB platform 8.2 to 11.3 (Displayer not found by Lookup)

On Fri, 5 May 2023, 18:38 Milan Horák, wrote: > Hi, > > my two cents: > > We have we have a whole ERP written in NetBeans 8 and absence of > JavaHelp and absent Czech translation (solvable) is the only thing > keeping us there. We don't insist on JavaHelp, but I couldn't find a way > to replace

Re: Javahelp broken after update from NB platform 8.2 to 11.3 (Displayer not found by Lookup)

On Fri, 5 May 2023 at 14:51, Marco Peters wrote: > Yes, I know the versions are quite old. It's a little embarrassing. > Unfortunately, we didn't have the chance to update earlier in our ESA SNAP > project. We were still using Java 1.8 too. > So, we now want to update step by step and not with

Re: [RELEASES] Preparing for 18-rc3

On Tue, 2 May 2023 at 16:09, Neil C Smith wrote: > We don't have much in delivery for 18-rc3 yet, and are still waiting > on #5842 to be ready for merging. Well, https://github.com/apache/netbeans/pull/5842 was merged and we have consistent test failures in delivery since. A few other

Re: [RELEASES] Preparing for 18-rc3

On Tue, 2 May 2023 at 22:05, Michael Bien wrote: > +1 for giving rc3 a bit more time so that it can get 1-2 more PRs in. Also a chance to look through outstanding issues, particularly anything with the milestone or reported against the RCs! https://github.com/apache/netbeans/issues

Re: Netbeans support for sorting and coloring of project tabs

On Tue, 2 May 2023 at 16:53, Ken Stewart-Smith wrote: > I am using Microchip MPLAB IDE which uses Netbeans. MPLAB is a third-party product that does not use, and will not be using, Apache NetBeans. I suggest you follow up with them. Best wishes, Neil

[RELEASES] Preparing for 18-rc3

Hi, We don't have much in delivery for 18-rc3 yet, and are still waiting on #5842 to be ready for merging. Should we hold off rc3 for a few days, or even until the beginning of next week, to see if anything else comes up? Hopefully then can be the last rc, and we can move to vote in week of

Re: [NOTICE] apache gitbox is currently unavailable - this affects our builds

On Sun, 30 Apr 2023 at 09:36, Michael Bien wrote: > to build locally, simply add > "-Dmetabuild.jsonurl=https://raw.githubusercontent.com/apache/netbeans-jenkins-lib/master/meta/netbeansrelease.json; > to the build line. This will use github instead of apache infra to grab > the json. In

Re: [RELEASES] Preparing for 18-rc2

Hi, On Thu, 27 Apr 2023, 18:55 Martin Balín, wrote: > Neil, > I have a question about this PR > https://github.com/apache/netbeans/pull/5868 > Merged to delivery on April 24th, not yet in master. > Just curious as I wanted to try in master build… > It was included in the sync to master

Re: [RELEASES] Preparing for 18-rc2

ns/pull/5888 > > and on netbeans-tools: https://github.com/apache/netbeans-tools/pull/64 > > the later one would create a multi-arch Snap image from the release zip. > > It would be good to test it our on 18-rc2 (I just tested that on the > latest dev builds, what is working) > &g

[NOTICE] Apache NetBeans 18 release candidate 2 available for testing

The second release candidate build for Apache NetBeans 18 is available (links below). Changes since NetBeans 18-rc1 can be seen at https://github.com/apache/netbeans/releases/tag/18-rc2 Please help with testing, and file issues in GitHub as necessary - https://github.com/apache/netbeans/issues

[RELEASES] Preparing for 18-rc2

Hi, I plan to close delivery tomorrow morning (UK time) and merge to the release branch to build rc2. There are two open PRs, both with do-not-merge labels. I'm fairly sure one won't be ready by then, but if the other is ready I'll merge it. I'll follow up in this thread when delivery is open

[NOTICE] Apache NetBeans 18 release candidate 1 available for testing

The first release candidate build for Apache NetBeans 18 is available (links below). Changes since NetBeans 17 can be seen at https://github.com/apache/netbeans/releases/tag/18-rc1 Please help with testing, and file issues in GitHub as necessary - https://github.com/apache/netbeans/issues If

Re: [NOTICE] Apache NetBeans 18 feature freeze / release branches

On Tue, 18 Apr 2023 at 15:13, Neil C Smith wrote: > **Master is closed for a few hours - please don't merge anything until > the spec version increment is in and a follow up email sent.** This is now done and master is open again for NB19 development. Thanks,

[NOTICE] Apache NetBeans 18 feature freeze / release branches

Hi All, As per earlier email, today is feature freeze for NetBeans 18, and the delivery and release branches are being set up. **Master is closed for a few hours - please don't merge anything until the spec version increment is in and a follow up email sent.** All open pull requests for NB18

Re: [DISCUSS] disable remote index extraction by default [NB18]

On Tue, 18 Apr 2023 at 06:49, Jan Lahoda wrote: > I apologize for being contrarian, but since the index download started for > me (again) while on a bus with very poor internet connection, I guess I > should tell you my view. ... > To be honest, it never seemed very polite to me to download and

Re: [NOTICE] - Freeze and branch for Apache NetBeans 18 on April 18th

On Sat, 15 Apr 2023 at 18:54, Michael Bien wrote: > I would like to add that if you are a committer, you can merge your own > PRs assuming they are reviewed, the right tests ran and properly > squashed. I am sometimes getting the impression that it is expected that > the release team is merging

[VOTE][RESULT] Minimum JDK build and run policy (dropping JDK 8)

Kishalmi John McDonnell Thilina Ranathunga Neil C Smith Committer +1 (3) Christian Oyarzun Karl Tauber Brad Walker Community +1 (9) Arnaud Bourree Jakub Herkel Alexander Kronenwett Wim Maerevoet John Neffenger Scott Palmer Kai Uwe Pel Tito Sanchez Giles Winstanley PMC -1 (1) Jaroslav Tulach PMC

Re: [VOTE] Minimum JDK build and run policy (dropping JDK 8)

+1 (binding) Thanks all, closing the vote. On Tue, 11 Apr 2023 at 09:16, Neil C Smith wrote: > > # Proposed policy > > * Apache NetBeans 18 will be the last release to support running the > platform on JDK 8. > > * From Apache NetBeans 19, the minimum JDK required to bu

Re: [NOTICE] - Freeze and branch for Apache NetBeans 18 on April 18th

On Sat, 8 Apr 2023 at 14:29, Neil C Smith wrote: > This is advance notice that we're intending to freeze and branch for > NetBeans 18 on April 18th. > > As we wind down towards NetBeans 18, please help with reviewing > remaining pending pull requests by April 17th. Just a r

Re: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Wed, 12 Apr 2023 at 16:39, Peter Blemel wrote: > My only concern with dropping JDK 11 is that JDK 17 made certain policy > warnings into fatal errors, which stops my platform apps from running. > Granted, this is a matter of me tracking down all of the issues that JDK 17 > forbids and

Re: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Wed, 12 Apr 2023 at 04:32, Jaroslav Tulach wrote: > The core of my alternative proposal is to move forward and support newer JDKs > properly, where needed via the "Run on JDK8, use JDK11 APIs!" - http:// > wiki.apidesign.org/wiki/AlternativeImplementation > > Are you saying we are using this

Re: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Wed, 12 Apr 2023 at 12:48, Svata Dedic wrote: > But it requires some degree of cooperation, which seem to be rejected > upfront. ... > But again, that assumes some degree of honest cooperation/respect from > the progressive majority - but given the past communication, throwing > obstacles in

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Tue, 11 Apr 2023 at 13:07, Geertjan Wielenga wrote: > INFO [org.netbeans.core.startup.NbEvents]: Turning on modules: > org.openide.util.lookup [8.25.1 20221005-cd0c929e4999] Thanks. Old style spec versions (although more recently compiled!) So that module is currently 8.54. I think it was

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Tue, 11 Apr 2023 at 12:43, Geertjan Wielenga wrote: > To Karl's question -- the cool new look and feels are not included in > the latest Microchip MPLAB X IDE, so it's quite an old version of the > NetBeans Platform, ... Not necessarily. You have to actively opt in to those. I implemented

[VOTE] Minimum JDK build and run policy (dropping JDK 8)

# Proposed policy * Apache NetBeans 18 will be the last release to support running the platform on JDK 8. * From Apache NetBeans 19, the minimum JDK required to build and run the IDE or platform will be JDK 11. * Future releases will take an "LTS-1" strategy for building and running (and CI

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Tue, 11 Apr 2023 at 07:41, Geertjan Wielenga wrote: > Could a consensus solution be that for all JDK 8 - compatibility > related items, any/all work related to that, we assign those issues to > Svata -- and we try this for one release and see how that goes? If it > fails, then in the release

Re: Publishing the VS Code extension on open-vsx.org

On Mon, 10 Apr 2023, 19:35 Jan Lahoda, wrote: > Hi, > > I just wanted to ask if anyone would object to me trying to publish the > existing VS Code extension binary on https://open-vsx.org? > https://github.com/apache/netbeans/issues/3914 Best wishes, Neil

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Mon, 10 Apr 2023, 17:45 Jaroslav Tulach, wrote: > Thank you Sváťa for writing this email. It open another "can of worms" in > the "lazy consensus" thread - in my opinion clearly rendering the "lazy > consensus" as obsolete. > In Apache projects, "consensus" means *widespread agreement among

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Mon, 10 Apr 2023 at 00:16, Svata Dedic wrote: > Please remember that the published proposal not only covered JDK8's > fate, which we argue about right now, but also the idea to drop JDK11 in > 2024. So take my > > * -1 (at the moment) for JDK8 phase out with NB19; > * and ANOTHER -1 to the

[NOTICE] - Freeze and branch for Apache NetBeans 18 on April 18th

Hi All, This is advance notice that we're intending to freeze and branch for NetBeans 18 on April 18th. As we wind down towards NetBeans 18, please help with reviewing remaining pending pull requests by April 17th. Please be release aware - merged PRs should be ready for release and not require

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Sat, 8 Apr 2023 at 13:05, Jaroslav Tulach wrote: > ...is going to break the promise me, you > and the NetBeans team was giving NetBeans Platform users since 1997! Aside from wondering how dropping JDK 7 support was not breaking the same promise, my message to Toni would be roughly the same as

Re: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Wed, 5 Apr 2023 at 17:25, toni.ep...@eppleton.de wrote: > Having the portability for platforms like Android is important, ... Did you read the proposal in full?! I know some of those currently actively working on the NetBeans codebase have expressed some bafflement at this, given we neither

Re: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

On Wed, 5 Apr 2023 at 16:13, Jaroslav Tulach wrote: > Alternative: > > - I will maintain what ever needs to be maintained to keep JDK 8 CI tests > running > > - From Apache NetBeans 19, the minimum JDK required to build and run > the IDE will be JDK 11. > > - The minimum JDK to run and test the

Re: Launching an application

On Tue, 4 Apr 2023 at 21:24, László Kishalmi wrote: > Snap cannot depend on system packages. It may depend on other snaps as > content packs, however that would only in a sandboxed environment. (We are > not sandboxed at the moment). Yes, I was wondering if classic confinement had a way to

Re: Launching an application

On Tue, 4 Apr 2023 at 18:12, Andrii Cherepkov wrote: > Yes, I know that NetBeans uses JDK and I need to install that. > But I said about users who don't know about that. Whey is not seeing any > popup windows in Linux like Ubuntu. Because it's not as simple an ask as it is on Windows. Does the

Re: Lets talk about JDK 8 (new year edition)

On Sun, 2 Apr 2023 at 15:49, Matthias Bläsing wrote: > Am Sonntag, dem 02.04.2023 um 15:38 +0200 schrieb Jaroslav Tulach: > > > It also becomes increasingly difficult to > > > motivate myself to fix JDK 8 issues in my freetime. > > > > I can imagine that. However we are not coding NetBeans to

[Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

As mentioned elsewhere, I'm kicking off a process to bring this issue to a decision. For various reasons, having a decision before we branch off NB18 is desirable. I've drawn up a draft proposal (below) that tries to encompass most of what has been expressed, and hopefully achieves that - thanks

Re: Lets talk about JDK 8 (new year edition)

On Fri, 31 Mar 2023 at 23:54, rangi.k...@siemens.com wrote: > I am in favor of an LTS-1 policy. It allows us to adopt (somewhat) recent > additions to the language while still supporting some older environments. > Given that with the new release roadmap we will see a new LTS release every >

Re: Lets talk about JDK 8 (new year edition)

On Tue, 14 Feb 2023 at 08:51, Michael Bien wrote: > With every new JDK release it will become more difficult to keep > supporting JDK 8 as runtime. It also becomes increasingly difficult to > motivate myself to fix JDK 8 issues in my freetime. If I see PRs which > fix edge cases in java-version

Re: [DISCUSS] tweak some defaults (round two)

On Sun, 19 Mar 2023 at 04:06, Michael Bien wrote: > - disable compile on save (maven) Let's deal with that first, as I'm mainly moving the discussion here as I was told to on https://github.com/apache/netbeans/issues/5260 :-) +1 for having that off by default. I think we have enough

Re: Compatibility with JDK 8: Shift work to people wanting it (was: Re: Lets talk about JDK 8 (new year edition))

On Thu, 16 Mar 2023 at 11:46, Svata Dedic wrote: > I see the rapid movement between > JDK versions that is even increasing with increased frequency of JDK > releases (with only limited features that make a real difference for NB > development) as dangerous But also a reality we don't control,

Re: Compatibility with JDK 8: Shift work to people wanting it (was: Re: Lets talk about JDK 8 (new year edition))

Hi Matthias, On Sun, 12 Feb 2023 at 22:22, Neil C Smith wrote: > On Sun, 12 Feb 2023, 19:11 Matthias Bläsing, > wrote: >> >> Hi, >> >> Am Freitag, dem 10.02.2023 um 10:12 + schrieb Neil C Smith: >> > On Thu, 9 Feb 2023 at 19:02, Matthias Bläsin

Re: [Discuss] Security and lunching programs from the IDE

On Tue, 14 Mar 2023 at 17:31, Antonio wrote: > This is very much the same we do with other external tools we may use, > such as "maven", or "npm" or "gradle" (we use our embedded "ant" though, > AFAIK). Maven is embedded too. > The question is, shall the IDE ask the user for permission before

Re: [DISCUSSION] Apache NetBeans 16-u1 Finalization Steps

On Wed, 4 Jan 2023 at 02:13, Laszlo Kishalmi wrote: > Created files updates-16.xml and updates-16-u1.xml (and gz and sha512 in > the same pattern). updates.xml and others have been replaced with > symlinks pointing to the 16-u1 versions. Now updated again to point to the archived versions, as

Re: Uploading binaries (OSUOSL)

On Sun, 26 Feb 2023 at 15:32, Matthias Bläsing wrote: > > Assume some portion of these may be available for other sources (i.e. maven > > central). Is any of these sources available as an alternative? > > Sure - many and without having counted the majority is already > downloaded from Maven

Re: Rust, anyone?

On Sun, 26 Feb 2023 at 21:11, Antonio wrote: > Wow, it's full of clusters [1]! :-) > If we added "rust" to "clusters.config.full.list" will it end up in the > stable update center? Maybe we don't want that yet, right? -Dcluster.config=release is used for everything - source, binaries and

Re: Rust, anyone?

On Sun, 26 Feb 2023 at 21:20, Michael Bien wrote: > this draft tests switching CI from release to the full cluster config. > > https://github.com/apache/netbeans/pull/5568 > > the properties file does need some cleanup IMO and we should make sure > that the cluster order isn't significantly

Re: Rust, anyone?

On Sun, 26 Feb 2023, 19:35 Michael Bien, wrote: > we have to make up our mind how to handle testing :) > ... > a) the "rust" branch approach > > we switch everything in main.yml to the rust cluster in that branch ... > My suggestion above was to add rust into the release cluster in the rust

Re: Rust, anyone?

On Fri, 24 Feb 2023 at 17:12, Michael Bien wrote: > We could skip 1.2 if you want and go right to master and develop it > there, no? > ... > Regarding testing... As you probably know, github actions build the > 'release' cluster config in a matrix, ... I was with you initially on skipping 1.2.

Re: Can't recompile master.

On Fri, 24 Feb 2023 at 17:08, Łukasz Bownik wrote: > I'm on Windows 11 Home, jdk 1.8.181 Build requires Java 11+ Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail:

[RESULT][VOTE] Release Apache NetBeans 17

=lkishalmi Neil C Smith https://people.apache.org/phonebook.html?uid=neilcsmith Geertjan Wielenga https://people.apache.org/phonebook.html?uid=geertjan Junichi Yamamoto https://people.apache.org/phonebook.html?uid=junichi11 +1 community votes : James Gosling* Kai Uwe Pel Tomáš Procházka Antonio

Re: [VOTE] Release Apache NetBeans 17

22.04 [X] I have tested the Windows, macOS and Linux DEB & RPM installer(s) with JDK 17 on Windows 11, macOS 12 (M1), Ubuntu 22.04 and Fedora 37 [ ] I have tested the Maven artefacts [ ] I have tested the VSCode extension On Thu, 16 Feb 2023 at 15:13, Neil C Smith wrote: > > This is our fi

Re: Release vote form - (was: single vote thread ...)

On Sat, 18 Feb 2023 at 11:18, Antonio wrote: > Apologies for posting in the wrong thread. No problem! If we can keep discussion out of [NOTICE], [LAZY CONSENSUS] and [VOTE] threads, then people can filter specifically on those subject tags. And by extension, hopefully not complain they missed

Re: Release vote form - (was: single vote thread ...)

On Fri, 17 Feb 2023 at 20:27, Antonio wrote: > I have voted using the template, I think we should rephrase it somewhow. > It's too verbose to clearly understand. This I agree with, and as mentioned above it's interesting to compare with the OpenOffice votes where we took a lead on the form -

Re: [LAZY CONSENSUS] single vote thread for NetBeans 17

On Fri, 17 Feb 2023 at 20:27, Antonio wrote: > I have voted using the template, I think we should rephrase it somewhow. > It's too verbose to clearly understand. Thanks. Will respond in the existing discussion thread about this - https://lists.apache.org/thread/5y8x2rtx1r6k4cbx7wyqvdm1qkhm0vzs

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

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

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

Re: Fedora 37 + RedHat JDK 17 + NB 17 vc1 doesn't start

On Thu, 16 Feb 2023 at 17:34, Michael Bien wrote: > > On 16.02.23 18:10, Neil C Smith wrote: > > On Thu, 16 Feb 2023 at 16:57, Michael Bien wrote: > >> tested the rpm on Red_Hat-17.0.5.0.8-1.fc37 > >> (+Red_Hat-17.0.6.0.10-1.fc37) and it did not start, it did wor

Re: Fedora 37 + RedHat JDK 17 + NB 17 vc1 doesn't start

On Thu, 16 Feb 2023 at 16:57, Michael Bien wrote: > > tested the rpm on Red_Hat-17.0.5.0.8-1.fc37 > (+Red_Hat-17.0.6.0.10-1.fc37) and it did not start, it did work fine on > other JDKs, e.g on Corretto 17: Working fine here in Virtualbox with Fedora 37 and RedHat JDK 17, and that file is there.

[VOTE] Release Apache NetBeans 17

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

Re: [LAZY CONSENSUS] single vote thread for NetBeans 17

7:24 AM Thilina Ranathunga > wrote: > > > It's a +1 for me. > > > >  > > > > -- > > Thilina01 > > > > On Sat, Feb 11, 2023, 12:14 AM Neil C Smith wrote: > > > > > Hi, > > > > > > Due to previously discusse

Re: Rust, anyone?

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

Re: NBLS issue with NB17

On Wed, 15 Feb 2023 at 14:47, Svata Dedic wrote: > I ask you to consider this hotfix to be applied on branch release170 and > creating a RC4 with that hotfix ... Sorry, the vote candidate has been built, signed and uploaded already, along with half of the other artefacts -

Re: 17 blocker? — [apache/netbeans] no library found for namespace http://omnifaces.org/ui (Issue #4976)

Hi, On Wed, 15 Feb 2023 at 08:24, Geertjan Wielenga wrote: > Do we have an assessment on the below, why it’s happening and what should > be done — I thought a lot of Jakarta EE work had been done recently, could > this be included? If you or anyone else wants to call this a blocker, please

Re: Lets talk about JDK 8 (new year edition)

On Mon, 13 Feb 2023 at 19:26, Jaroslav Tulach wrote: > As you probably know, I am not participating in day-to-day development of > NetBeans. And for those of use who are more involved day-to-day, it's causing issues, and creating work (including the issue that kicked off this thread). That one

Re: NB 17rc3 Java Module caused exception in Lexer?

On Mon, 13 Feb 2023 at 15:11, Scott Palmer wrote: > > > On Feb 13, 2023, at 9:17 AM, Neil C Smith wrote: > > > > On Sat, 11 Feb 2023 at 22:41, Scott Palmer wrote: > >> Saw this in the messages.log for NB 17rc3 > > > > Please can you report as a bug,

Proceeding towards NetBeans 17 release?

Hi, How are you getting on with 17-rc3? There are no open PRs against NB17 and no current high / critical marked issues. Issues currently marked NB17 that will be pushed back to NB18 are here - https://github.com/apache/netbeans/issues?q=is%3Aopen+is%3Aissue+milestone%3ANB17 Any concerns about

Re: NB 17rc3 Java Module caused exception in Lexer?

On Sat, 11 Feb 2023 at 22:41, Scott Palmer wrote: > Saw this in the messages.log for NB 17rc3 Please can you report as a bug, with context. Thanks, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For

Re: Issues with Gradle 8.0-rc-5 on NB 17rc3

On Sat, 11 Feb 2023 at 22:44, Scott Palmer wrote: > > Trying to run multiple gradle projects from the IDE and second one failed. > > A org.gradle.tooling.GradleConnectionException has occurred. > > If you are running the latest version > of NetBeans you can

<    1   2   3   4   5   6   7   8   9   10   >