date:20230216

official youtube channel reniew request

2023-02-16 Thread name name2

https://www.youtube.com/@NetBeansVideos/videos

>Welcome to the official YouTube channel for the NetBeans IDE and NetBeans
Platform, featuring videos from the NetBeans team and community!

Where is a new videos? Last video was published about 3 years ago

Re: Rust, anyone?

2023-02-16 Thread László Kishalmi

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
>
>
>
>

Re: Rust, anyone?

2023-02-16 Thread Chris


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

Re: [VOTE] Release Apache NetBeans 17

2023-02-16 Thread 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: [VOTE] Release Apache NetBeans 17

2023-02-16 Thread 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

No communication from plugin portal verifiers (do we need to drop plugin portal?)

2023-02-16 Thread Matthias Bläsing

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://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

2023-02-16 Thread Kai Uwe Pel

[X] 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)
[X] I have tested the binary zip with installer(s) with on
[X] I have tested the Maven artefacts
[ ] I have tested the VSCode extension

Best regards
Kai Uwe Pel

On 2/16/2023 4:13 PM, 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 tested

Thank you to all contributors for all your hard work!

Apache NetBeans release team

Re: [VOTE] Release Apache NetBeans 17

2023-02-16 Thread Michael Bien

please ignore the RedHat note, that was user error - everything is
working as expected

On 16.02.23 18:07, Michael Bien wrote:

[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 jdk-19.0.2.7.1-corretto on
Linux 6.1.11-1-MANJARO (required)
[x] I have tested the binary zip with jdk-19.0.2.7.1-corretto on Linux
6.1.11-1-MANJARO (Cinnamon DE)
[x] I have tested the rpm installer with
amazon-corretto-17.0.6.10.1-linux-x64 on Linux fedora
6.0.10-300.fc37.x86_64
[x] I have tested the deb installer with OpenJDK
17.0.4+8-Debian-1deb11u1 on Debian 11.5 5.10.149-2

[x] I have tested the Maven artefacts
[ ] I have tested the VSCode extension

Additional info (optional) - any specifics on what you've tested

note:
- default Red Hat JDK 17 on fedora 37 did not start (since corretto
worked I don't see it as show stopper), see other thread
- tested mostly java projects which use maven/mvnd + only rudimentary
tests with the maven artifacts + installer tests were mostly automated

thanks Neil && release team - great release!

best regards,
michael

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.

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/

-- 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

In particular, you should (at least) follow these steps.

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

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

2023-02-16 Thread Neil C Smith

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 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.
> >
> > Are you sure you haven't just got the headless JDK package installed?
>
> actually I have (its stock fedora and it worked last time).
>
> I just ran "sudo dnf install java-17-openjdk" again and it downloaded
> 500kb and re-installed it - and NetBeans 17 is starting now...
>
> can't explain what happened - false alarm sorry,

No worries.  Let's just say that one comes from experience ... ;-)

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: [apache/netbeans/rcp]

2023-02-16 Thread Christian Oyarzun

I put them default_options in a custom app.conf file using
https://bits.netbeans.org/mavenutilities/nbm-maven-plugin/nbm-maven-plugin/cluster-app-mojo.html#etcConfFile
.

Maybe we should consider adding the minimum required from what the Wizards
generates to the default file? This will also require another PR for the
harness used by nbm-maven-plugin.
https://github.com/apache/netbeans/blob/master/harness/apisupport.harness/release/etc/app.conf


--Christian

On Thu, Feb 16, 2023 at 11:58 AM Claudio Rosati
 wrote:

> Thank you Michael for your answer.
>
> I have imagined that some “--add-opens” and “--add-exports” should have
> been added. The real problem was where add these flags. The jms-config link
> was anyway very useful to have a set of flags ready to be copyed.
>
> However, digging a bit here and there I’ve found where to hadd the flags
> for the Ant-based RCP app, and for the Maven based too. I’ll add
> instructions here for completeness (possibly the following instructions
> should be added to the “NetBeans Platform Quick Start” and “NetBeans
> Platform Quick Start Using Maven” documentation pages).
>
>
> Ant-based RCP app
> -
>
> In the application module's “project.properties” file add the
> “--add-opens” and “--add-exports” directives to the “run.args.extra”
> property, in my specific situation the following was enough:
>
> run.args.extra=\
> -J--add-opens=java.base/java.net=ALL-UNNAMED \
> -J--add-opens=java.desktop/javax.swing=ALL-UNNAMED \
> -J--add-exports=java.desktop/sun.awt=ALL-UNNAMED
>
>
> Maven-based RCP app
> ---
>
> Maven-based RCP apps require a little more work.
>
> In the application module’s “pom.xml” file add the “netbeans.run.params”
> property with all “--add-opens” and “--add-exports” directives prefixed by
> “-J”:
>
> 
>   ...
>   -J--add-opens=java.base/java.net=ALL-UNNAMED
> -J--add-opens=java.desktop/javax.swing=ALL-UNNAMED
> -J--add-exports=java.desktop/sun.awt=ALL-UNNAMED
> 
>
> The change will allow running the application without problems. Instead
> building will fails because the application is run as a
> maven-surefire-plugin test, and the added property is not applied, moreover
> when the application is run normally the “-Djava.security.manager=allow” is
> set, but not when launched in a test.
>
> To fis those problems, in the same “pom.xml” locate the definition of the
> “maven-surefire-plugin”, and to its configuration add the “argLine”
> parameter containing “-Djava.security.manager=allow”, and all the
> “--add-opens” and “--add-exports” directives without the “-J” prefix:
>
> 
> 
> ...
> 
> 
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12.2
> 
> -Djava.security.manager=allow
> --add-opens=java.base/java.net=ALL-UNNAMED
> --add-opens=java.desktop/javax.swing=ALL-UNNAMED
> --add-exports=java.desktop/sun.awt=ALL-UNNAMED
> ...
> 
> 
> ...
> 
> 
>
>
> I think that the missing “-Djava.security.manager=allow” parameter to the
> maven-surefire-plugin should be fixed in the following release of NetBeans,
> while some tools to transparently easily allow the user to add/remove
> “--add-opens” and “--add-exports” directives could be added in the module
> node’s Properties dialog.
>
> Best regards,
> Claudio
>
>
> _
>
> Claudio Rosati
>
> Calle Tamara 7
> Villa Jinámar
> 35220 Telde, Gran Canaria
> España
> Skype:  claudio.rosati
> Phone:  +34 638 579 990 (mobile)
> E-mail: claudio.ros...@mac.com
> _
>
> EMAIL CONFIDENTIALITY NOTICE
> This message is private and confidential.
> If you have received this message in error,
> please notify me and remove it from your system.
> _
>
>
>
>
> > On 16 Feb 2023, at 10:47, Michael Bien  wrote:
> >
> > this is caused by encapsulation violations of the java module system,
> see JEP 396. If you run it on JDK 15 or older, you should see warnings,
> anything after that will throw exceptions.
> >
> > Some NetBeans modules need direct access to JDK modules.
> >
> > NetBeans-the-IDE sets the following flags:
> > https://github.com/apache/netbeans/tree/master/nbbuild/jms-config
> >
> > NetBeans RCP apps won't need all of those flags, since they usually use
> a subset of the modules NetBeans uses.
> >
> > there should be many blog entries online about this topic since it isn't
> really NB specific,
> >
> > best regards,
> > michael
> >
> >
> > On 16.02.23 11:34, Claudio Rosati wrote:
> >> Hello all,
> >>
> >> After some years not using NetBeans RCP (only de IDE), I’ve tried to
> follow the "NetBeans Platform Quick Start Using Maven” using NetBeans 16
> with Java 19.
> >>
> >> When I try to "Build with Dependencies” the app the following error
> appears at compilation time:
> >>
> >> Running es.intellectusetanima.mavenplatformwordapp.ApplicationTest
> >> Feb 14, 2023

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

2023-02-16 Thread Matthias Bläsing

Hi Michael,

Am Donnerstag, dem 16.02.2023 um 17:52 +0100 schrieb Michael Bien:
> 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:
> 
> [mbien@fedora netbeans-validation]$ uname -a
> Linux fedora 6.0.10-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 26 
> 16:55:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
> [mbien@fedora netbeans-validation]$ java -version
> openjdk version "17.0.5" 2022-10-18
> OpenJDK Runtime Environment (Red_Hat-17.0.5.0.8-1.fc37) (build 17.0.5+8)
> OpenJDK 64-Bit Server VM (Red_Hat-17.0.5.0.8-1.fc37) (build 17.0.5+8, 
> mixed mode, sharing)
> 
> [mbien@fedora netbeans-validation]$ netbeans
> which: no javac in 
> (/home/mbien/.local/bin:/home/mbien/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)
> WARNING: package com.apple.eio not in java.desktop
> java.lang.UnsatisfiedLinkError: Can't load library: 
> /usr/lib/jvm/java-17-openjdk-17.0.5.0.8-1.fc37.x86_64/lib/libawt_xawt.so
>      at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2393)
>      at java.base/java.lang.Runtime.load0(Runtime.java:755)
>      at java.base/java.lang.System.load(System.java:1953)

Neil is right. I checked the Fedora 37 workstation live DVD and:

sudo dnf list installed | grep jdk

shows:

java-17-openjdk-headless.x86_64

This is trivially fixed by running:

sudo dnf install java-17-openjdk

And yay - starts.

HTH

Matthias

-
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: Fedora 37 + RedHat JDK 17 + NB 17 vc1 doesn't start

2023-02-16 Thread Michael Bien


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 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.

Are you sure you haven't just got the headless JDK package installed?


actually I have (its stock fedora and it worked last time).

I just ran "sudo dnf install java-17-openjdk" again and it downloaded 
500kb and re-installed it - and NetBeans 17 is starting now...


can't explain what happened - false alarm sorry,

best regards,

michael



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

Re: [VOTE] Release Apache NetBeans 17

2023-02-16 Thread Michael Bien

[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 jdk-19.0.2.7.1-corretto on Linux
6.1.11-1-MANJARO (required)
[x] I have tested the binary zip with jdk-19.0.2.7.1-corretto on Linux
6.1.11-1-MANJARO (Cinnamon DE)
[x] I have tested the rpm installer with amazon-corretto-17.0.6.10.1-linux-x64
on Linux fedora 6.0.10-300.fc37.x86_64
[x] I have tested the deb installer with OpenJDK 17.0.4+8-Debian-1deb11u1 on
Debian 11.5 5.10.149-2
[x] I have tested the Maven artefacts
[ ] I have tested the VSCode extension

Additional info (optional) - any specifics on what you've tested

thanks Neil && release team - great release!

best regards,
michael

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.

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/

-- 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

In particular, you should (at least) follow these steps.

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

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

2023-02-16 Thread Neil C Smith

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.

Are you sure you haven't just got the headless JDK package installed?

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: [apache/netbeans/rcp]

2023-02-16 Thread Claudio Rosati

Thank you Michael for your answer.

I have imagined that some “--add-opens” and “--add-exports” should have been 
added. The real problem was where add these flags. The jms-config link was 
anyway very useful to have a set of flags ready to be copyed.

However, digging a bit here and there I’ve found where to hadd the flags for 
the Ant-based RCP app, and for the Maven based too. I’ll add instructions here 
for completeness (possibly the following instructions should be added to the 
“NetBeans Platform Quick Start” and “NetBeans Platform Quick Start Using Maven” 
documentation pages).

Ant-based RCP app
-

In the application module's “project.properties” file add the “--add-opens” and 
“--add-exports” directives to the “run.args.extra” property, in my specific 
situation the following was enough:

run.args.extra=\
-J--add-opens=java.base/java.net=ALL-UNNAMED \
-J--add-opens=java.desktop/javax.swing=ALL-UNNAMED \
-J--add-exports=java.desktop/sun.awt=ALL-UNNAMED 

Maven-based RCP app
---

Maven-based RCP apps require a little more work.

In the application module’s “pom.xml” file add the “netbeans.run.params” 
property with all “--add-opens” and “--add-exports” directives prefixed by “-J”:

  ...
  -J--add-opens=java.base/java.net=ALL-UNNAMED 
-J--add-opens=java.desktop/javax.swing=ALL-UNNAMED 
-J--add-exports=java.desktop/sun.awt=ALL-UNNAMED

The change will allow running the application without problems. Instead 
building will fails because the application is run as a maven-surefire-plugin 
test, and the added property is not applied, moreover when the application is 
run normally the “-Djava.security.manager=allow” is set, but not when launched 
in a test.

To fis those problems, in the same “pom.xml” locate the definition of the 
“maven-surefire-plugin”, and to its configuration add the “argLine” parameter 
containing “-Djava.security.manager=allow”, and all the “--add-opens” and 
“--add-exports” directives without the “-J” prefix:

...

org.apache.maven.plugins
maven-surefire-plugin
2.12.2

-Djava.security.manager=allow 
--add-opens=java.base/java.net=ALL-UNNAMED 
--add-opens=java.desktop/javax.swing=ALL-UNNAMED 
--add-exports=java.desktop/sun.awt=ALL-UNNAMED
...

...

I think that the missing “-Djava.security.manager=allow” parameter to the 
maven-surefire-plugin should be fixed in the following release of NetBeans, 
while some tools to transparently easily allow the user to add/remove 
“--add-opens” and “--add-exports” directives could be added in the module 
node’s Properties dialog.

Best regards,
Claudio

_

Claudio Rosati

Calle Tamara 7
Villa Jinámar
35220 Telde, Gran Canaria
España
Skype:  claudio.rosati
Phone:  +34 638 579 990 (mobile)
E-mail: claudio.ros...@mac.com
_

EMAIL CONFIDENTIALITY NOTICE
This message is private and confidential. 
If you have received this message in error, 
please notify me and remove it from your system.
_

> On 16 Feb 2023, at 10:47, Michael Bien  wrote:
> 
> this is caused by encapsulation violations of the java module system, see JEP 
> 396. If you run it on JDK 15 or older, you should see warnings, anything 
> after that will throw exceptions.
> 
> Some NetBeans modules need direct access to JDK modules.
> 
> NetBeans-the-IDE sets the following flags:
> https://github.com/apache/netbeans/tree/master/nbbuild/jms-config
> 
> NetBeans RCP apps won't need all of those flags, since they usually use a 
> subset of the modules NetBeans uses.
> 
> there should be many blog entries online about this topic since it isn't 
> really NB specific,
> 
> best regards,
> michael
> 
> 
> On 16.02.23 11:34, Claudio Rosati wrote:
>> Hello all,
>> 
>> After some years not using NetBeans RCP (only de IDE), I’ve tried to follow 
>> the "NetBeans Platform Quick Start Using Maven” using NetBeans 16 with Java 
>> 19.
>> 
>> When I try to "Build with Dependencies” the app the following error appears 
>> at compilation time:
>> 
>> Running es.intellectusetanima.mavenplatformwordapp.ApplicationTest
>> Feb 14, 2023 1:09:17 PM org.netbeans.ProxyURLStreamHandlerFactory register
>> SEVERE: No way to find original stream handler for jar protocol
>> java.lang.reflect.InaccessibleObjectException: Unable to make field 
>> transient java.net.URLStreamHandler java.net.URL.handler accessible: module 
>> java.base does not "opens java.net" to unnamed module @7e0ea639
>>  at 
>> java.base/java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:387)
>>  at 
>> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:363)
>>  at 
>> java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:311)
>>  at 
>>

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

2023-02-16 Thread Michael Bien

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:


[mbien@fedora netbeans-validation]$ uname -a
Linux fedora 6.0.10-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 26 
16:55:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

[mbien@fedora netbeans-validation]$ java -version
openjdk version "17.0.5" 2022-10-18
OpenJDK Runtime Environment (Red_Hat-17.0.5.0.8-1.fc37) (build 17.0.5+8)
OpenJDK 64-Bit Server VM (Red_Hat-17.0.5.0.8-1.fc37) (build 17.0.5+8, 
mixed mode, sharing)


[mbien@fedora netbeans-validation]$ netbeans
which: no javac in 
(/home/mbien/.local/bin:/home/mbien/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)

WARNING: package com.apple.eio not in java.desktop
java.lang.UnsatisfiedLinkError: Can't load library: 
/usr/lib/jvm/java-17-openjdk-17.0.5.0.8-1.fc37.x86_64/lib/libawt_xawt.so

    at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2393)
    at java.base/java.lang.Runtime.load0(Runtime.java:755)
    at java.base/java.lang.System.load(System.java:1953)
    at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
    at 
java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(NativeLibraries.java:388)
    at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:232)
    at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:174)
    at 
java.base/jdk.internal.loader.NativeLibraries.findFromPaths(NativeLibraries.java:315)
    at 
java.base/jdk.internal.loader.NativeLibraries.loadLibrary(NativeLibraries.java:285)

    at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2398)
    at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:818)
    at java.base/java.lang.System.loadLibrary(System.java:1989)
    at 
java.desktop/sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:63)
    at 
java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
    at 
java.desktop/sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:60)
    at 
java.desktop/sun.awt.PlatformGraphicsInfo.createGE(PlatformGraphicsInfo.java:36)
    at 
java.desktop/java.awt.GraphicsEnvironment$LocalGE.createGE(GraphicsEnvironment.java:93)
    at 
java.desktop/java.awt.GraphicsEnvironment$LocalGE.(GraphicsEnvironment.java:84)
    at 
java.desktop/java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:106)

    at org.netbeans.core.startup.Main.start(Main.java:249)
    at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98)
    at java.base/java.lang.Thread.run(Thread.java:833)


the lib appears to be missing:

[mbien@fedora netbeans-validation]$ ls -l 
/usr/lib/jvm/java-17-openjdk-17.0.5.0.8-1.fc37.x86_64/lib/

total 140284
-rw-r--r--. 1 root root 71374 Oct 20 15:20 classlist
-rwxr-xr-x. 1 root root 19336 Oct 20 15:26 jexec
drwxr-xr-x. 1 root root    44 Dec  1 08:02 jfr
-rw-r--r--. 1 root root    110509 Oct 20 15:20 jrt-fs.jar
-rwxr-xr-x. 1 root root 27344 Oct 20 15:26 jspawnhelper
-rw-r--r--. 1 root root    29 Oct 20 15:20 jvm.cfg
-rwxr-xr-x. 1 root root 19480 Oct 20 15:26 libattach.so
-rwxr-xr-x. 1 root root 75488 Oct 20 15:26 libawt_headless.so
-rwxr-xr-x. 1 root root   1066208 Oct 20 15:26 libawt.so
-rwxr-xr-x. 1 root root 43784 Oct 20 15:26 libdt_socket.so
-rwxr-xr-x. 1 root root 20616 Oct 20 15:26 libextnet.so
-rwxr-xr-x. 1 root root   2834624 Oct 20 15:26 libfontmanager.so
-rwxr-xr-x. 1 root root    944672 Oct 20 15:26 libfreetype.so
-rwxr-xr-x. 1 root root 80128 Oct 20 15:26 libinstrument.so
-rwxr-xr-x. 1 root root 66032 Oct 20 15:26 libj2gss.so
-rwxr-xr-x. 1 root root 26888 Oct 20 15:26 libj2pcsc.so
-rwxr-xr-x. 1 root root    131736 Oct 20 15:26 libj2pkcs11.so
-rwxr-xr-x. 1 root root 17056 Oct 20 15:26 libjaas.so
-rwxr-xr-x. 1 root root    300544 Oct 20 15:26 libjavajpeg.so
-rwxr-xr-x. 1 root root    295576 Oct 20 15:26 libjava.so
-rwxr-xr-x. 1 root root    386296 Oct 20 15:26 libjdwp.so
-rwxr-xr-x. 1 root root    166952 Oct 20 15:26 libjimage.so
-rwxr-xr-x. 1 root root    142936 Oct 20 15:26 libjli.so
-rwxr-xr-x. 1 root root 19008 Oct 20 15:26 libjsig.so
-rwxr-xr-x. 1 root root    121096 Oct 20 15:26 libjsound.so
-rwxr-xr-x. 1 root root    874632 Oct 20 15:26 libjsvml.so
-rwxr-xr-x. 1 root root    656168 Oct 20 15:26 liblcms.so
-rwxr-xr-x. 1 root root 17368 Oct 20 15:26 libmanagement_agent.so
-rwxr-xr-x. 1 root root 51256 Oct 20 15:26 libmanagement_ext.so
-rwxr-xr-x. 1 root root 44456 Oct 20 15:26 libmanagement.so
-rwxr-xr-x. 1 root root    659000 Oct 20 15:26 libmlib_image.so
-rwxr-xr-x. 1 root root    147352 Oct 20 15:26 libnet.so
-rwxr-xr-x. 1 root root    151520 Oct 20 15:26 libnio.so
-rwxr-xr-x. 1 root root 17960 Oct 20 15:26 libprefs.so
-rwxr-xr-x. 1 root root 16728 Oct 20 15:26 librmi.so
-rwxr-xr-x. 1 root root    210448 Oct 20 15:26 libsaproc.so

[VOTE] Release Apache NetBeans 17

2023-02-16 Thread Neil C Smith

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.

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/

-- 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

In particular, you should (at least) follow these steps.

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

Additional info (optional) - any specifics on what you've tested

Thank you to all contributors for all your hard work!

Apache NetBeans release team

-
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)

2023-02-16 Thread Michael Bien

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".


best regards,

-mbien


On 16.02.23 13:14, Eric Barboni wrote:

Hi,

As a manner to have umbrella on issue for entreprise/javaee , I've set up a 
github project https://github.com/orgs/apache/projects/226

I'm not sure it's helpfull but better to test before discarding, if commiter 
want admin access let me know.

Best Regards
Eric
-Message d'origine-
De : Josh Juneau 
Envoyé : mercredi 15 février 2023 23:39
À : dev@netbeans.apache.org
Objet : Re: 17 blocker? — [apache/netbeans] no library found for namespace 
http://omnifaces.org/ui (Issue #4976)

Apologies for not checking the Omnifaces library previously.  Omnifaces is NOT 
working...you are correct.  I just tried to add that library and it is not recognizing it 
properly.  I also do not believe that xmlns:h="jakarta.faces.html" works as it 
should with Jakarta EE 10.  I do not believe that this is a blocker, but full Jakarta 
Faces functionality is incomplete without these working properly.

Thanks

Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
Apress Author 



On Wed, Feb 15, 2023 at 4:28 PM Geertjan Wielenga 
 wrote:


What about omnifaces?

Gj

On Wed, 15 Feb 2023 at 23:26, Josh Juneau  wrote:


To All,

First, I want to thank everyone who has put forth efforts for the
Jakarta EE support in Apache NetBeans.  Jose Contreras, Gaurav
Gupta, and others have put forth a lot of effort for this (and past) releases.

I just tested and I have no issues with primefaces namespace on NB

17-RC3.

Below are the namespaces I have declared in my JSF view, and there
are no
errors:

http://www.w3.org/1999/xhtml;
   xmlns:h="http://xmlns.jcp.org/jsf/html;
   xmlns:p="http://primefaces.org/ui;
   xmlns:f="http://xmlns.jcp.org/jsf/core;>

My suggestion is to create a new NetBeans workspace and start from

scratch

to try and create a new project.  Also, be sure you have added the
primefaces dependency to your project:

 
 org.primefaces
 primefaces
 12.0.0
 jakarta
 

Thanks for another great Apache NetBeans release.

Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
Apress Author 



On Wed, Feb 15, 2023 at 3:19 PM Matthias Bläsing
 wrote:


Hi,

Am Mittwoch, dem 15.02.2023 um 10:21 +0100 schrieb Geertjan Wielenga:

OK, let’s prioritize for the next release and note as a known
error

to

be

fixed ASAP since it blocks all usage of Java/Jakarta EE.

this needs people adding support for the jackarta namespace. This
might or might not be hard. We need to see.

I don't see this as a release blocker.

The reason is, that Oracle dropped development of JavaEE and
transfered the source code to the Eclipse Foundation. Instead of
doing the right
thing: Donate the naming rights to them to, they did the insane thing:
They donated the source code, but required the implementations to
switch package names and XSD namespaces. This is wrong on so many
levels.On that day a lot of cute kittens died an gruesome death.

Greetings

Matthias


--
--- 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: [LAZY CONSENSUS] single vote thread for NetBeans 17

2023-02-16 Thread Neil C Smith

OK, closing this off as decided.  Thanks all!  Vote thread is inbound
and on approach.

Neil

On Sat, 11 Feb 2023 at 08:03, ehsavoie  wrote:
>
> +1
> --
> Emmanuel Hugonnet
> http://www.ehsavoie.com
> http://twitter.com/ehsavoie
>
>
> On Sat, Feb 11, 2023 at 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 discussed issues and delays caused by running
> > > multiple voting threads on the various convenience binaries, we'd like
> > > to try a single voting thread covering all artefacts for NetBeans 17.
> > > We can then review after the release.
> > >
> > > Eric and I have put together a vote email template here -
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Voting+template
> > >
> > > The primary change is to include a voting form similar to that used by
> > > OpenOffice, to be copied into and filled out with every vote.  As well
> > > as voting +1 or -1 on the release, we'll ask you to tick off which
> > > artefacts you've checked with JDK and OS info where appropriate.
> > > Validating the sources will remain a requirement for voting - checking
> > > every convenience binary will not.
> > >
> > > Adding as a lazy consensus thread in case anyone wishes to -1 with
> > > concerns before we proceed.  +1's welcomed but not required.
> > >
> > > We should hopefully be in a position to run the release vote next week.
> > >
> > > Thanks and 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

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

2023-02-16 Thread Richard Grin


Hello,

About Jakarta EE, especially JSF: 
https://github.com/apache/netbeans/discussions/5510


Best regards,

Richard

Le 16/02/2023 à 13:14, Eric Barboni a écrit :

Hi,

As a manner to have umbrella on issue for entreprise/javaee , I've set up a 
github project https://github.com/orgs/apache/projects/226

I'm not sure it's helpfull but better to test before discarding, if commiter 
want admin access let me know.

Best Regards
Eric
-Message d'origine-
De : Josh Juneau 
Envoyé : mercredi 15 février 2023 23:39
À : dev@netbeans.apache.org
Objet : Re: 17 blocker? — [apache/netbeans] no library found for namespace 
http://omnifaces.org/ui (Issue #4976)

Apologies for not checking the Omnifaces library previously.  Omnifaces is NOT 
working...you are correct.  I just tried to add that library and it is not recognizing it 
properly.  I also do not believe that xmlns:h="jakarta.faces.html" works as it 
should with Jakarta EE 10.  I do not believe that this is a blocker, but full Jakarta 
Faces functionality is incomplete without these working properly.

Thanks

Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
Apress Author 



On Wed, Feb 15, 2023 at 4:28 PM Geertjan Wielenga 
 wrote:


What about omnifaces?

Gj

On Wed, 15 Feb 2023 at 23:26, Josh Juneau  wrote:


To All,

First, I want to thank everyone who has put forth efforts for the
Jakarta EE support in Apache NetBeans.  Jose Contreras, Gaurav
Gupta, and others have put forth a lot of effort for this (and past) releases.

I just tested and I have no issues with primefaces namespace on NB

17-RC3.

Below are the namespaces I have declared in my JSF view, and there
are no
errors:

http://www.w3.org/1999/xhtml;
   xmlns:h="http://xmlns.jcp.org/jsf/html;
   xmlns:p="http://primefaces.org/ui;
   xmlns:f="http://xmlns.jcp.org/jsf/core;>

My suggestion is to create a new NetBeans workspace and start from

scratch

to try and create a new project.  Also, be sure you have added the
primefaces dependency to your project:

 
 org.primefaces
 primefaces
 12.0.0
 jakarta
 

Thanks for another great Apache NetBeans release.

Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
Apress Author 



On Wed, Feb 15, 2023 at 3:19 PM Matthias Bläsing
 wrote:


Hi,

Am Mittwoch, dem 15.02.2023 um 10:21 +0100 schrieb Geertjan Wielenga:

OK, let’s prioritize for the next release and note as a known
error

to

be

fixed ASAP since it blocks all usage of Java/Jakarta EE.

this needs people adding support for the jackarta namespace. This
might or might not be hard. We need to see.

I don't see this as a release blocker.

The reason is, that Oracle dropped development of JavaEE and
transfered the source code to the Eclipse Foundation. Instead of
doing the right
thing: Donate the naming rights to them to, they did the insane thing:
They donated the source code, but required the implementations to
switch package names and XSD namespaces. This is wrong on so many
levels.On that day a lot of cute kittens died an gruesome death.

Greetings

Matthias


--
--- 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: [apache/netbeans/rcp]

2023-02-16 Thread Michael Bien

this is caused by encapsulation violations of the java module system, 
see JEP 396. If you run it on JDK 15 or older, you should see warnings, 
anything after that will throw exceptions.


Some NetBeans modules need direct access to JDK modules.

NetBeans-the-IDE sets the following flags:
https://github.com/apache/netbeans/tree/master/nbbuild/jms-config

NetBeans RCP apps won't need all of those flags, since they usually use 
a subset of the modules NetBeans uses.


there should be many blog entries online about this topic since it isn't 
really NB specific,


best regards,
michael


On 16.02.23 11:34, Claudio Rosati wrote:

Hello all,

After some years not using NetBeans RCP (only de IDE), I’ve tried to follow the 
"NetBeans Platform Quick Start Using Maven” using NetBeans 16 with Java 19.

When I try to "Build with Dependencies” the app the following error appears at 
compilation time:

Running es.intellectusetanima.mavenplatformwordapp.ApplicationTest
Feb 14, 2023 1:09:17 PM org.netbeans.ProxyURLStreamHandlerFactory register
SEVERE: No way to find original stream handler for jar protocol
java.lang.reflect.InaccessibleObjectException: Unable to make field transient 
java.net.URLStreamHandler java.net.URL.handler accessible: module java.base does not 
"opens java.net" to unnamed module @7e0ea639
at 
java.base/java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:387)
at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:363)
at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:311)
at 
java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:180)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:174)
at 
org.netbeans.ProxyURLStreamHandlerFactory.register(ProxyURLStreamHandlerFactory.java:59)
at org.netbeans.JarClassLoader.(JarClassLoader.java:142)
at org.netbeans.MainImpl.execute(MainImpl.java:153)
at org.netbeans.MainImpl.main(MainImpl.java:60)
at org.netbeans.Main.main(Main.java:58)
at 
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at 
org.netbeans.junit.NbModuleSuite$S.runInRuntimeContainer(NbModuleSuite.java:906)
at org.netbeans.junit.NbModuleSuite$S.access$100(NbModuleSuite.java:661)
at org.netbeans.junit.NbModuleSuite$S$1.protect(NbModuleSuite.java:682)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at org.netbeans.junit.NbModuleSuite$S.run(NbModuleSuite.java:678)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at 
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:113)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

If I try to run the app, I have the previous error plus the following:

java.lang.IllegalAccessException: class org.netbeans.TopSecurityManager cannot 
access class sun.awt.AppContext (in module java.desktop) because module 
java.desktop does not export sun.awt to unnamed module @5cc73178
at 
java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:420)
at 
java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:709)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at 
org.netbeans.TopSecurityManager.makeSwingUseSpecialClipboard(TopSecurityManager.java:714)
at 
org.netbeans.core.NbLifecycleManager.advancePolicy(NbLifecycleManager.java:71)
at org.netbeans.core.GuiRunLevel.run(GuiRunLevel.java:84)
at org.netbeans.core.startup.Main.start(Main.java:316)
at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98)
at java.base/java.lang.Thread.run(Thread.java:1589)

Anyway, the application starts.

The same happens using the alternative way of building an RCP app (i.e. using 
Ant-based development, as in NetBeans Platform Quick Start for NetBeans 
Platform).

[apache/netbeans/rcp]

2023-02-16 Thread Claudio Rosati

Hello all,

After some years not using NetBeans RCP (only de IDE), I’ve tried to follow the 
"NetBeans Platform Quick Start Using Maven” using NetBeans 16 with Java 19.

When I try to "Build with Dependencies” the app the following error appears at 
compilation time:

Running es.intellectusetanima.mavenplatformwordapp.ApplicationTest
Feb 14, 2023 1:09:17 PM org.netbeans.ProxyURLStreamHandlerFactory register
SEVERE: No way to find original stream handler for jar protocol
java.lang.reflect.InaccessibleObjectException: Unable to make field transient 
java.net.URLStreamHandler java.net.URL.handler accessible: module java.base 
does not "opens java.net" to unnamed module @7e0ea639
at 
java.base/java.lang.reflect.AccessibleObject.throwInaccessibleObjectException(AccessibleObject.java:387)
at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:363)
at 
java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:311)
at 
java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:180)
at java.base/java.lang.reflect.Field.setAccessible(Field.java:174)
at 
org.netbeans.ProxyURLStreamHandlerFactory.register(ProxyURLStreamHandlerFactory.java:59)
at org.netbeans.JarClassLoader.(JarClassLoader.java:142)
at org.netbeans.MainImpl.execute(MainImpl.java:153)
at org.netbeans.MainImpl.main(MainImpl.java:60)
at org.netbeans.Main.main(Main.java:58)
at 
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at 
org.netbeans.junit.NbModuleSuite$S.runInRuntimeContainer(NbModuleSuite.java:906)
at org.netbeans.junit.NbModuleSuite$S.access$100(NbModuleSuite.java:661)
at org.netbeans.junit.NbModuleSuite$S$1.protect(NbModuleSuite.java:682)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at org.netbeans.junit.NbModuleSuite$S.run(NbModuleSuite.java:678)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:90)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at 
java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:578)
at 
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at 
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at 
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:113)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)

If I try to run the app, I have the previous error plus the following:

java.lang.IllegalAccessException: class org.netbeans.TopSecurityManager cannot 
access class sun.awt.AppContext (in module java.desktop) because module 
java.desktop does not export sun.awt to unnamed module @5cc73178
at 
java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:420)
at 
java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:709)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at 
org.netbeans.TopSecurityManager.makeSwingUseSpecialClipboard(TopSecurityManager.java:714)
at 
org.netbeans.core.NbLifecycleManager.advancePolicy(NbLifecycleManager.java:71)
at org.netbeans.core.GuiRunLevel.run(GuiRunLevel.java:84)
at org.netbeans.core.startup.Main.start(Main.java:316)
at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98)
at java.base/java.lang.Thread.run(Thread.java:1589)

Anyway, the application starts.

The same happens using the alternative way of building an RCP app (i.e. using 
Ant-based development, as in NetBeans Platform Quick Start for NetBeans 
Platform).

Now, how can I get rid of these errors? Do I need a moodule-info.java file? If 
yes, where? Otherwise?

Claudio


_

Claudio Rosati

Calle Tamara 7
Villa Jinámar
35220 Telde, Gran Canaria
España
Skype:  claudio.rosati
Phone:  +34 638 579 990 (mobile)
E-mail: claudio.ros...@mac.com
_

EMAIL CONFIDENTIALITY NOTICE
This message is private and confidential. 
If you have received this message in error, 
please notify me and remove it from your system.
_

Junit5 @Nested

2023-02-16 Thread Chris Luff

Hey all, I encountered a project using the @Nested annotation for test classes;

class ProjectTests {
@Nested
class HappyPath {
@Test
void test_this_happy() {
System.out.println(“Happiness);
}
}
@Nested
class SadPath {
@Test
void test_this_sad() {
System.out.println(“Sadness);
}
}
}

I was attempting to debug one of the nested tests and noted that nothing is 
executed. I have the surefire config;


org.apache.maven.plugins
maven-surefire-plugin







org.junit.jupiter
junit-jupiter-engine
${junit.jupiter.version}




NetBeans is executing;
mvn 
-Dtest=com.cerner.ukdev.mars.dataaccess.ProjectTests#test_this_happy 
-Pdevelopment process-test-classes surefire:test

This means the test is not found. On the command line I can run;
mvn 
-Dtest=com.cerner.ukdev.mars.dataaccess.ProjectTests\$HappyPath#test_this_happy 
-Pdevelopment process-test-classes surefire:test

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? 
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?

Thoughts welcome.
Chris

[1]: https://github.com/apache/netbeans/pull/1069

Re: Rust, anyone?

2023-02-16 Thread 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

Re: Rust, anyone?

2023-02-16 Thread John Kostaras

I would vote for b2) for various reasons: the baseline doesn't depend on
rust development, many people can develop independently using pull
requests, open the bugs in github instead of communicating them in emails.
Minus: the burden to add it to the plugins repo (or will it be integrated
in the core when ready)?

On Thu, Feb 16, 2023 at 8:02 AM Antonio  wrote:

> Hi again,
>
> So, to clarify:
>
> a) I don't think Rust support is ready yet to be merged with core: it's
> in alpha state ([1] details some aspects that need work).
>
> b) If we want to add Rust support to NetBeans we have to decide the best
> way:
>
> b.1) Create a "rust" branch in the main repo, add code there and keep on
> improving it until things are ready to merge in core.
>
> b.2) Create a repo of ours and let "rust" be an experimental plugin, and
> keep on improving it there.
>
> b.3) Keep on upgrading in my cloned repo until we're all happy.
>
> We could start by deciding which option in "b)" best suites us. This may
> apply also to future "NetBeans experiments" that we may want to get
> involved into.
>
> Cheers,
> Antonio
>
> [1]
> An assorted list of bugs and features that we could add to Rust:
>
> 1. Lexer/Parser bugs
>
> 1.1. Lexer/parser are too detailed for an IDE, I think. We may not be
> interested in lexing the internals of a comment, for instance. We may
> want to simplify things.
>
> 1.2. We should recover nicely from Antlr4 lexer/parser errors. We
> currently don't. (add arbitrary text to a .rs file and see how it fails)
>
> 2. Project/Properties/Licenses
>
> The "Project/Properties/Licenses" (dependency to Ant Projects) dialog
> opens, let's you choose a license, but then forgets. Licenses are never
> applied to new files.
>
> 3. Project/Properties/Other
>
> We need customizers for Rust projects. Choosing between Debug and
> Release configurations, for instance.
>
> 4. Workspaces
>
> Rust projects with workspaces (such as
> https://github.com/rust-lang/regex) show the different Rust submodules
> in the "Sources" node. We may want to handle these as we do with "Maven
> Submodules".
>
> 5. Fonts & Colors
>
> We want to add more fonts-colors to different tokens (macros, etc.)
>
> 6. Folding
>
> Folds work for code blocks, but structs is missing.
>
> 7. Debugging
>
> Before adding debugging, we need to extract the "gdb" support from the
> "cnd" branch and add it somewhere in NetBeans. Maybe "ide/gdb*" is a
> good destination?
>
> 8. Semantic HL
>
> We may want to add semantic highlighting to different parts of the Rust
> code (special coloring for mutable reference variables, for instance).
>
> 9. Options dialog
>
> To select the "cargo" path.
>
> 10. Fonts and Colors dialog
>
> With a sample .rs file, so people can modify fonts-colors easily.
>
> 11. Code completion
>
> Of course. "rust-analyzer" (https://rust-analyzer.github.io/) is a
> popular LSP server, I think.
>
>
> On 15/2/23 22:21, Antonio wrote:
> > Hi,
> >
> > It's currently integrated in my repo . Whether this goes to core and
> > is released as a plugin is not clear yet, I think. That needs some
> > thought. Releasing it as a plugin has the advantage that it can have a
> > different lifecycle than the core.
> >
> > On 15/2/23 19:48, John Kostaras wrote:
> >> This is integrated into the core.
>
> -
> 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
>
>
>
>

official youtube channel reniew request

Re: Rust, anyone?

Re: Rust, anyone?

Re: [VOTE] Release Apache NetBeans 17

Re: [VOTE] Release Apache NetBeans 17

No communication from plugin portal verifiers (do we need to drop plugin portal?)

Re: [VOTE] Release Apache NetBeans 17

Re: [VOTE] Release Apache NetBeans 17

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

Re: [apache/netbeans/rcp]

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

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

Re: [VOTE] Release Apache NetBeans 17

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

Re: [apache/netbeans/rcp]

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

[VOTE] Release Apache NetBeans 17

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

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

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

Re: [apache/netbeans/rcp]

[apache/netbeans/rcp]

Junit5 @Nested

Re: Rust, anyone?

Re: Rust, anyone?

25 matches

Site Navigation

Mail list logo

Footer information