Re: plugin verification and new NB releases

[Ernie Rael]

On 6/14/22 10:23 AM, Michael Bien wrote:

Hello,

I forgot to request verification of my little plugin for NB 13. Then i 
was wondering - I bet some don't even know that they have to request 
verification after every NetBeans release, otherwise it won't appear 
in the plugin manager.


Thanks for mentioning this. I usually forget. Thought I'd add a request 
for NB-14 while I was thinking about it; but alas, new version's not 
there yet.


Might be good to add a version button for a new release early in the 
process, maybe during RC.




Searching through the plugin portal showed some useful plugins which 
weren't verified since NB 12.


Could this be automated? Lets say there is a successful verification 
for NetBeans N-1, it would automatically request verification for N on 
release.


I'd guess it's very rare that a plugin stops working. If an automatic 
extension to the next release, or something like that, isn't acceptable, 
then the automated request seems useful.


There was some discussion around this in the "Postmortem 12.5" thread, 
when the new versioning scheme came about


   https://lists.apache.org/thread/fzojvpgh6kboh99qfpc22x66wx7jccf9

and there is some discussion about how to specify plugin compatibility, 
including a suggestion from Jaroslav Tulach,


   https://issues.apache.org/jira/browse/NETBEANS-5064

It's a shame some plugins are almost lost, I still keep the license 
changer around.




This would increase workload for the verifiers I suppose. There is 
probably also the argument to be made that the plugin maintainers 
should care about their plugins and not forget things like I do.


Maybe an automated mail to the maintainers as notification to 
re-request verification?


I'd find that useful.

-ernie



best regards,

michael



-
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: How to build/configure NetBeans for local use

[John Neffenger]

On 6/14/22 11:28 AM, Ernie Rael wrote:
I built nb based on current delivery branch for local use (I see that 
release140 is now available). I'd like to know what difference there is 
from this to what is released.


I build from the 'release140' branch on GitHub, and below are the 
differences between the sources of that Git branch and the sources used 
to build the official NetBeans release (as of the 14-rc6 date):


$ diff -qr ./ ~/opt/netbeans-14-rc6-src/
Only in ./: contrib
Only in ./cpplite: README.md
Only in /home/john/opt/netbeans-14-rc6-src/: DEPENDENCIES
Only in ./enterprise: performance.javaee
Only in ./enterprise: performance.scripting
Only in ./enterprise: performance.web
Only in ./ergonomics: performance.ergonomics
Only in ./java: build.xml
Only in ./java: performance
Only in ./java: performance.java
Files ./LICENSE and /home/john/opt/netbeans-14-rc6-src/LICENSE differ
Only in /home/john/opt/netbeans-14-rc6-src/: licenses
Only in /home/john/opt/netbeans-14-rc6-src/nbbuild: gitinfo.properties
Only in /home/john/opt/netbeans-14-rc6-src/nbbuild: netbeansrelease.json
Files ./NOTICE and /home/john/opt/netbeans-14-rc6-src/NOTICE differ

It makes me nervous that we're shipping a release of NetBeans that is 
built from source code with no relation to a branch or release tag on 
GitHub. We're losing the cryptographic guarantee on the source code 
provided by the Git commit hashes.


That's how the SolarWinds supply-chain attack happened -- by modifying 
source code files during the build process, away from the eyes of all 
the developers tracking the source code under version control.


I've no idea where/how these changes are made to the repo build for 
release. Where to look?


Look here:

Build #27 (Jun 1, 2022 1:45:59 PM)
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release140/27/

Download the "consoleText" file from the link called "View as plain 
text" on the left. Then look for the creation of the archive file 
"release-src-666.zip".


You'll find that the sources used to build the official NetBeans release 
are created by this Ant command:


$ ant build-source-config -Dcluster.config=release \
  -Dbuildnum=666 -Dmetabuild.branch=release140

The Ant task is defined here:

target name="build-source-config" ...
https://github.com/apache/netbeans/blob/master/nbbuild/build.xml#L1663

John

-
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

How to build/configure NetBeans for local use

[Ernie Rael]

I built nb based on current delivery branch for local use (I see that 
release140 is now available). I'd like to know what difference there is 
from this to what is released.


I know about the plugin update centers. And I can live with the window 
title. And I've seen -J-Dnetbeans.logger.console=true -J-ea.


I'd like to know what other, if any, changes. Particularly how the 
runtime is effected, in addition to the "-ea" option.


I've no idea where/how these changes are made to the repo build for 
release. Where to look?


-ernie


-
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

plugin verification and new NB releases

[Michael Bien]

Hello,

I forgot to request verification of my little plugin for NB 13. Then i 
was wondering - I bet some don't even know that they have to request 
verification after every NetBeans release, otherwise it won't appear in 
the plugin manager.


Searching through the plugin portal showed some useful plugins which 
weren't verified since NB 12.


Could this be automated? Lets say there is a successful verification for 
NetBeans N-1, it would automatically request verification for N on release.


This would increase workload for the verifiers I suppose. There is 
probably also the argument to be made that the plugin maintainers should 
care about their plugins and not forget things like I do.


Maybe an automated mail to the maintainers as notification to re-request 
verification?


best regards,

michael


-
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: NB 14 tags and home page update

[Geertjan Wielenga]

Maybe you need to refresh the home page.

Yes, we’re updating things now and announcements will be going out as well.

Gj

On Tue, 14 Jun 2022 at 18:30, Rangi Keen  wrote:

> It looks like the NetBeans 14 release is now available to download,
> but the home
> page  is still advertising 13 and there are
> no tags on github  for the
> release. The NB 13 tags were missing last release (fixed with #3779
> ), so perhaps the process
> needs to be updated to ensure that step isn't missed in future. Apologies
> if these steps are planned but not yet done for NB 14.
>
> Thanks,
> Rangi
>

Re: netbeans-antlr pluging, click on the current editor event

[Ernie Rael]

Presumably, the primary issue is getting hold of the editor component so 
that you can add a mouse listener.


One approach is to add listener to the EditorRegistry.

   
https://bits.netbeans.org/dev/javadoc/org-netbeans-modules-editor-lib2/org/netbeans/api/editor/EditorRegistry.html

and use the FOCUS_GAINED_PROPERTY. This conveniently also has the 
previous editor if you want to remove a listener.


-ernie


On 6/14/22 6:30 AM, Peter Cheung wrote:

Dear Sir/Madam
  I want to enhance my netbeans-antlr plugin 
(https://gitlab.com/quantr/toolchain/netbeans-antlr) by allowing people to 
click on the editor and highlight the token in the tree view. How can I 
subscribe the click event of the current editor?


Thanks

>From Peter (System Architect, Quantr Limited https://www.quantr.hk , Mobile : 
96554595)




-
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

NB 14 tags and home page update

[Rangi Keen]

It looks like the NetBeans 14 release is now available to download,
but the home
page  is still advertising 13 and there are
no tags on github  for the
release. The NB 13 tags were missing last release (fixed with #3779
), so perhaps the process
needs to be updated to ensure that step isn't missed in future. Apologies
if these steps are planned but not yet done for NB 14.

Thanks,
Rangi

error to create a javafx folder

[Lucas Daniel Monteiro de Sousa]

when i try do create a javafx folder, it shows this message, can you help
me?

-
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

netbeans-antlr pluging, click on the current editor event

[Peter Cheung]

Dear Sir/Madam
 I want to enhance my netbeans-antlr plugin 
(https://gitlab.com/quantr/toolchain/netbeans-antlr) by allowing people to 
click on the editor and highlight the token in the tree view. How can I 
subscribe the click event of the current editor?


Thanks

>From Peter (System Architect, Quantr Limited https://www.quantr.hk , Mobile : 
>96554595)