Re: NetBeans 15 performance improvements

[Alessandro]

Great to hear this!

And by the way, this kind of development activity summary would be greatly
appreciated in the release announcement.

Kind Regards
—
Alex

Il giorno sab 30 lug 2022 alle 19:46 Michael Bien  ha
scritto:

> Hello devs,
>
> NetBeans 15 is coming with some performance improvements, it should be
> easy to see by comparing a NB 15 release candidate with NB 14 side by
> side (if you know where to look).
>
>
> maven related:
>
>   - the index folder should be smaller (by almost 1 GB last time I
> checked) #3558
>
>   - indexing of local repos should be about 20% faster (although the
> main bottleneck is the extraction/indexing of the (remote) central index
> which is still slow and makes the improvement not very noticeable) #4095
>
>   - completion in maven poms for artifacts, group ids and versions
> should all be faster (sometimes significantly faster). There is one
> exception, the first query for group ids (specifically) might be a
> little slower, but subsequent queries should be at least as fast again.
> #3558 #4136
>
>   - this applies to all kinds of index queries, but completion will be
> probably most noticeable
>
> java editor:
>
>   - Michael Zucchi contributed an optimization which improves the
> performance of a core utility class. This improves completion
> performance significantly on classes with a lot of fields (as sometimes
> seen in OpenGL/Vulkan and other library bindings). Since this is part of
> utilities used by other features, it might also improve performance
> elsewhere too.  #4142
>
>   - Michael (not me) also improved the output window performance of ant
> projects #4180
>
> javascript:
>
>   - Matthias tagged two javascrpt PRs with performance #4324, #4313, but
> I wasn't really involved there so I don't know the details or where to
> look to notice a difference.
>
> php tests (honorable mention):
>
>   - php editor tests run more than twice as fast now (~2h -> ~40min) and
> are no longer the slowest CI job #4284
>
>
> list of integrated performance PRs:
>
>
> https://github.com/apache/netbeans/issues?q=label%3Aperformance+is%3Aclosed+milestone%3ANB15
>
>
> (also keep in mind that NetBeans 14 and 15 can both already run on JDK
> 18, so you can get a little bit of free performance out of this just by
> keeping your JDK up2date)
>
> 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
>
>
>
> --
*--*
*Alessandro Falappa*

Re: [VOTE] Release Apache NetBeans 12.4 Linux Installer

[Alessandro]

+1

Verified checksum
Installed on Ubuntu 18.04 with OpenJDK11 leaving out PHP cluster
Started NB trough application icon added by installer
Activated most features and made some Options changes (such as LookAndFeel)
Successfully opened a Maven project, compiled and run it
Made some Java editing

Regards,
*--*
*Alessandro Falappa*


Il giorno gio 20 mag 2021 alle ore 12:23 Eric Barboni  ha
scritto:

> Hi,
>
>
>
> We can vote for Apache NetBeans 12.4 Linux installer.
>
>
>
> Primary voting artefact:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-installers/lin
> ux/Apache-NetBeans-12.4-bin-linux-x64.sh
> <https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-installers/linux/Apache-NetBeans-12.4-bin-linux-x64.sh>
>
>
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
>
>
> PGP signature file:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-installers/lin
> ux/Apache-NetBeans-12.4-bin-linux-x64.sh.asc
> <https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-installers/linux/Apache-NetBeans-12.4-bin-linux-x64.sh.asc>
>
>
>
> SHA512 checksum file
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-installers/lin
> ux/Apache-NetBeans-12.4-bin-linux-x64.sh.sha512
> <https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-installers/linux/Apache-NetBeans-12.4-bin-linux-x64.sh.sha512>
>
>
>
> Built locally using the artefacts found in the Jenkins job:
>
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/
> release124/22/
> <https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release124/22/>
>
>
>
> This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as
> usual. Please mark your vote with (binding) if you're an Apache NetBeans
> PMC
> member.
>
>
>
> Apache NetBeans-12.4 Linux Installer will be released if and when this vote
> passes.
>
>
>
> Best Regards
>
>
>
> Eric
>
>

Re: How to release plugin for multiple netbeans version

[Alessandro]

Hi Rahul,
  if you are depending on NB platform artifacts version 12.0 your plugin is
compatible with NB 12.0, 12.1 and 12.2.

If you are asking how to have your plugin listed in the Update Center
(Tools > Plugins > Available Plugins) you have to upload it to the NetBeans
Plugin Portal (https://plugins.netbeans.apache.org/) and request
verification for NB v12.

Publishing a plugin on the Plugin Portal is described here:
https://cwiki.apache.org/confluence/display/NETBEANS/How+to+get+plugin+on+Plugin+Portal+Update+Center

Regards,
*--*
*Alessandro Falappa*


Il giorno dom 6 dic 2020 alle ore 13:31 Rahul Khandelwal <
rahulne...@gmail.com> ha scritto:

> Hi All,
>
> I have created a netbeans plugin for toml files.
> There is still some polishing pending for which I may need help from
> community.
>
> Meanwhile I wanted to know how to publish the plugin for multiple netbeans
> versions?
> The netbeans dependencies are version 12.0 in pom file if that is relevant.
>
> Regards,
> Rahul khandelwal
>

Re: Re: Plugin verification

[Alessandro]

Hi Eric,
  my answers below.

Regards
*--*
*Alessandro Falappa*


Il giorno sab 5 dic 2020 alle ore 17:38 Eric Bresie  ha
scritto:

> So does that still mean a new version of the plug-in can or cannot be used
> / verified against an old version of Netbeans?
>

No, an old plugin version can be verified against an old version of NB.


> In other words, should a given plugin version show which versions of
> Netbeans it’s compatible against?
>

This is up to the plugin developer. For example if my plugin version X+1
would support Gradle projects I could verify it against NB12 but leave
version X verified against NB11.


> Eric Bresie
> ebre...@gmail.com (mailto:ebre...@gmail.com)
>

Re: Plugin verification

[Alessandro]

Hi all,
Junichi's suggestion is correct and my reasoning is wrong.

At any given time there is a single verified plugin version for one
NetBeans version.
This sound reasonable and allows for example to have a former version of a
plugin verified for an older version of NetBeans while a newer version of a
plugin verified for a newer version of NetBeans.

Verification requested and under way, If you are a plugin verifier  please
approve!

Regards,
*--*
*Alessandro Falappa*


Il giorno ven 4 dic 2020 alle ore 11:36 Alessandro 
ha scritto:

> Hi Junichi,
>   this means a plugin cannot be verified for multiple NetBeans versions?
>
> If I understood it correctly after verification the plugin, or its new
> version thereof, "appears" on the UpdateCenter, if I remove the
> verification it "disappears" from the UpdateCenter. This would mean that as
> soon as a plugin is verified for the latest version of NetBeans it
> disappears for the users of previous versions. Sounds like an important
> limitation to me.
>
> Anyway I will try your suggestion.
>
> Thanks for helping,
> Regards
>
> *--*
> *Alessandro Falappa*
>
>
> Il giorno ven 4 dic 2020 alle ore 11:25 Junichi Yamamoto <
> junichi0...@gmail.com> ha scritto:
>
>> Hi,
>>
>> Please try to drop verification for the old version. Then, try to go
>> to the new version page.
>>
>> HTH,
>> Junichi
>>
>> On Sun, Nov 29, 2020 at 9:16 PM Alessandro 
>> wrote:
>> >
>> > Hi all,
>> >   while testing the recently released NetBeans 12.2 Linux installer I
>> > noticed that in NB12.2 the older version of my NBSpringBoot plugin is
>> > available from the Update Center.
>> >
>> > I went on the new plugin portal and realized that the last version was
>> not
>> > verified while the older was but I don't seem to find a way to request
>> > verification of the last version.
>> > I went to MyPlugins section, clicked on edit button for NBSpringBoot
>> plugin
>> > then on edit button for last version, it shows the plugin enabled for NB
>> > 11.0 and 12.0 but no way to request verification, if I recall correctly
>> > there were buttons to request verification against selected NB versions.
>> >
>> > Could someone shed some light on this?
>> >
>> > Thank you in advance for your help.
>> >
>> > Regards
>> > *--*
>> > *Alessandro Falappa*
>>
>> -
>> 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: Plugin verification

[Alessandro]

Hi Junichi,
  this means a plugin cannot be verified for multiple NetBeans versions?

If I understood it correctly after verification the plugin, or its new
version thereof, "appears" on the UpdateCenter, if I remove the
verification it "disappears" from the UpdateCenter. This would mean that as
soon as a plugin is verified for the latest version of NetBeans it
disappears for the users of previous versions. Sounds like an important
limitation to me.

Anyway I will try your suggestion.

Thanks for helping,
Regards

*--*
*Alessandro Falappa*


Il giorno ven 4 dic 2020 alle ore 11:25 Junichi Yamamoto <
junichi0...@gmail.com> ha scritto:

> Hi,
>
> Please try to drop verification for the old version. Then, try to go
> to the new version page.
>
> HTH,
> Junichi
>
> On Sun, Nov 29, 2020 at 9:16 PM Alessandro  wrote:
> >
> > Hi all,
> >   while testing the recently released NetBeans 12.2 Linux installer I
> > noticed that in NB12.2 the older version of my NBSpringBoot plugin is
> > available from the Update Center.
> >
> > I went on the new plugin portal and realized that the last version was
> not
> > verified while the older was but I don't seem to find a way to request
> > verification of the last version.
> > I went to MyPlugins section, clicked on edit button for NBSpringBoot
> plugin
> > then on edit button for last version, it shows the plugin enabled for NB
> > 11.0 and 12.0 but no way to request verification, if I recall correctly
> > there were buttons to request verification against selected NB versions.
> >
> > Could someone shed some light on this?
> >
> > Thank you in advance for your help.
> >
> > Regards
> > *--*
> > *Alessandro Falappa*
>
> -
> 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: Plugin verification

[Alessandro]

Hi all,
 is this the right mailing list to discuss plugin portal issues?

Regards,
*--*
*Alessandro Falappa*


Il giorno dom 29 nov 2020 alle ore 13:16 Alessandro 
ha scritto:

> Hi all,
>   while testing the recently released NetBeans 12.2 Linux installer I
> noticed that in NB12.2 the older version of my NBSpringBoot plugin is
> available from the Update Center.
>
> I went on the new plugin portal and realized that the last version was not
> verified while the older was but I don't seem to find a way to request
> verification of the last version.
> I went to MyPlugins section, clicked on edit button for NBSpringBoot
> plugin then on edit button for last version, it shows the plugin enabled
> for NB 11.0 and 12.0 but no way to request verification, if I recall
> correctly there were buttons to request verification against selected NB
> versions.
>
> Could someone shed some light on this?
>
> Thank you in advance for your help.
>
> Regards
> *--*
> *Alessandro Falappa*
>

Re: NB12.2 - No completion of method references

[Alessandro]

Hi Matthias,
  I am running NB on OpenJDK11 freshly installed with no import of previous
settings and with no nbjavac (to test how does it work without it).
I am going to try if installing nbjavac makes any difference.

The IDE log seems clean no relevant exception logged apart from a pair of
suspicious lines:
INFO [null]: Last record repeated 2 more times.
INFO [null]: Last record repeated again.
note null instead of logger name

Regards,
*--*
*Alessandro Falappa*


Il giorno dom 29 nov 2020 alle ore 14:10 Matthias Bläsing <
mblaes...@doppel-helix.eu> ha scritto:

> Hi,
>
> works for me one a slightly modified master build. One thing you might
> try: If you have nbjavac installed, remove it. I had trouble at work
> with netbeans not providing code completion and noticed exeptions from
> javac in the logs. I removed nbjavac, run Apache Netbeans on JDK 11.0.9
> and were a happy camper afterwards.
>
> Greetings
>
> Matthias
>
> Am Sonntag, den 29.11.2020, 13:39 +0100 schrieb Alessandro:
> > Hi all,
> > could anyone confirm if method references are completed in the last
> > NB
> > release?
> >
> >
> >1. Create a simple Java 8+ project with a main class
> >2. Type for example the following code:
> >
> > Arrays.asList("One", "Two", "Three", "Four", "Five")
> > .stream()
> > .filter(s -> s.length() > 3)
> > .forEach(System.out::|); // <--invoke completion here
> >
> > If confirmed I will open a JIRA issue
> >
> > Regards,
> > *--*
> > *Alessandro Falappa*
>
>
>
> -
> 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
>
>
>
>

NB12.2 - No completion of method references

[Alessandro]

Hi all,
could anyone confirm if method references are completed in the last NB
release?


   1. Create a simple Java 8+ project with a main class
   2. Type for example the following code:

Arrays.asList("One", "Two", "Three", "Four", "Five")
.stream()
.filter(s -> s.length() > 3)
.forEach(System.out::|); // <--invoke completion here

If confirmed I will open a JIRA issue

Regards,
*--*
*Alessandro Falappa*

Plugin verification

[Alessandro]

Hi all,
  while testing the recently released NetBeans 12.2 Linux installer I
noticed that in NB12.2 the older version of my NBSpringBoot plugin is
available from the Update Center.

I went on the new plugin portal and realized that the last version was not
verified while the older was but I don't seem to find a way to request
verification of the last version.
I went to MyPlugins section, clicked on edit button for NBSpringBoot plugin
then on edit button for last version, it shows the plugin enabled for NB
11.0 and 12.0 but no way to request verification, if I recall correctly
there were buttons to request verification against selected NB versions.

Could someone shed some light on this?

Thank you in advance for your help.

Regards
*--*
*Alessandro Falappa*

Re: [VOTE] Release Apache NetBeans 12.2 Linux Installer

[Alessandro]

+1
Check signature OK
Run installer on Ubuntu 18.04 with OpenJDK11, excluded PHP OK
Run NB via system launcher OK
Not imported previous settings, activated features OK
Loaded some maven projects, built them OK
Created new maven project OK
Triggered reindex of maven repository and download of index from maven
central OK

Kudos to everyone involved and special thanks to Release Manager Laszlo
Kishalmi!

Regards
*--*
*Alessandro Falappa*


Il giorno gio 26 nov 2020 alle ore 01:08 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Dear all,
>
> The Apache NetBeans 12.2 Source bundle has been voted to be released, so
> I call the community to vote on the complimentary Linux Installer.
>
> Please check,
>
> - the checksum
> - the signature
> - does it work?
> - module version output in the IDE log contains the git commit id
> (d73d3dd898acc440c460924dabf8ad5feb90369f)
>
> The artifact we are voting on:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/Apache-NetBeans-12.2-bin-linux-x64.sh
>
> Checksum and Signature:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/Apache-NetBeans-12.2-bin-linux-x64.sh.sha512
>
> 0dd65073e9565abcd6c77acdf24cf695cf3576ce74cdef6ba42776e3cf01d30f77a8d89aef35900d186cd757549ddfd1cc51f07bb362002539042c8bbad886b1
> <https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/Apache-NetBeans-12.2-bin-linux-x64.sh.sha5120dd65073e9565abcd6c77acdf24cf695cf3576ce74cdef6ba42776e3cf01d30f77a8d89aef35900d186cd757549ddfd1cc51f07bb362002539042c8bbad886b1>
> Apache-NetBeans-12.2-bin-linux-x64.sh
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/Apache-NetBeans-12.2-bin-linux-x64.sh.asc
>
> Our KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
> Built by:
>
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release122/21/
>
> --
>Laszlo Kishalmi
>
>
> -
> 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
>
>
>
>

Maven Daemon

[Alessandro]

Hi all,
  I remember some time ago a discussion on improving Maven projects build
speed in NetBeans.
Stumbled upon this yesterday: https://github.com/mvndaemon/mvnd . It tries
to port to Maven the same concept behind the Gradle daemon.
Could an integration with the above daemon be worth pursuing to improve
Maven build speed?

Regards
*--*
*Alessandro Falappa*

Re: Status of converting icons to SVG

[Alessandro]

Hello all,
I support Erik’s plan.
Collaboration with https://opensourcedesign.net/ as pointed out by Neil
could be an alternative.

Kind Regards’
Alex

Il giorno mar 8 set 2020 alle 19:14 Eirik Bakke  ha
scritto:

> In my opinion, the ideal way to do this would be to crowdfund the effort
> and have new icons be drawn by a single paid, professional icon designer.
> I'd be interested in hearing your thoughts on this.
>
>
>
> In my experience, drawing an icon takes 30 minutes on average [1], after
> getting up to speed. Graphic designers on UpWork are perhaps $30-60/hour
> (we'd need to find someone who's qualified for this particular job). For an
> initial effort, there are about 160 icons that should be converted [2].
> Ideally, we'd find someone to do it who could later be called upon to do
> another 6-700 icons to cover most of the remaining interface, if the first
> project is a success.
>
>
>
> As an alternative, for a crowdsourced effort, I'd be happy to do a
> "training" session by Zoom to show contributors how to draw icons in
> Illustrator according to the style guide described in NETBEANS-2617. I'm
> swamped until February 2021, though...
>
>
>
> Some issues to consider:
>
> * Programming and graphic design are two different skillsets. Programmers
> do not always produce tasteful graphic designs.
>
> * In the long term, we'd want to convert at least several hundred icons,
> maybe thousands [3]. This may be beyond what is possible with a volunteer
> effort.
>
> * If too many different people work on this, we will get a hodgepodge of
> different icon styles.
>
> * Normally, cosmetic issues are not very important. But in this case, the
> purpose of the effort is to make NetBeans look good, so aesthetics is
> actually a primary concern.
>
> * From my own experience, it took about 4 hours of icon-drawing work in
> Illustrator (which I already had some experience with) before I was fully
> "up-to-speed" with designing new icons. If multiple people are working on
> the icons, each person will have to go through this learning curve.
>
> * You often end up copying and pasting shapes between different icons. If
> many people are working on the effort, they will end up redrawing shapes
> that others have already drawn.
>
> * There are lots of little issues that contributors will get wrong--e.g.
> how vertices are aligned to the pixel grid. A lot of familiarity with the
> drawing software is needed.
>
> * If many people are working on the effort, a single person will still end
> up having to go through all the Illustrator files and cleaning them up to a
> consistent standard, naming scheme etc. For the simpler icons (e.g. two
> rectangles), this takes up as much time as drawing the icon itself.
>
>
>
> -- Eirik
>
> [1] See
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements?preview=/110692909/110692926/vectorized.png
>
> [2]
> https://people.csail.mit.edu/ebakke/misc/netbeans-icons/prioritized.html
>
> [3] https://people.csail.mit.edu/ebakke/misc/netbeans-icons/
>
>
>
> -Original Message-
>
> From: Jaroslav Tulach 
>
> Sent: Tuesday, September 8, 2020 4:29 AM
>
> To: dev@netbeans.apache.org
>
> Subject: Status of converting icons to SVG
>
>
>
> Hello everyone, hello Eirik.
>
>
>
> It is a while since the [support for SVG icons](https://github.com/apache/
> netbeans/commit/
>
>
> 51a01eb9cbfc6f342a1827d47f0b37e1b2f070a3#diff-721be4afbc5aed18d39b11702d02c9fd)
>
> landed into NetBeans code base. Is it used or is it just laying around?
>
>
>
> I do remember there was an attempt to start a community supported
> conversion of the icons. What's the status of such conversion? Were some
> (at least those visible in the toolbar by default) icons converted?
>
>
>
> Maybe we should ask guys that have a say in the wider community like Jirka
> Kovalský, Geertjan, etc. to make some buzz around the conversion? Have an
> "icon-a-hack-a-ton"?
>
>
>
> Last time I asked for help with reorganizing source files layout per
> cluster, the community reacted quite well. A lot of people contributed.
> Contributing icons shall be even easier and more fun, right?
>
>
>
> -jt
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -
>
> 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
>
>
>
>
>
>
>
> --
*--*
*Alessandro Falappa*

Re: Installers for 12.1?

[Alessandro]

Hi all,
I have briefly tested NetBeans 12.1-beta3 using the Linux installer, Ubuntu
18.04, Oracle JDK 8 (yes still using that), fresh user dir, no import of
previous settings.

On first run activated some features, installed nb-javac as requested but
not restarted, switched to FlatLaf Light LAF then restarted.
Created a simple maven project, triggered indexing of maven local
repository and download and index unpack of central repository.

All OK.

Regards
*--*
*Alessandro Falappa*


Il giorno gio 20 ago 2020 alle ore 12:47 Neil C Smith 
ha scritto:

> Hi All,
>
> Think I've asked this before (or maybe just to Eric?), but I'm not
> sure what the state of play is with the installers at the moment?
>
> The CI build includes the Linux and Windows installers.  Hopefully
> some people have been testing these with the betas too?!
>
> Is the Windows installer actually ready for release or are there
> additional steps (signing?) required still?
>
> Is someone with access to macOS able to take on the installer and
> signing, etc. tasks for the macOS installer?
>
> The above as and when we have a successful voting candidate obviously,
> but be good to know we're ready.
>
> Feel free to point me at a wiki page if I've missed any info on above?! :-)
>
> Thanks,
>
> 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: Spring Support

[Alessandro]

Hi all,
  in general I don't think that now that NetBeans is an open source project
all the existing open source plugins should be integrated in it. Spring
framework and Spring Boot support in Eclipse, for example, is provided via
plugins (
https://marketplace.eclipse.org/content/spring-tools-4-aka-spring-tool-suite-4).
Having Spring support as a plugin means it is available for more than one
NetBeans version (I currently compile against NetBeans 8.2 API to encompass
as many versions as possible).

If anyone would like to contribute to the plugin feel free to do so at
https://github.com/AlexFalappa/nb-springboot. As far as feature requests
go, please consider that I develop the plugin in my free time.

I admit I haven't been very active recently but if I will find myself
unable to work on the plugin anymore I will certainly consider contributing
it to the NetBeans project as a mean of letting others continue developing
it.

Regards
*--*
*Alex Falappa*


Il giorno mer 10 giu 2020 alle ore 05:22 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Well, it depends on the plugin author Alex. He is an active member of
> the community.
>
> If he thinks it fits, then I think there would be no objection to
> integrate his plugins into NetBeans mainline.
>
> Alex?
>
> On 6/9/20 4:20 PM, Christopher Gusenbauer wrote:
> > Hi! Since you already integrated the Dark LAF, maybe you could integrate
> > another great user project as well?
> > http://plugins.netbeans.org/plugin/67888/nb-springboot
> > IntelliJ and Eclipse both offer better support for Spring and Netbeans
> for
> > me personally has always been cooler, but the lack of out of the box
> Spring
> > really hurts since its so widely used
> >
>

Re: Maven projects regression in NB 12.0

[Alessandro]

Hi all,
thanks to Christian Oyarzun for finding the root cause of the problem (see
https://issues.apache.org/jira/browse/NETBEANS-4341 for details).

We now have a workaround and Mattias Blaesing has queued a proper fix in
the codebase (https://github.com/apache/netbeans/pull/2177).

Thanks everybody.

Regards
*--*
*Alessandro Falappa*


Il giorno lun 8 giu 2020 alle ore 10:21 Alessandro 
ha scritto:

> Hi all,
>   I have added the reproduction step to the mentioned issue on Jira.
>
> With regard to NetCAT test specs where can I find them and how to
> contribute to them?
>
> Regards.
> *--*
> *Alessandro Falappa*
>
>
> Il giorno lun 8 giu 2020 alle ore 09:45 Geertjan Wielenga <
> geert...@apache.org> ha scritto:
>
>> We need steps to reproduce the problem.
>>
>> To avoid this kind of thing being discovered at the time of release, as in
>> this case, you can add test cases to the NetCAT specs, yes, even for
>> external plugins. If you don’t, no guarantees anyone will find problems in
>> time.
>>
>> Gj
>>
>> On Sun, 7 Jun 2020 at 19:40, Alessandro  wrote:
>>
>> > Hi all,
>> >   I am facing https://issues.apache.org/jira/browse/NETBEANS-4341 .
>> >
>> > The bug hinders the usability of my NBSpringBoot plugin as it manifests
>> > immediately when creating new Spring Boot projects.
>> >
>> > Has something changed recently in NB12.0 with regard to the Maven area?
>> >
>> > Apparently after a maven build and download of dependencies a project
>> > reindex is not triggered and NB thinks the project is still unloadable
>> for
>> > missing dependencies.
>> >
>> > Regards.
>> > *--*
>> > *Alessandro Falappa*
>> >
>>
>

Re: Maven projects regression in NB 12.0

[Alessandro]

Hi all,
  I have added the reproduction step to the mentioned issue on Jira.

With regard to NetCAT test specs where can I find them and how to
contribute to them?

Regards.
*--*
*Alessandro Falappa*


Il giorno lun 8 giu 2020 alle ore 09:45 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> We need steps to reproduce the problem.
>
> To avoid this kind of thing being discovered at the time of release, as in
> this case, you can add test cases to the NetCAT specs, yes, even for
> external plugins. If you don’t, no guarantees anyone will find problems in
> time.
>
> Gj
>
> On Sun, 7 Jun 2020 at 19:40, Alessandro  wrote:
>
> > Hi all,
> >   I am facing https://issues.apache.org/jira/browse/NETBEANS-4341 .
> >
> > The bug hinders the usability of my NBSpringBoot plugin as it manifests
> > immediately when creating new Spring Boot projects.
> >
> > Has something changed recently in NB12.0 with regard to the Maven area?
> >
> > Apparently after a maven build and download of dependencies a project
> > reindex is not triggered and NB thinks the project is still unloadable
> for
> > missing dependencies.
> >
> > Regards.
> > *--*
> > *Alessandro Falappa*
> >
>

Maven projects regression in NB 12.0

[Alessandro]

Hi all,
  I am facing https://issues.apache.org/jira/browse/NETBEANS-4341 .

The bug hinders the usability of my NBSpringBoot plugin as it manifests
immediately when creating new Spring Boot projects.

Has something changed recently in NB12.0 with regard to the Maven area?

Apparently after a maven build and download of dependencies a project
reindex is not triggered and NB thinks the project is still unloadable for
missing dependencies.

Regards.
*--*
*Alessandro Falappa*

Re: [VOTE] Release Apache NetBeans-12.0 Linux Installer

[Alessandro]

+1

Ubuntu 18.04 with Oracle JDK 8 u201 (an old version I know).
Installed customizing the feature set (no PHP).
No import of previous settings.
Opened a maven project compiled it and run it.

Minor things:

   - Observed same issue as Lazslo Kishalmi, in the installer the JavaSE
   feature requires HTML5/Javascript feature.
   - Another thing I noticed is that chosen features must be activated on
   first run, that was not the case previously, where the feature chosen in
   the installer got automatically activated.


Regards
*--*
*Alessandro Falappa*


Il giorno mer 3 giu 2020 alle ore 11:56 Eric Barboni  ha
scritto:

> Hi folks,
>
>
>
> Main vote is almost over,  The easiest installer for linux can be voted I
> guess (no certification request or notarizaion). Not tested myself having
> only textual linux.
>
>
>
> Primary voting artifact:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.0/vc1/installers
> /Apache-NetBeans-12.0-bin-linux-x64.sh
> <https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.0/vc1/installers/Apache-NetBeans-12.0-bin-linux-x64.sh>
>
>
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
>
>
> PGP signature file:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.0/vc1/installers
> /Apache-NetBeans-12.0-bin-linux-x64.sh.asc
> <https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.0/vc1/installers/Apache-NetBeans-12.0-bin-linux-x64.sh.asc>
>
>
>
> SHA512 checksum file
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.0/vc1/installers
> /Apache-NetBeans-12.0-bin-linux-x64.sh.sha512
> <https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.0/vc1/installers/Apache-NetBeans-12.0-bin-linux-x64.sh.sha512>
>
>
>
> Built using Jenkins job:
>
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
> ns/job/release120/23/artifact/
> <https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release120/23/artifact/>
>
>
>
> This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as
> usual.
>
> Please mark your vote with (binding) if you're an Apache NetBeans PMC
> member.
>
> Apache NetBeans-12.0 Linux Installer will be released if and when this vote
> passes.
>
>
>
> Best Regards,
>
>
>
> Eric
>
>

Re: NetBeans 12 Beta4 unable

[Alessandro]

Hi all,
  problem solved, false alarm.

On Ubuntu (and probably on Debian as well) the JDK is split in several
packages. In order for NetBeans to correctly autodetect all aspects of the
JDK the source and doc packages should be installed as well.

For example for JDK 11 at least the following packages are needed:
openjdk-11-doc
openjdk-11-jdk
openjdk-11-jdk-headless
openjdk-11-jre
openjdk-11-jre-headless
openjdk-11-source

The openjdk-11-doc can be installed afterwards (as will install the
javadocs in the /usr/lib/jvm/java-11-openjdk-amd64/docs folder I mentioned
in my first email) while the openjdk-11-source should be present before
autodetection otherwise manual addition is a bit cumbersome.

Ideally this should be mentioned somewhere on the installation
instructions/release notes.

Regards,
*--*
*Alessandro Falappa*


Il giorno mer 20 mag 2020 alle ore 17:03 John Kostaras 
ha scritto:

>  Hallo Alessandro,
>
> in Mac it displays  *https://docs.oracle.com/en/java/java13/docs/api
> <https://docs.oracle.com/en/java/java13/docs/api>* (for Java 13
> obviously).
> Same story with the other JDKs. I tried with GraalVM 8, no issue. I don't
> have any OpenJDK installed to try.
>
> Kind regards,
> John.
>
> On Wed, 20 May 2020 at 10:32, Alessandro  wrote:
>
> > Hi all,
> > I am trying the latest beta and I noticed that it is unable to properly
> > configure the Javadoc URLs of the Java platforms.
> > I am on Ubuntu 18.04 with OpenJDK 11.0.7 installed trough the OS packages
> > (openjdk-11-jdk package), I also have OpenJDK 8u252 (openjdk-8-jdk
> > package).
> > In the Java Platform Manager dialog for the JDK 11 platform I have in the
> > Javadoc tab a folder '/usr/lib/jvm/java-11-openjdk-amd64/docs' instead
> of a
> > 'http://docs.oracle.com/javase/...' URL as in the previous versions of
> > NetBeans.
> > Adding the JDK8 platform results in a similar behaviour with an
> > autoconfigured /docs folder instead of the typical URL.
> > This appear to be a regression respect to NetBeans 11.3.
> > The out of the box experience is not great, especially for newbies, as
> > documentation tooltips in the editor are not available, even for common
> > java.lang classes.
> >
> > Can anyone confirm? Could it depend on the fact that I have the OS
> > packages? Has javadoc autoconfiguration for newly added platform changed
> in
> > recent commits?
> >
> > Regards
> > --
> > *Alessandro Falappa*
> >
>

NetBeans 12 Beta4 unable

[Alessandro]

Hi all,
I am trying the latest beta and I noticed that it is unable to properly
configure the Javadoc URLs of the Java platforms.
I am on Ubuntu 18.04 with OpenJDK 11.0.7 installed trough the OS packages
(openjdk-11-jdk package), I also have OpenJDK 8u252 (openjdk-8-jdk package).
In the Java Platform Manager dialog for the JDK 11 platform I have in the
Javadoc tab a folder '/usr/lib/jvm/java-11-openjdk-amd64/docs' instead of a
'http://docs.oracle.com/javase/...' URL as in the previous versions of
NetBeans.
Adding the JDK8 platform results in a similar behaviour with an
autoconfigured /docs folder instead of the typical URL.
This appear to be a regression respect to NetBeans 11.3.
The out of the box experience is not great, especially for newbies, as
documentation tooltips in the editor are not available, even for common
java.lang classes.

Can anyone confirm? Could it depend on the fact that I have the OS
packages? Has javadoc autoconfiguration for newly added platform changed in
recent commits?

Regards
-- 
*Alessandro Falappa*

Re: Can Ligatures in fonts be turned off in Windows

[Alessandro]

Hello Ken,
Font ligatures in Java Swing are enabled with a text attribute:
https://docs.oracle.com/javase/8/docs/api/java/awt/font/TextAttribute.html

It should be certainly possible to selectively enable/disable it.
Unfortunately I have searched NB source code for LIGATURES but found
nothing relevant.

Someone more accustomed with the code of NB editor infrastructure could
tell where to intervene.

Regards,
Alex

Il giorno dom 5 apr 2020 alle 17:42 Kenneth Fogel <
kfo...@dawsoncollege.qc.ca> ha scritto:

> Not long ago I wrote about the JetBrains Mono font. I liked it but it had
> ligatures I could not turn off in NB on Windows. To the rescue came Andrew
> Podkovyrin who forked a non-ligature version at
> https://github.com/podkovyrin/JetBrainsMono/tree/feature/no-ligatures-1-0-3/no-ligatures.
> When I first discovered the font I learned, possibly incorrectly, that it’s
> the editor responsibility for disabling ligatures. It could also be a
> switch in Java. I have my solution in the forked font but I was curious,
> any suggestions?
>
>
>
> *Ken Fogel*
> Faculty
>
> email: kfo...@dawsoncollege.qc.ca
> phone: (514) 931-8731 local 4799
>
> Dawson College, 3040 Sherbrooke St. W
> 
>  Westmount, Quebec, H3Z
> 
> 1A4, Canada
>
> [image: facebook icon]  [image:
> twitter icon]  [image: youtube icon]
>  [image: linkedin icon]
>  [image: instagram icon]
> 
>
> [image: cid:16cd4bdce7eaf8d708] 
>
>
>
>
>
>

Re: Problems of (dark) FlatLaF

[Alessandro]

Hi Jaroslav,
Regarding the second one (3942) I sometimes faced it especially when
switching between color profiles or look and feels which recommend a color
profile. The colors of breakpoints and execution line are defined in the
FlatLaf color profile and are consistent with the  others.

What you are probably seeing are the colors of a light color profile. It
seems that some colors are not overwritten by the switch and kept to the
previous value.

Please try to reset them to the color profile definition by using the reset
button in the annotations tab and see if that fixes it. Unfortunately you
will lose any tweak you made after the switch.

Hope it helps.

Alex

Il giorno mer 4 mar 2020 alle 09:23 Jaroslav Tulach <
jaroslav.tul...@gmail.com> ha scritto:

> Hi.
> FlatLaF is nice, but it has few problems. I've reported:
>
> https://issues.apache.org/jira/browse/NETBEANS-3943
> https://issues.apache.org/jira/browse/NETBEANS-3942
> https://issues.apache.org/jira/browse/NETBEANS-3910
>
> Is there a guy who feels responsible for these issues?
>
> On a general note: How do we make sure FlatLaF related issues got assigned
> to the right people? What category to use? How to identify them?
> -jt
>

Re: Pull the plug from Java 8 in 12.1?

[Alessandro]

Hi all,
  I am not against it completely but in my opinion before dropping JDK 8 as
NB running JDK the following points must be addressed:

   - Compile on Save functionality still requires nb-javac (even on JDK 11)
   - Some application servers cannot run on JDK 11 this would mean needing
   a user to define a JDK 8 Java Platform only to launch such application
   servers

As pointed out in Jan Lahoda's mail it also seems that JDK 11 javac is not
on par with nb-javac as far as error recovery is concerned, this would
impact the java code editing experience.

On the positive side JDK 11 should offer some improvements of HiDPI and
fonts rendering areas that a graphical application like an IDE could
benefit from a lot.

Regards,
Alex

Il giorno gio 27 feb 2020 alle ore 02:13 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Dear all,
>
> What do you think about stopping support Java 8 as NetBeans runtime from
> 12.1 and on?
>
> Neil mentioned it in the user's chat first regarding that we have issues
> with nb-javac from time to time.
>
> As we know our mid term plan is/was to rely on javac tooling instead of
> habing to maintain the nb-javac fork.
>
> Right now NetBeans run fairly well on standard javac, however when the
> IDE is running on Java 8 we need the nb-javac.
>
> I think removing Java 8 support as runtime shall be not a big deal, it
> would be a few thing less to worry about. During the 12.x cycle we could
> perfect our stuff on Java 11.
>
>
>
>
>
> -
> 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: Features page for 11.3

[Alessandro]

Hi Gertjan,
   had a quick look to the features page and it looks good.
Only thing is in the Appearance section it's said that FlatLaf was donated
but I don't think it is correct.

I would reword that sentence as:
A strong focus of the 11.3 release is around appearance, since the NetBeans
dark look and feels support (Dark Metal and Dark Nimbus) has been donated
by Oracle to Apache, while FlatLaf, a completely new look and feel by  Karl
Tauber from FormDev Software GmbH, has been integrated. Also enhancements
for HiDPI on Windows have been introduced.

and maybe introduce a link to FlatLaf web site:
https://www.formdev.com/flatlaf/

Regards,
Alex

Il giorno mer 26 feb 2020 alle ore 10:25 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> Hi all,
>
> When we release 11.3, here's the features page we'll make available with
> the highlights drawn from our Wiki:
>
> https://netbeans.apache.org/download/nb113/index.html
>
> It's not completely complete and I'm adding more content continually --
> however, feedback is needed and especially if you've worked on the 11.3
> release in some way.
>
> Just respond with any comments you might have here or provide a PR to the
> above.
>
> Thanks,
>
> Gj
>

Re: compatibility with dark look and feel

[Alessandro]

Hi Ernie,
  the usual way to handle the choice of colors is to use
UIManager.getColor("laf_color_name") and choose a suitable "laf_color_name".
Every LAF define a set of color names, there are some basic ones (e.g.
selection, text, shadow, button face, etc.) and some widget specific ones
(e.g. button disabled text). Have a look at UIManager class javadoc here:
https://docs.oracle.com/javase/8/docs/api/javax/swing/UIManager.html section
"Defaults".

The list of available default names (which include colors) for a given LAF
is obtainable with UIManager.getDefaults().keys() . The main problem is
usually to choose a laf color name that is available in all LAFs.

A very nice HTML view of defaults for the Nimbus LAF is available at:
https://docs.oracle.com/javase/tutorial/uiswing/lookandfeel/_nimbusDefaults.html

Hope it helps.

Alex

Il giorno mer 26 feb 2020 alle ore 03:37 Ernie Rael  ha
scritto:

> The jVi plugin has two issues with the dark look and feels. Icons and
> jVi colors.
>
> I downloaded gimp and will attack the icons. The jVi colors show up in
> the jVi options dialog where you can set them, there's also a "default"
> button for each color; an example jVi color is the VisualBellColor. For
> each color I'd like to have a default compatible with the current look
> and feel.
>
> I've never worked with swing UI color and LaF stuff. Any links that
> might help me understand how to find good colors appreciated.
>
> I'd guess I need to examine the current colors/settings and use that
> info to select colors. I guess I could hardcode colors for each known
> laf, but it would be nice to have a technique that's dynamic based on
> current colors...
>
> -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
>
>
>
>

Re: [VOTE] Release Apache NetBeans 11.3 [vote candidate 2]

[Alessandro]

+1

Downloaded source archive
Checked source archive SHA digest
Unzipped source archive
Checked NOTICE, LICENSE
Verified presence of mentioned jars
Built on Ubuntu Linux 18.04 with Oracle JDK8
Run built application

Downloaded binary archive
Unzipped archive
Adjusted configuration in etc/netbeans.conf
Run application

Regards,
Alex

Il giorno ven 21 feb 2020 alle ore 19:32 Eric Barboni  ha
scritto:

> Dear community,
>
>
>
> Time, it needs time
>
> Be we are back again
>
> .  (slightly base on a song :D )
>
> This is our second voting candidate for the 11.3 release of Apache
> NetBeans.
> Matthias found a bad generation of LICENSE file that should be fixed now.
>
> Note that this is our second release vote where you are required to check
> both sources and convenience binaries before voting!
>
>
>
> See requirements below.
>
>
>
> Apache NetBeans 11.3 constitutes all clusters in the Apache NetBeans Git
> repo, 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/11.3/vc2
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.3/vc2
>
>
>
> They were built by the Jenkins pipeline and moved to their place:
>
>
>
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
> ns/job/release113/20
> 
>
>
>
> We are primarily voting on:
>
>
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/vc2/netbeans-1
> 1.3-source.zip
> 
>
>
>
> SHA512:
>
> (sha512 generation changed a bit, no more folder info)
>
>
> af0f52aec261d307626f0089b6957ba559808268d90e0c41720b481d40cc42d7474b0ffe5b93
> baf7c03ec7ebf3c9bbe1d229c219f8057a5f26294d46de0d986c
> ./netbeans-11.3-source.zip
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
>
>
> --
>
>
>
> Associated to the primary source item you will have (generated with
> pipeline
> mentioned above)
>
>
>
> under https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/vc2
>
>   binaries associated to the source
>
>   netbeans-11.3-bin.zip
>
>   as well as update content under nbms folder
>
>   a small testrelease.sh script over here
> https://dist.apache.org/repos/dist/dev/netbeans
>
>
>
> under
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.3/vc2
>
>
>
>   you will find platform cluster build
>
>   netbeans-platform-11.3-bin
>
>   netbeans-platform-11.3-source
>
>
>
>
>
> Associated Apache Maven artefacts RELEASE113 can be found at
>
> https://repository.apache.org/content/repositories/orgapachenetbeans-1056
>
>
>
> Artefacts are composed of jars,nbm,sources,javadocs,pom.
>
>
>
> --
>
>
>
> Apache NetBeans Git Repo tag: 11.3-vc2 :
>
>
>
> https://github.com/apache/netbeans/tree/11.3-vc2
>
>
>
> Release specific wiki page:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.3
>
>
>
>
>
> 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 - see
>
> 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, except for:
>
>
>
> -
>
> platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/
>
> empty.jar
>
> - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
>
> - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
>
> - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
>
> - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
>
>
>
> which are only jars by their name
>
>
>
> 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 should check the associated
>
> convenience binary zips and nbms at the artefact links above. 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. Separate votes will be held on
> other convenience binaries, mostly for each installer.
>
> Those will be dependent on this vote passing.
>
> Thi

Re: [VOTE] Release Apache NetBeans 11.3 [vote candidate 1]

[Alessandro]

+1

Downloaded source archive
Checked source archive SHA digest
Unzipped source archive
Checked NOTICE, LICENSE
Verified presence of mentioned jars
Built on Windows 10 with OpenJDK8
Run built application

Downloaded binary archive
Unzipped archive
Adjusted configuration in etc/netbeans.conf
Run application

Kudos to the Release Manager Eric Barboni!

Regards,
Alex

Il giorno mer 19 feb 2020 alle ore 17:19 Eric Barboni  ha
scritto:

> Dear community,
>
>
>
> Sorry for the delay, artefacts are ready since 3 days but we hit a per file
> size limitation on the distribution server. Thanks to INFRA this now ok.
>
>
>
> This is our first voting candidate for the 11.3 release of Apache NetBeans.
> Note that this is our first release vote where you are required to check
> both sources and convenience binaries before voting!
>
>
>
> See requirements below.
>
> Apache NetBeans 11.3 constitutes all clusters in the Apache NetBeans Git
> repo, 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/11.3/
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.3/
>
>
>
> They were built by the Jenkins pipeline and moved to their place:
>
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbea
> ns/job/release113/13
> 
>
>
>
> We are primarily voting on:
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/netbeans-11.3-
> source.zip
> 
>
>
>
> SHA512:
>
>
> 5c9152d571993f116c94fe968066ec8ca288c76353b4406c0de4d6e0941a4678724c73447444
> 8128f9f9ff4dd79a944598d5760311ecea7695437d4debcde75c
> netbeans-11.3-source.zip
>
>
>
> KEYS file:
>
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
>
>
> --
>
>
>
> Associated to the primary source item you will have (generated with
> pipeline
> mentioned above)
>
> under https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.3/
>
>   binaries associated to the source
>
>   netbeans-11.3-bin.zip
>
>   as well as update content under nbms folder
>
>
>
> under
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.3/
>
>   you will find platform cluster build
>
>   netbeans-platform-11.3-bin
>
>   netbeans-platform-11.3-source
>
>
>
> Associated Apache Maven artefacts RELEASE113 can be found at
> https://repository.apache.org/content/repositories/orgapachenetbeans-1055
>
> Artefacts are composed of jars,nbm,sources,javadocs,pom.
>
> --
>
>
>
> Apache NetBeans Git Repo tag: 11.3-vc1 :
>
> https://github.com/apache/netbeans/tree/11.3-vc1
>
>
>
>
>
> Release specific wiki page:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.3
>
>
>
>
>
> 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 - see
> 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, except for:
>
> -
>
> platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/
> empty.jar
>
> - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
>
> - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
>
> - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
>
> - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
>
> which are only jars by their name
>
> 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 should check the associated
> convenience binary zips and nbms at the artefact links above. 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. Separate votes will be held on
> other convenience binaries, mostly for each installer. Those will be
> dependent on this vote passing.
>
>
>
> 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 with (binding) if you're an Apache NetBeans PMC
> member
> to help with voting admin.  NetBeans 11.3

Re: Annoying build issue on Windows

[Alessandro]

Hi Kenneth,
  I think this hasn’t got to do with path length. If I remove that
cleaner.exe file the build succeeds, even in the Documents folder.

Regards ,
Alex

Il giorno mer 12 feb 2020 alle 16:13 Kenneth Fogel <
kfo...@dawsoncollege.qc.ca> ha scritto:

> Consider building from a shorter path. Windows still suffers from a max
> path of 260 characters. I tell my students to never use the Documents
> folder because it already eats up path. I create a older off of the root of
> a drive and call it dev. There is a long path in Windows that NTFS supports
> of an amazing length of 65,535 but for some reason it is not the default.
> It can only be used on an app by app basis but that means you could create
> paths that some apps can't use so we get stuck at 260. Sigh.
>
> Ken
>
>
> -Original Message-
> From: Alessandro 
> Sent: February 12, 2020 4:08 AM
> To: dev@netbeans.apache.org
> Subject: Annoying build issue on Windows
>
> Hi all,
>   I am facing an annoying build issue on Windows and I wonder if it
> something it could be dealt with.
>
> Building NetBeans from a fresh git clone is OK.
> On a second time build (no clean just ant build) I get:
> BUILD FAILED
> C:\Users\falappa\Documents\gitrepos\netbeans\nbbuild\build.xml:660: The
> following error occurred while executing this line:
>
> C:\Users\falappa\Documents\gitrepos\netbeans\harness\libs.nbi.engine\build.xml:50:
> Error while expanding
>
> C:\Users\falappa\Documents\gitrepos\netbeans\harness\libs.nbi.engine\external\nbi.engine-external-binaries-11.zip
> java.nio.file.AccessDeniedException:
>
> C:\Users\falappa\Documents\gitrepos\netbeans\nbi\engine\native\cleaner\windows\dist\cleaner.exe
> at
>
> sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83)
> at
> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
> at
> sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
> at
>
> sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230)
> at
>
> java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
> at java.nio.file.Files.newOutputStream(Files.java:216)
> at
> org.apache.tools.ant.taskdefs.Expand.extractFile(Expand.java:361)
> at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:199)
> at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:157)
> ...
>
> It seems that the mentioned nbi.engine-external-binaries-11.zip contains
> the cleaner.exe file with system and hidden attributes set, those prevents
> overwriting on the second build. To work around it I have to manually
> remove the cleaner.exe file with del /ash cleaner.exe.
>
> Are those attributes really needed?
> Would it be possible to have them removed from the file in the zip archive?
> Am I building something wrong?
>
> Regards,
> Alex
>
> -
> 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
>
>
>
>

Annoying build issue on Windows

[Alessandro]

Hi all,
  I am facing an annoying build issue on Windows and I wonder if it
something it could be dealt with.

Building NetBeans from a fresh git clone is OK.
On a second time build (no clean just ant build) I get:
BUILD FAILED
C:\Users\falappa\Documents\gitrepos\netbeans\nbbuild\build.xml:660: The
following error occurred while executing this line:
C:\Users\falappa\Documents\gitrepos\netbeans\harness\libs.nbi.engine\build.xml:50:
Error while expanding
C:\Users\falappa\Documents\gitrepos\netbeans\harness\libs.nbi.engine\external\nbi.engine-external-binaries-11.zip
java.nio.file.AccessDeniedException:
C:\Users\falappa\Documents\gitrepos\netbeans\nbi\engine\native\cleaner\windows\dist\cleaner.exe
at
sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:83)
at
sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:97)
at
sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:102)
at
sun.nio.fs.WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230)
at
java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)
at java.nio.file.Files.newOutputStream(Files.java:216)
at org.apache.tools.ant.taskdefs.Expand.extractFile(Expand.java:361)
at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:199)
at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:157)
...

It seems that the mentioned nbi.engine-external-binaries-11.zip contains
the cleaner.exe file with system and hidden attributes set, those prevents
overwriting on the second build. To work around it I have to manually
remove the cleaner.exe file with del /ash cleaner.exe.

Are those attributes really needed?
Would it be possible to have them removed from the file in the zip archive?
Am I building something wrong?

Regards,
Alex

NetBeans and Windows Defender

[Alessandro]

Hi all,
  Windows users often report performance issues caused by the Windows
Defender native antivirus software. It would be great if NetBeans could
detect Windows Defender running and warn the users at startup.

Here
https://github.com/JetBrains/intellij-community/blob/master/platform/platform-impl/src/com/intellij/diagnostic/WindowsDefenderChecker.java
is what Intellij IDEA Community does to detect Windows Defender and even
add some folders to the ignore list.

That code could be adapted to have a similar functionality in NetBeans. The
code is Apache 2.0 licensed but cannot be used as it is.

Any Windows based takers?

Regards,
Alex

Toolbar grips for FlatLaf

[Alessandro]

Hi all,
  I have opened https://github.com/apache/netbeans/pull/1928 to fix my last
gripe with FlatLaf: toolbar grips.

Testing on MacOS and MacOS Retina would be more than welcome as I do not
own an HiDPI monitor.

Karl Tauber confirmed is OK on Windows with 150% HiDPI.

Would also be awesome to include the PR in next beta.

Regards,
Alex

Fix for remove surrounding code action...

[Alessandro]

Hi all,
  I have opened a PR to fix the hardcoded colors in the Java editor "Remove
Surrounding Code" action (Alt + Backspace):
https://github.com/apache/netbeans/pull/1926

The PR is beneficial for dark LAFs (see PR page for before/after
screenshots).

Would it be possible to have it reviewed and included in NB 11.3 next beta?

Regards,
Alex

Re: Flat Look and Feel NB12 default?

[Alessandro]

Hi Neil,
  well thought!

Indeed the import settings dialog would be the best place where to add the
choice of a couple of common settings should the user decide to not import
the settings from a previous version.

Regards,
Alex

Il giorno gio 23 gen 2020 alle ore 10:12 Neil C Smith 
ha scritto:

> On Thu, 23 Jan 2020, 08:10 Geertjan Wielenga,  wrote:
>
> > I’d be hesitant about introducing anything that slows the startup
> > experience.
> >
>
> We already have the import settings dialog which needs some work. What
> would be your concern with a welcome wizard for some common settings? Done
> right it could speed up the start-up experience?
>
> Best wishes,
>
> Neil
>

Re: Flat Look and Feel NB12 default?

[Alessandro]

Hi Geertjan,
  my answers below.

Il giorno gio 23 gen 2020 alle ore 09:10 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> I’d be hesitant about introducing anything that slows the startup
> experience.
>

I meant a wizard shown only on the very first launch of a newly installed
NetBeans, it could be used to ask the user to choose other frequently
adjusted preferences normally found in the Options dialog. For instance it
would be the right place to ask which features he/she would like to
activate.

But maybe something could be introduced into the Welcome Screen, a message
> like “Make NetBeans look even better here” which pops up the relevant tab
> in the Options window.
>

This is another way to have it. Maybe less effective but surely more
visible to a newcomer.

Gj
>
> On Thu, 23 Jan 2020 at 09:07, Alessandro  wrote:
>
> > Hi,
> >   as a confirmation of the VERY subjective perspective, I for one would
> > like NetBeans having the same default Look  and Feel on all platforms,
> > instead of the OS natives one (still available and switchable by the
> user).
> >
> > At present (NB 8.2, 11.2) I install and switch to Darcula on Linux and
> > Windows.
> >
> > In my opinion, the best thing besides making FlatLaf the default L&F
> would
> > be to also show a wizard on first launch asking the users to choose the
> > variant (Light or Dark).
> >
> > This topic could require a user poll to get it right for the majority of
> > the users.
> >
> > Regards,
> > Alex
> >
> > Il giorno mer 22 gen 2020 alle ore 23:57 Chuck Davis  >
> > ha scritto:
> >
> > > We're talking about very, VERY subjective perspectives here.  Just
> > because
> > > there is a new fad called "flat" doesn't mean it's an improvement.
> > > Actually, "flat" looks so 1970's ish.  Perhaps the fascination with it
> is
> > > due to the fact that most of the productive people here either weren't
> > > alive at that time in computing history or were still too young to
> > remember
> > > those days.
> > >
> > > I agree with Mr. Bakke that on Windows and Mac it should still use the
> os
> > > native laf as the default.  For Linux (where I spend 100% of my
> > development
> > > time) I don't care what ships as long as I can make it what I want it
> to
> > be
> > > by merely selecting from a list that includes basic stuff like we've
> got
> > > now (i.e. "Metal").  I don't find "dark" or "flat" attractive in the
> > > least.  I DO like colorful icons that make my desktop "attractive".
> What
> > > we each think is "attractive" is a very subjective judgement so a
> variety
> > > of options is a good thing -- even on Windows and Mac for those who
> > prefer
> > > something other than native.
> > >
> > > Just my $.02.
> > >
> > > On Wed, Jan 22, 2020 at 2:09 PM Eirik Bakke  wrote:
> > >
> > > > I think FlatLAF could very well be made the default on Linux. But on
> > > > Windows and MacOS, I'd argue we should use the OS-specific LAFs by
> > > default.
> > > >
> > > > On MacOS and Windows, we have very good existing LAFs that follow the
> > > same
> > > > style as other desktop applications on the same platform. So NetBeans
> > > will
> > > > look like a native MacOS app on Mac, and like a native Windows app on
> > > > Windows. In fact, both the MacOS (Aqua) and Windows LAFs make calls
> to
> > > the
> > > > OS to retrieve real, native graphics for buttons, combo boxes,
> > > checkboxes,
> > > > and so on. So NetBeans always gets the correct look for whichever OS
> > > > version is currently running. There has also been a lot of
> improvements
> > > to
> > > > the Windows and MacOS LAFs over the past few releases, and the next
> > one,
> > > > especially for HiDPI displays. (See
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> > > > )
> > > >
> > > > The fact that NetBeans looks like a native app on both Windows and
> > MacOS
> > > > is a strong brand differentiator, compared to for instance IntelliJ,
> > > which
> > > > does not in any way try to stay consistent with the OS look.
> > > >
> > > > -- Eirik
> > > >
> > > > -Original Message-
> > > > From: John Mc 
> > > > Sent: Wednesday, January 22, 2020 1:48 PM
> > > > To: dev@netbeans.apache.org
> > > > Subject: Flat Look and Feel NB12 default?
> > > >
> > > > Hi
> > > >
> > > > So I started using the latest development builds and I really like
> the
> > > > progress with the Flat Look and Feel addition for NB11.3.  Great job
> to
> > > the
> > > > guys who have done all this work it really looks nice.
> > > >
> > > > Are there plans to consider making this the default LnF for NetBeans
> 12
> > > > onwards?
> > > >
> > > > Regards
> > > >
> > > > John
> > > >
> > >
> >
>

Re: Flat Look and Feel NB12 default?

[Alessandro]

Hi,
  as a confirmation of the VERY subjective perspective, I for one would
like NetBeans having the same default Look  and Feel on all platforms,
instead of the OS natives one (still available and switchable by the user).

At present (NB 8.2, 11.2) I install and switch to Darcula on Linux and
Windows.

In my opinion, the best thing besides making FlatLaf the default L&F would
be to also show a wizard on first launch asking the users to choose the
variant (Light or Dark).

This topic could require a user poll to get it right for the majority of
the users.

Regards,
Alex

Il giorno mer 22 gen 2020 alle ore 23:57 Chuck Davis 
ha scritto:

> We're talking about very, VERY subjective perspectives here.  Just because
> there is a new fad called "flat" doesn't mean it's an improvement.
> Actually, "flat" looks so 1970's ish.  Perhaps the fascination with it is
> due to the fact that most of the productive people here either weren't
> alive at that time in computing history or were still too young to remember
> those days.
>
> I agree with Mr. Bakke that on Windows and Mac it should still use the os
> native laf as the default.  For Linux (where I spend 100% of my development
> time) I don't care what ships as long as I can make it what I want it to be
> by merely selecting from a list that includes basic stuff like we've got
> now (i.e. "Metal").  I don't find "dark" or "flat" attractive in the
> least.  I DO like colorful icons that make my desktop "attractive".  What
> we each think is "attractive" is a very subjective judgement so a variety
> of options is a good thing -- even on Windows and Mac for those who prefer
> something other than native.
>
> Just my $.02.
>
> On Wed, Jan 22, 2020 at 2:09 PM Eirik Bakke  wrote:
>
> > I think FlatLAF could very well be made the default on Linux. But on
> > Windows and MacOS, I'd argue we should use the OS-specific LAFs by
> default.
> >
> > On MacOS and Windows, we have very good existing LAFs that follow the
> same
> > style as other desktop applications on the same platform. So NetBeans
> will
> > look like a native MacOS app on Mac, and like a native Windows app on
> > Windows. In fact, both the MacOS (Aqua) and Windows LAFs make calls to
> the
> > OS to retrieve real, native graphics for buttons, combo boxes,
> checkboxes,
> > and so on. So NetBeans always gets the correct look for whichever OS
> > version is currently running. There has also been a lot of improvements
> to
> > the Windows and MacOS LAFs over the past few releases, and the next one,
> > especially for HiDPI displays. (See
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/HiDPI+%28Retina%29+improvements
> > )
> >
> > The fact that NetBeans looks like a native app on both Windows and MacOS
> > is a strong brand differentiator, compared to for instance IntelliJ,
> which
> > does not in any way try to stay consistent with the OS look.
> >
> > -- Eirik
> >
> > -Original Message-
> > From: John Mc 
> > Sent: Wednesday, January 22, 2020 1:48 PM
> > To: dev@netbeans.apache.org
> > Subject: Flat Look and Feel NB12 default?
> >
> > Hi
> >
> > So I started using the latest development builds and I really like the
> > progress with the Flat Look and Feel addition for NB11.3.  Great job to
> the
> > guys who have done all this work it really looks nice.
> >
> > Are there plans to consider making this the default LnF for NetBeans 12
> > onwards?
> >
> > Regards
> >
> > John
> >
>

Re: NetBeans API for projects lifecycle

[Alessandro]

Hi Chris,
  the DebuggerManager API allows to listen for start/stop debug project
events just fine.
Do you, or anyone, know how to listen to start/stop run project events too?

Thank you in advance.

Regards,
Alex


Il giorno mar 21 gen 2020 alle ore 16:41 Alessandro 
ha scritto:

> Thanks Chris,
>   will check that out.
>
> Greets,
> Alex
>
> Il giorno mar 21 gen 2020 alle ore 13:33 Christian Lenz <
> christian.l...@gmx.net> ha scritto:
>
>> Hey Alessandro,
>>
>> check this out:
>> https://gist.github.com/Chris2011/f779ec3227bad795d23786daf3ac008e
>>
>>
>> Cheers
>>
>> Chris
>>
>>
>>
>> Von: Alessandro
>> Gesendet: Montag, 20. Januar 2020 15:13
>> An: dev@netbeans.apache.org
>> Betreff: NetBeans API for projects lifecycle
>>
>> Hi all,
>>   is there a NetBeans API for listening to when user starts/stops
>> Run/Debug
>> of Java projects (all build tools) and also possibly programmatically
>> starting/stopping them too?
>>
>> Is this a question better suited for the users mailing list?
>>
>> Regards,
>> Alex
>>
>>

Re: NetBeans API for projects lifecycle

[Alessandro]

Thanks Chris,
  will check that out.

Greets,
Alex

Il giorno mar 21 gen 2020 alle ore 13:33 Christian Lenz <
christian.l...@gmx.net> ha scritto:

> Hey Alessandro,
>
> check this out:
> https://gist.github.com/Chris2011/f779ec3227bad795d23786daf3ac008e
>
>
> Cheers
>
> Chris
>
>
>
> Von: Alessandro
> Gesendet: Montag, 20. Januar 2020 15:13
> An: dev@netbeans.apache.org
> Betreff: NetBeans API for projects lifecycle
>
> Hi all,
>   is there a NetBeans API for listening to when user starts/stops Run/Debug
> of Java projects (all build tools) and also possibly programmatically
> starting/stopping them too?
>
> Is this a question better suited for the users mailing list?
>
> Regards,
> Alex
>
>

NetBeans API for projects lifecycle

[Alessandro]

Hi all,
  is there a NetBeans API for listening to when user starts/stops Run/Debug
of Java projects (all build tools) and also possibly programmatically
starting/stopping them too?

Is this a question better suited for the users mailing list?

Regards,
Alex

Re: Where to put color profiles...

[Alessandro]

Hi Laszlo,
  that was quick!

Also had a glimpse to what Karl from FormDev is cooking up in his next PR
and I am impressed!

Greetings,
Alex

Il giorno mar 10 dic 2019 alle ore 21:20 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> And now it ison the way to master:
> https://github.com/apache/netbeans/pull/1769
>
> On 12/10/19 11:46 AM, Alessandro wrote:
> > Hi Laszlo,
> >please have a look at PR-1768.
> >
> > Greetings,
> > Alex
> >
> > Il giorno dom 8 dic 2019 alle ore 20:48 Laszlo Kishalmi <
> > laszlo.kisha...@gmail.com> ha scritto:
> >
> >> Check out the branch from the apache repo, then commit it back to your
> >> fork, that would be fine. and yes then the PR
> >>
> >>
> >> On 12/8/19 11:23 AM, Alessandro wrote:
> >>> Hi Laszlo,
> >>> I had a quick look to your work and I saw that we made similar
> choices
> >>> with regard to file naming and folder structure. I did not use your
> >>> upgraded DTD for defining the color palette but this can be worked on
> >>> afterwards. The NBDarcula color profiles define colours with an ARGB
> hex
> >>> color notation, does your new DTD suppor that?
> >>>
> >>> How should I proceed considering that I cannot commit to the Apache
> >>> repository directly? Is it OK if I fork again the repo, checkout your
> >>> branch, update it and then open a PR against your original branch?
> >>>
> >>> Let me know.
> >>>
> >>> Greetings,
> >>> Alex
> >>>
> >>> Il giorno dom 8 dic 2019 alle 19:55 Laszlo Kishalmi <
> >>> laszlo.kisha...@gmail.com> ha scritto:
> >>>
> >>>> The branch name is: flatlaf-fontscolors
> >>>>
> >>>> I'd name the theme to FlatLaf Dark and we probably improve it a bit
> over
> >>>> Darcula.
> >>>>
> >>>> Let's keep the name Darcula for the external nb-darcula plugin.
> >>>>
> >>>> On 12/8/19 10:48 AM, Laszlo Kishalmi wrote:
> >>>>> Huh, I kind of worked on the same thing.
> >>>>>
> >>>>> Let me open a branch for that. I'd put the basic files and layout
> >>>>> there. You can update the content as that's I'm not finished with.
> >>>>> Then once we put our stuff together we create a PR from that branch.
> >>>>>
> >>>>> As of the Norway Today. I think it is either was available before the
> >>>>> Dark Look and Feels. It is a similar theme like IBM used in OS/2 E
> >>>>> editor (an old time favorite of mine from 1998). I used it a lot even
> >>>>> with light LaF-s.
> >>>>>
> >>>>>
> >>>>> On 12/8/19 9:50 AM, Alessandro wrote:
> >>>>>> Hi all,
> >>>>>>  I have created an editor color profile that matches the Darcula
> >>>>>> palette
> >>>>>> by porting the NB Darcula color profile.
> >>>>>>
> >>>>>> I have called this new profile "FlatLafDark" and put it into
> >>>>>> platform/o.n.swing.laf.flatlaf in my fork of Apache NetBeans source,
> >>>>>> however I noticed that the standard color profiles (e.g. Norway
> >>>>>> Today, City
> >>>>>> Lights, etc.) live in ide/defaults. It also seems a bit strange that
> >>>>>> they
> >>>>>> are in different clusters.
> >>>>>>
> >>>>>> Moreover I noticed that the recently ported dark LAFs (Dark Metal
> and
> >>>>>> Dark
> >>>>>> Nimbus) are not tightly coupled with a color profile but suggest the
> >>>>>> use of
> >>>>>> Norway Today as recommended profile (recent work by Laszlo Kishalmi
> in
> >>>>>> commit
> >>>>>>
> >>
> https://github.com/apache/netbeans/commit/f268b73e83b4d10e3c015a5fee2c7e8adc258237
> >> )
> >>>>>> thus it could be better to choose a generic name for the color
> >>>>>> profile such
> >>>>>> as "Darcula".
> >>>>>>
> >>>>>> How should I call the new color profile and where should I place its
> >>>>>> files?
> >>>>>>
> >>>>>> Regards,
> >>>>>> Alex
> >>>>>>
> >>>> -
> >>>> 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: Where to put color profiles...

[Alessandro]

Hi Laszlo,
  please have a look at PR-1768.

Greetings,
Alex

Il giorno dom 8 dic 2019 alle ore 20:48 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Check out the branch from the apache repo, then commit it back to your
> fork, that would be fine. and yes then the PR
>
>
> On 12/8/19 11:23 AM, Alessandro wrote:
> > Hi Laszlo,
> >I had a quick look to your work and I saw that we made similar choices
> > with regard to file naming and folder structure. I did not use your
> > upgraded DTD for defining the color palette but this can be worked on
> > afterwards. The NBDarcula color profiles define colours with an ARGB hex
> > color notation, does your new DTD suppor that?
> >
> > How should I proceed considering that I cannot commit to the Apache
> > repository directly? Is it OK if I fork again the repo, checkout your
> > branch, update it and then open a PR against your original branch?
> >
> > Let me know.
> >
> > Greetings,
> > Alex
> >
> > Il giorno dom 8 dic 2019 alle 19:55 Laszlo Kishalmi <
> > laszlo.kisha...@gmail.com> ha scritto:
> >
> >> The branch name is: flatlaf-fontscolors
> >>
> >> I'd name the theme to FlatLaf Dark and we probably improve it a bit over
> >> Darcula.
> >>
> >> Let's keep the name Darcula for the external nb-darcula plugin.
> >>
> >> On 12/8/19 10:48 AM, Laszlo Kishalmi wrote:
> >>> Huh, I kind of worked on the same thing.
> >>>
> >>> Let me open a branch for that. I'd put the basic files and layout
> >>> there. You can update the content as that's I'm not finished with.
> >>> Then once we put our stuff together we create a PR from that branch.
> >>>
> >>> As of the Norway Today. I think it is either was available before the
> >>> Dark Look and Feels. It is a similar theme like IBM used in OS/2 E
> >>> editor (an old time favorite of mine from 1998). I used it a lot even
> >>> with light LaF-s.
> >>>
> >>>
> >>> On 12/8/19 9:50 AM, Alessandro wrote:
> >>>> Hi all,
> >>>> I have created an editor color profile that matches the Darcula
> >>>> palette
> >>>> by porting the NB Darcula color profile.
> >>>>
> >>>> I have called this new profile "FlatLafDark" and put it into
> >>>> platform/o.n.swing.laf.flatlaf in my fork of Apache NetBeans source,
> >>>> however I noticed that the standard color profiles (e.g. Norway
> >>>> Today, City
> >>>> Lights, etc.) live in ide/defaults. It also seems a bit strange that
> >>>> they
> >>>> are in different clusters.
> >>>>
> >>>> Moreover I noticed that the recently ported dark LAFs (Dark Metal and
> >>>> Dark
> >>>> Nimbus) are not tightly coupled with a color profile but suggest the
> >>>> use of
> >>>> Norway Today as recommended profile (recent work by Laszlo Kishalmi in
> >>>> commit
> >>>>
> >>
> https://github.com/apache/netbeans/commit/f268b73e83b4d10e3c015a5fee2c7e8adc258237
> )
> >>
> >>>> thus it could be better to choose a generic name for the color
> >>>> profile such
> >>>> as "Darcula".
> >>>>
> >>>> How should I call the new color profile and where should I place its
> >>>> files?
> >>>>
> >>>> Regards,
> >>>> Alex
> >>>>
> >> -
> >> 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: Where to put color profiles...

[Alessandro]

Hi Laszlo,
  I had a quick look to your work and I saw that we made similar choices
with regard to file naming and folder structure. I did not use your
upgraded DTD for defining the color palette but this can be worked on
afterwards. The NBDarcula color profiles define colours with an ARGB hex
color notation, does your new DTD suppor that?

How should I proceed considering that I cannot commit to the Apache
repository directly? Is it OK if I fork again the repo, checkout your
branch, update it and then open a PR against your original branch?

Let me know.

Greetings,
Alex

Il giorno dom 8 dic 2019 alle 19:55 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> The branch name is: flatlaf-fontscolors
>
> I'd name the theme to FlatLaf Dark and we probably improve it a bit over
> Darcula.
>
> Let's keep the name Darcula for the external nb-darcula plugin.
>
> On 12/8/19 10:48 AM, Laszlo Kishalmi wrote:
> > Huh, I kind of worked on the same thing.
> >
> > Let me open a branch for that. I'd put the basic files and layout
> > there. You can update the content as that's I'm not finished with.
> > Then once we put our stuff together we create a PR from that branch.
> >
> > As of the Norway Today. I think it is either was available before the
> > Dark Look and Feels. It is a similar theme like IBM used in OS/2 E
> > editor (an old time favorite of mine from 1998). I used it a lot even
> > with light LaF-s.
> >
> >
> > On 12/8/19 9:50 AM, Alessandro wrote:
> >> Hi all,
> >>I have created an editor color profile that matches the Darcula
> >> palette
> >> by porting the NB Darcula color profile.
> >>
> >> I have called this new profile "FlatLafDark" and put it into
> >> platform/o.n.swing.laf.flatlaf in my fork of Apache NetBeans source,
> >> however I noticed that the standard color profiles (e.g. Norway
> >> Today, City
> >> Lights, etc.) live in ide/defaults. It also seems a bit strange that
> >> they
> >> are in different clusters.
> >>
> >> Moreover I noticed that the recently ported dark LAFs (Dark Metal and
> >> Dark
> >> Nimbus) are not tightly coupled with a color profile but suggest the
> >> use of
> >> Norway Today as recommended profile (recent work by Laszlo Kishalmi in
> >> commit
> >>
> https://github.com/apache/netbeans/commit/f268b73e83b4d10e3c015a5fee2c7e8adc258237)
>
> >>
> >> thus it could be better to choose a generic name for the color
> >> profile such
> >> as "Darcula".
> >>
> >> How should I call the new color profile and where should I place its
> >> files?
> >>
> >> Regards,
> >> Alex
> >>
>
> -
> 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
>
>
>
>

Where to put color profiles...

[Alessandro]

Hi all,
  I have created an editor color profile that matches the Darcula palette
by porting the NB Darcula color profile.

I have called this new profile "FlatLafDark" and put it into
platform/o.n.swing.laf.flatlaf in my fork of Apache NetBeans source,
however I noticed that the standard color profiles (e.g. Norway Today, City
Lights, etc.) live in ide/defaults. It also seems a bit strange that they
are in different clusters.

Moreover I noticed that the recently ported dark LAFs (Dark Metal and Dark
Nimbus) are not tightly coupled with a color profile but suggest the use of
Norway Today as recommended profile (recent work by Laszlo Kishalmi in
commit
https://github.com/apache/netbeans/commit/f268b73e83b4d10e3c015a5fee2c7e8adc258237)
thus it could be better to choose a generic name for the color profile such
as "Darcula".

How should I call the new color profile and where should I place its files?

Regards,
Alex

Re: FlatLaf look and feel in main window

[Alessandro]

Hi Karl,
  first of all thanks for your stunning work on FlatLaf, it is a great LaF
and if it were for me I would make it the default LaF for NetBeans in a
future release.

I played with Darcula in the past and I even contributed back some small
bits (dialog icons and a fix for baseline alignment of spinners), even if I
can't promise anything, I would gladly help.

I am not working on any of the parts you mentioned so please go ahead and
leave me some time to familiarize with FlatLaf code and its NetBeans
module. I will try to focus on an editor color scheme that goes well with
FlatLaf.

Regards,
Alex

Il giorno mer 4 dic 2019 alle ore 16:36 Karl Tauber 
ha scritto:

> Hi there,
>
> I'm Karl, creator of the FlatLaf look and feel.
> (https://github.com/JFormDesigner/FlatLaf)
>
> Thanks to Laszlo and Junichi, FlatLaf is now in NetBeans as experimental
> LaF.
>
> I'd like to help improving the look of FlatLaf in NetBeans and can spend
> some time to work on it.
>
> To avoid duplicate work, I'd like to ask whether someone else is already
> working on (parts of) the main window (editor/view tabs, splitter,
> minimize/maximize/close buttons, etc)?
>
> If not, I would like to work on these parts.
>
> All work will be done in module org.netbeans.swing.laf.flatlaf.
> Other look and feels should be not affected.
> All colors, insets, etc will be used from UI defaults, so that it is
> customizable and other FlatLaf based themes can be later added.
> (https://www.formdev.com/flatlaf/themes/)
>
> Regards,
> Karl
>
> -
> 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: Approaching Darkness

[Alessandro]

Hi Laszlo,
  With regard to the editor scheme going well with the FlatLaf look and
feel I would suggest contacting Fagner Granella who contributed an IntelliJ
Darcula based editor scheme to NB Darcula:
https://github.com/granella/Netbeans-Darcula-Theme

There is no license specified in that repository thus I think it would be
best trying to contact the author.

The editor scheme could also be “ported over” from NB Darcula itself.

Do not forget that also FlatLaf has some missing pieces and could be great
to foster collaboration between the two projects. See for example some
issues here:
https://github.com/JFormDesigner/FlatLaf/issues).

Regards,
Alex

Il giorno sab 23 nov 2019 alle 10:28 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Dear all,
>
> Say hello to our long lost pals Dark Metal and Dark Nimbus Look and
> Feels at: https://github.com/apache/netbeans/pull/1651
>
> (I've seen in its day several people were fond of the Dark Metal LaF, I
> never understood why...)
>
> I also took on Junichi Yamamoto's idea on including FlatLaf as a Look
> and Feel option and kicked some rocks together:
> https://github.com/apache/netbeans/pull/1652
>
> If there is no strong opinion against that I'd merge that code on
> Monday. Let's see what could we do with that as a community (a fitting
> editor color schema is going to be needed as well).
>
>
>
>
> -
> 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: Class index for single project

[Alessandro]

Here is a small gif screencast demonstrating the problematic behaviour:
https://imgur.com/a/OM6cKCM

I have slightly updated the previously mentioned code to deal with classes
in default package.

I would appreciate if someone could give me any hint.

Regards,
Alex

Il giorno gio 14 nov 2019 alle ore 16:10 Tomas Zezula <
tomas.zez...@oracle.com> ha scritto:

> Hi,
> it depends on how you created the ClasspathInfo.
> If the ClasspathInfo was created by `ClasspathInfo.create(FileObject)` or
> `ClasspathInfo.create(File)`
> the returned types (packages) are the types (packages) from the project
> where the `FileObject` comes from and
> projects the project depends on.
> If you need only the types (packages) from the project itself you can use
> SearchScope.SOURCE like:
>
> ci.getDeclaredTypes(“Foo”, NameKind.SIMPLE_NAME,
> Collections.singleton(SearchScopeType.SOURCE))
>
> When you need to search in a specific set of roots you can always create a
> custom ClasspathInfo to search just in given roots
> using `ClasspathInfo.create(ClassPath, ClassPath, ClassPath)`.
> The classpath for required roots can be constructed using
> `ClassPathSupport.createClassPath`.
>
> — Tomas
>
> > On 11 Nov 2019, at 14:27, Alessandro  wrote:
> >
> > Hi all,
> >  In a plugin I am writing I would like to complete a user text looking
> for
> > package an class names of the maven java project the edited file belongs
> > to. I am using the ClassIndex obtained via ClasspathInfo but it helps me
> > complete package and class names coming from all opened projects.
> >
> > Is there a way to limit the class index search to a single project?
> >
> > Thank you in advance.
> >
> > Regards,
> > Alex
>
>
> -
> 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: Class index for single project

[Alessandro]

Hi Tomas,
  thanks for your insights.

I am creating the ClasspathInfo object with a maven project root:
final ClassIndex classIndex =
ClasspathInfo.create(mvnPrj.getProjectDirectory()).getClassIndex();
where mvnPrj is a org.netbeans.modules.maven.NbMavenProjectImpl casted from
a org.netbeans.api.project.Project passed to the constructor of a class
annotated with @ProjectServiceProvider for maven project types.

I then query packages with:
Set packageNames = classIndex.getPackageNames(filter, true,
EnumSet.allOf(ClassIndex.SearchScope.class));
where filter is a user typed text string, and later in the code for classes
in a given package with:
Set> types =
classIndex.getDeclaredTypes(typeFilter,
ClassIndex.NameKind.CASE_INSENSITIVE_PREFIX, Collections.singleton(new
SinglePackageScope(packageFilter)));
where typeFilter and packageFilter are substrings of user typed string.

To have more context the plugin project is on GitHub at
https://github.com/AlexFalappa/nb-springboot , the snippets above are
from here:
https://github.com/AlexFalappa/nb-springboot/blob/5a5867946a0c0d89a243b91559d163f43f0015dc/src/main/java/com/github/alexfalappa/nbspringboot/projects/service/impl/SpringBootServiceImpl.java#L252-L257
and here:
https://github.com/AlexFalappa/nb-springboot/blob/5a5867946a0c0d89a243b91559d163f43f0015dc/src/main/java/com/github/alexfalappa/nbspringboot/projects/service/impl/LoggerNameHintProvider.java#L57-L79

It seems I am doing everything right, yet I noticed getting back results
from all the maven projects currently opened in the IDE. I will double
check later at home.

Your explanation is already valuable however.

Regards,
Alex

Il giorno gio 14 nov 2019 alle ore 16:10 Tomas Zezula <
tomas.zez...@oracle.com> ha scritto:

> Hi,
> it depends on how you created the ClasspathInfo.
> If the ClasspathInfo was created by `ClasspathInfo.create(FileObject)` or
> `ClasspathInfo.create(File)`
> the returned types (packages) are the types (packages) from the project
> where the `FileObject` comes from and
> projects the project depends on.
> If you need only the types (packages) from the project itself you can use
> SearchScope.SOURCE like:
>
> ci.getDeclaredTypes(“Foo”, NameKind.SIMPLE_NAME,
> Collections.singleton(SearchScopeType.SOURCE))
>
> When you need to search in a specific set of roots you can always create a
> custom ClasspathInfo to search just in given roots
> using `ClasspathInfo.create(ClassPath, ClassPath, ClassPath)`.
> The classpath for required roots can be constructed using
> `ClassPathSupport.createClassPath`.
>
> — Tomas
>
> > On 11 Nov 2019, at 14:27, Alessandro  wrote:
> >
> > Hi all,
> >  In a plugin I am writing I would like to complete a user text looking
> for
> > package an class names of the maven java project the edited file belongs
> > to. I am using the ClassIndex obtained via ClasspathInfo but it helps me
> > complete package and class names coming from all opened projects.
> >
> > Is there a way to limit the class index search to a single project?
> >
> > Thank you in advance.
> >
> > Regards,
> > Alex
>
>
> -
> 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
>
>
>
>

Class index for single project

[Alessandro]

Hi all,
  In a plugin I am writing I would like to complete a user text looking for
package an class names of the maven java project the edited file belongs
to. I am using the ClassIndex obtained via ClasspathInfo but it helps me
complete package and class names coming from all opened projects.

Is there a way to limit the class index search to a single project?

Thank you in advance.

Regards,
Alex

Curious multi-release jar problem...

[Alessandro]

Hi all,
  I just come up with a problem using a maven dependency jar that is a
multi-release jar, NetBeans 11.2 is unable to "see" some classes contained
in the jar.

The maven coordinates of the dependencies are:

com.formdev
flatlaf
0.17


To reproduce create a maven project with compile target and source 11, then
create a JFrame in it (New > JFrame Form... from context menu), then
replace the generated code that sets the Nimbus LAF with the following:
try {
javax.swing.UIManager.setLookAndFeel(new
com.formdev.flatlaf.|); // complete here
} catch (javax.swing.UnsupportedLookAndFeelException ex) {

java.util.logging.Logger.getLogger(NewJFrame.class.getName()).log(java.util.logging.Level.SEVERE,
null, ex);
}

Try to invoke completion at the pipe sign in the highlighted row, you'll
find that no look and feel class is shown, the Look and Feel classes
contained in the maven dependency should be FlatLightLaf, FlatDarkLaf,
FlatIntellijLaf and FlatDarculaLaf.
Note that even entering the class by hand there are error markers even if
the project builds and run successfully.

The only peculiar thing I noticed is that the dependency jar is a
multi-release jar that aims to be compatible with Java 8 but also support
modular programming (Java 9+), to achieve this it stores the
module-info.class into META-INF/versions/9 folder inside the jar. Curious
thing is that NetBeans does not have any problems with the most recent
log4j2 dependency that has a similar structure. Setting compiler source and
target to 8 is another way to get correct behaviour.

Could anyone reproduce?

NetBeans is 11.2 running on OpenJDK 11.0.4 with nb-javac plugin installed.

Regards,
Alex

Folding display options

[Alessandro]

Hi all,
  what's the purpose of Tools > Options > Editor > Folding > Display
Options > Content Preview toggle?

I thought it enabled/disabled the showing of a tooltip with folded content
while hovering on the folded section marker but it has actually no effect,
the tooltip is always shown.

Is it a bug?

Greets,
Alex

Maven projects Compile on Save requires nbjavac

[Alessandro]

Hi all,
  while testing NB11.2 voting candidate running on OpenJDK 11 I noticed
that the "Compile on Save" checkbox in maven projects project properties
dialog was greyed out but I didn't digged it further.
After a while I tested the installation of nbjavac plugin and shortly
afterwards noticed that the "Compile on Save" checkbox was enabled and
selected.

Is this a known requirement?

Out of curiosity which features does exactly nbjavac enable when on OpenJDK
11 ?

Found no direct documentation on the web site/wiki but as far as I recall
nbjavac is mandatory for JDK 8 and optional for JDK 9 and above.

Regards,
Alex

Re: [VOTE] Release Apache NetBeans 11.2 [vote candidate 1]

[Alessandro]

+1

Checked SHA512 of binary
Unzipped and launched binary with Oracle JDK8 on Linux
Activated all features except PHP (this triggered installation of nbjavac)
Opened and compiled some maven projects
Added maven 3.6.2 as external maven installation
Opened and compiled other maven projects
Added OpenJDK 11 as Java Platform
Opened and compiled two java modular projects


Il giorno dom 20 ott 2019 alle ore 14:26 Neil C Smith 
ha scritto:

> Dear all,
>
> This is our first voting candidate for the 11.2 release of Apache
> NetBeans. Note that this is our first release vote where you are
> required to check both sources and convenience binaries before voting!
> See requirements below.
>
> Apache NetBeans 11.2 constitutes all clusters in the Apache NetBeans
> Git repo, 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/11.2-vc1/
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.2-vc1/
>
> They were built by the Jenkins pipeline at:
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/29/
>
> We are primarily voting on:
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/netbeans-11.2-vc1-source.zip
>
> SHA512:
>
> 4586ec37778d7b7044e4a456408fce1686ea70db9847d5a24e2974728774d57963c1d0372c54b91008835b16b0d5c7f99b8b5714387b40116c8f28a331392a39
>  ./netbeans-11.2-vc1-source.zip
>
> KEYS file:
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
> Apache NetBeans Git Repo tag: 11.2-vc1 :
> https://github.com/apache/netbeans/tree/11.2-vc1
>
>
> Release specific wiki page:
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.2
>
>
> 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 - see
> 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, except for:
> -
> platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar
> - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
> - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
> - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
> - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
> which are only jars by their name
> 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 should check the associated
> convenience binary zips and nbms at the artefact links above. 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. Separate votes
> will be held on other convenience binaries, including Maven artefacts
> and for each installer. Those will be dependent on this vote passing.
>
>
> This vote is going to be open at least 72 hours, vote with +1, 0, and
> -1 as usual.  Please mark your vote with (binding) if you're an Apache
> NetBeans PMC member to help with voting admin.  NetBeans 11.2 will be
> released if and when this vote passes.
>
>
> Thank you for all the hard work!
>
> Best wishes,
>
> Neil
> Volunteer Release Manager for Apache NetBeans 11.2
>
> -
> 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: New plugin portal and update center

[Alessandro]

Thank you Geertjan, much appreciated.

Regards,
Alex

Il giorno ven 18 ott 2019 alle ore 08:55 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> We’ll get you a login/password for the ‘old’ plugin portal, there were some
> changes about that recently.
>
> The new one won’t be registered in 11.2, not really ready for that yet.
> Many thanks for trying it out and getting your plugins registered there,
> those that have not been approved will be approved soon.
>
> Gj
>
> On Fri, 18 Oct 2019 at 08:49, Alessandro  wrote:
>
> > Hi all,
> > I have successfully published a plugin on the new portal and I have
> another
> > in the queue, I would like to know how and when those will be available
> > directly within NetBeans in Options > Plugins (Plugin Portal Update
> > Center). I am asking because I cannot log-in into the old portal anymore.
> >
> > Current NetBeans 11.2-beta3 has a 'NetBeans Plugin Portal' update center
> > with URL https://netbeans.apache.org/nb/updates/11.2/updates.xml.gz but
> it
> > contains the plugins of the old portal.
> >
> > Regards,
> > Alex
> >
>

New plugin portal and update center

[Alessandro]

Hi all,
I have successfully published a plugin on the new portal and I have another
in the queue, I would like to know how and when those will be available
directly within NetBeans in Options > Plugins (Plugin Portal Update
Center). I am asking because I cannot log-in into the old portal anymore.

Current NetBeans 11.2-beta3 has a 'NetBeans Plugin Portal' update center
with URL https://netbeans.apache.org/nb/updates/11.2/updates.xml.gz but it
contains the plugins of the old portal.

Regards,
Alex

Re: [news] Plugin Portal 3.0 on the horizon

[Alessandro]

Jiri, I have received the mail notifications from the system signaling the
approval for each NB version I applied to.

Thanks for the kind words, this plugin was more like a test bed before
applying it to my more important NB Spring Boot plugin.

Regards,
Alex

Il giorno mar 15 ott 2019 alle 11:46 Jiří Kovalský 
ha scritto:

> Hi Alessandro,
>
> that's perfect. I have approved your plugin and also added my Go
> votes so now you only need one more verification from some other
> verifier and your plugin will show up on the Update Center(s). I will
> talk to Geertjan in about 1.5 hour and ask him to add his Go vote too.
>
> And many thanks! Your plugin is great!
>
> -Jirka
>
> Dne 14. 10. 19 v 9:49 Alessandro napsal(a):
>
> > Hi Jiri,
> >I managed to submit my first plugin this morning following the steps
> in
> > the Help section.
> >
> > The plug-in is now listed as waiting approval, I have also requested
> > verification for a set of NB versions.
> >
> > What are the next steps?
> >
> > Regards,
> > Alex
> >
> > Il giorno gio 10 ott 2019 alle ore 00:11 Jiří Kovalský <
> > jiri.koval...@oracle.com> ha scritto:
> >
> >> Hello NetBeans people,
> >>
> >>  if you have ever fine-tuned your NetBeans IDE with some
> >> community-contributed plugin or you are a plugin developer yourself,
> >> please read this e-mail carefully.
> >>
> >>  The last reason for netbeans.org domain existence is the NetBeans
> >> Plugin Portal - our repository of NetBeans extensions. Given the
> >> original infrastructure is no longer maintained by Oracle and in order
> >> to avoid potential legal issues with hosting 3rd party binaries licensed
> >> under Apache incompatible licenses we have decided for a complete
> >> rewrite of the Plugin Portal website.
> >>
> >>  Today, we are happy to announce the result of our effort, the brand
> >> new Plugin Portal version 3.0 [1] which is running on the same Apache
> >> infrastructure which already hosts Synergy - the tests management tool
> >> for NetCAT programs.
> >>
> >> [1]
> https://urldefense.proofpoint.com/v2/url?u=http-3A__netbeans-2Dvm.apache.org_pluginportal_&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4&m=r2Pl4tAqfl2Fpue3mplTOSFb8KFLXurqgXTZVClkk7s&s=MwGXPH_8H_D5bcwkyWyt6T54TPgNB5F4KjTIBH6yvHs&e=
> >>
> >> The 3 most substantial changes if compared with Plugin Portal 2.0 are:
> >>
> >> * Only plugins published in the Maven Central Repository can be
> >> registered in the Plugin Portal 3.0.
> >> * Only NBM or JAR file types are supported binary formats.
> >> * Google SSO is used as authentication mechanism.
> >>
> >>  The concept of community controlled publishing of plugins on the
> >> Plugin Portal Update Center remains unchanged i.e. if two verifiers
> >> approve a plugin and nobody disapproves it, the plugin gets
> >> automatically added to the module catalog for appropriate NetBeans
> version.
> >>
> >>  Sounds good so far? Cool! The purpose of this message though is to
> >> ask for cooperation. :) As you could have guessed we need to load the
> >> new Plugin Portal with meaningful plugins so if you have developed a
> >> NetBeans plugin, please publish it in the Maven Central and then share
> >> it with others through the new Plugin Portal. And obviously sending us
> >> any feedback on the registration process or Plugin Portal's new user
> >> interface in general will be much appreciated! Bugs should be created
> >> against "updatecenters - Pluginportal" component.
> >>
> >>  Finally, once the final polishing is made, we will open source the
> >> codebase so that everyone can participate in improving the website. And
> >> if you are curious, the credit for creating the new Plugin Portal goes
> >> to Jan Pirek (jpirek). Hats off to you, Jan!
> >>
> >> Thanks and long live the Plugin Portal 3.0!
> >>
> >> Best regards,
> >> -Jirka
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> >> For additional commands, e-mail: dev-h...@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Mailing-2Blists&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=8_Pz0x0SKeT5e3IehhQKCbQ2xl3tz40jnCU133NrdP4&m=r2Pl4tAqfl2Fpue3mplTOSFb8KFLXurqgXTZVClkk7s&s=jmx1tgr_v8fpzHzpbQo945sWHgmI2m_0cb4Ivhi8_0U&e=
> >>
> >>
> >>
> >>
> >
>
> -
> 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: Cannot login on New Plugin Portal

[Alessandro]

I essentially followed the step by step instructions on the Dzone article
by Mohammed Nadeem mentioned on
https://cwiki.apache.org/confluence/display/NETBEANS/How+to+Upload+NetBeans+Modules+to+Maven+Central
(last page listed on the plugin portal help page).

The differences from the 2016 article were:
1- after opening the ticket on Sonatype Jira it is requested to create a
GitHub repo to demonstrate ownership of the account
2- the maven javadoc plug-in config to add to the Pom file is not correctly
reported in the article, refer to the Pom mentioned at the end
3- propagation of PGP signature requires some minutes so I initially got
failures due to unrecognized signatures
4- I had to add the developer information section to the Pom file

A novice might be confused by the maven release plugin way of working
(prepare/perform steps) and is absolutely needed to git reset hard the
commits made by the release plugin if something goes wrong and adjustment
commits are needed otherwise you are forced to advance the version without
a real reason.

Positive side effect of the strict maven release way of working
(snapshot/release version alternance) is the availability of development
NBM artifacts on Sonatype snapshot repository useful if some user wants to
be on the bleeding edge.

Regards,
Alex

Il giorno lun 14 ott 2019 alle 10:30 Geertjan Wielenga 
ha scritto:

> Hi Alex,
>
> On Sun, Oct 13, 2019 at 5:23 PM Alessandro  wrote:
>
> > Hi all,
> >   I just finished trying the new procedure for having a plugin available
> on
> > the new Plugin Portal.
> >
> > I successfully published the plugin on Maven Central (perhaps the biggest
> > step)
>
>
> Congratulations.:-)
>
> Did you document the process or can you remember it enough to provide some
> notes -- sure there's official Maven documentation about how to do the
> process, but what's your personal step by step approach that you
> implemented and the stumbling blocks encountered?
>
> Gj
>
>
>
>
> > now I am trying to log-in into the plugin portal to complete the
> > publishing process but after inserting my Google credentials the
> > "AddPlugin" button mentioned in the Help section is not available.
> >
> > I was able to log-in last friday just to have a look so this looks like a
> > temporary server problem, could anyone have a look?
> >
> > Regards,
> > Alex
> >
>

Re: [news] Plugin Portal 3.0 on the horizon

[Alessandro]

Hi Jiri,
  I managed to submit my first plugin this morning following the steps in
the Help section.

The plug-in is now listed as waiting approval, I have also requested
verification for a set of NB versions.

What are the next steps?

Regards,
Alex

Il giorno gio 10 ott 2019 alle ore 00:11 Jiří Kovalský <
jiri.koval...@oracle.com> ha scritto:

> Hello NetBeans people,
>
> if you have ever fine-tuned your NetBeans IDE with some
> community-contributed plugin or you are a plugin developer yourself,
> please read this e-mail carefully.
>
> The last reason for netbeans.org domain existence is the NetBeans
> Plugin Portal - our repository of NetBeans extensions. Given the
> original infrastructure is no longer maintained by Oracle and in order
> to avoid potential legal issues with hosting 3rd party binaries licensed
> under Apache incompatible licenses we have decided for a complete
> rewrite of the Plugin Portal website.
>
> Today, we are happy to announce the result of our effort, the brand
> new Plugin Portal version 3.0 [1] which is running on the same Apache
> infrastructure which already hosts Synergy - the tests management tool
> for NetCAT programs.
>
> [1] http://netbeans-vm.apache.org/pluginportal/
>
> The 3 most substantial changes if compared with Plugin Portal 2.0 are:
>
> * Only plugins published in the Maven Central Repository can be
> registered in the Plugin Portal 3.0.
> * Only NBM or JAR file types are supported binary formats.
> * Google SSO is used as authentication mechanism.
>
> The concept of community controlled publishing of plugins on the
> Plugin Portal Update Center remains unchanged i.e. if two verifiers
> approve a plugin and nobody disapproves it, the plugin gets
> automatically added to the module catalog for appropriate NetBeans version.
>
> Sounds good so far? Cool! The purpose of this message though is to
> ask for cooperation. :) As you could have guessed we need to load the
> new Plugin Portal with meaningful plugins so if you have developed a
> NetBeans plugin, please publish it in the Maven Central and then share
> it with others through the new Plugin Portal. And obviously sending us
> any feedback on the registration process or Plugin Portal's new user
> interface in general will be much appreciated! Bugs should be created
> against "updatecenters - Pluginportal" component.
>
> Finally, once the final polishing is made, we will open source the
> codebase so that everyone can participate in improving the website. And
> if you are curious, the credit for creating the new Plugin Portal goes
> to Jan Pirek (jpirek). Hats off to you, Jan!
>
> Thanks and long live the Plugin Portal 3.0!
>
> Best regards,
> -Jirka
>
> -
> 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: Cannot login on New Plugin Portal

[Alessandro]

Hi Jiri,
  I successfully logged-in from work (Windows 10, Chrome) and created a new
plugin request.

Will check again at home (Linux, Chrome) following your suggestions this
evening and let you know.

Thank you.

Regards,
Alex

Il giorno lun 14 ott 2019 alle ore 09:39 Jiří Kovalský <
jiri.koval...@oracle.com> ha scritto:

> Hello Alessandro,
>
> can you still reproduce it? I can sign in through Google and return
> authenticated to Plugin Portal just fine.
>
> 1. Is there anything suspicious in web console or network tab of your
> browser?
> 2. Does GET request for Google's iframe [1] return 200?
> 3. Does opening your Google calendar [2] display the sign-in window and
> then shows the calendar?
>
> [1] https://accounts.google.com/o/oauth2/iframe
> [2] https://www.google.com/calendar/render
>
> -Jirka
>
> Dne 13. 10. 19 v 17:23 Alessandro napsal(a):
>
> > Hi all,
> >I just finished trying the new procedure for having a plugin
> available on
> > the new Plugin Portal.
> >
> > I successfully published the plugin on Maven Central (perhaps the biggest
> > step) now I am trying to log-in into the plugin portal to complete the
> > publishing process but after inserting my Google credentials the
> > "AddPlugin" button mentioned in the Help section is not available.
> >
> > I was able to log-in last friday just to have a look so this looks like a
> > temporary server problem, could anyone have a look?
> >
> > Regards,
> > Alex
> >
>
> -
> 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
>
>
>
>

Cannot login on New Plugin Portal

[Alessandro]

Hi all,
  I just finished trying the new procedure for having a plugin available on
the new Plugin Portal.

I successfully published the plugin on Maven Central (perhaps the biggest
step) now I am trying to log-in into the plugin portal to complete the
publishing process but after inserting my Google credentials the
"AddPlugin" button mentioned in the Help section is not available.

I was able to log-in last friday just to have a look so this looks like a
temporary server problem, could anyone have a look?

Regards,
Alex

Re: nbm-maven-plugin detected wrong path

[Alessandro]

Hi Peter,
  I have defined the netbeans.installation property in
/.m2/settings.xml so that different developers can have their
paths set-up differently.

Here's the content of my settings.xml file:
http://maven.apache.org/SETTINGS/1.0.0";
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
https://maven.apache.org/xsd/settings-1.0.0.xsd";>


netbeans-installation

true



C:/Users/falappa/PortableApps/netbeans-8.2

C:/Users/falappa/Documents/nb8.2-userdir





It also defines a location of the user dir, this is handy to avoid feature
activation, maven index download and process every time I launch a
secondary NetBeans instance.
You can avoid the  part but in that case you have to explicit
enable the netbeans-installation profile when you run/debug your project.

Hope it helps.

Greets,
Alex

Il giorno gio 10 ott 2019 alle ore 08:48 Peter Cheung 
ha scritto:

> Hi All
>I check the source code of nbm-maven-plugin
> https://github.com/mojohaus/nbm-maven-plugin/blob/4f25f6a3f80f97a0fd9986b7df38e7e9ed58d263/nbm-maven-plugin/src/main/java/org/codehaus/mojo/nbm/RunNetBeansMojo.java
> . It has no code to set the variable "netbeans.installation", so it
> probably netbeans pass this var to it. Is there any UI/tool/whatever i can
> view the value of this variable?
> thanks
> Peter
> 
> From: Peter Cheung 
> Sent: Thursday, October 10, 2019 2:37 PM
> To: dev@netbeans.apache.org 
> Subject: nbm-maven-plugin detected wrong path
>
> Hi
> Why my nbm-maven-plugin is detecting a wrong path, so when i run the
> netbeans module, it said:
>
> Failed executing NetBeans: Error while executing process. Cannot run
> program "/Users/peter/workspace/netbeans-quick-outline/VALUE/bin/netbeans":
> error=2, No such file or directory
>
> When i click the about dialog, the "user directory" path is correct. I
> don't want to specific  in pom.xml, because not
> everyone using same installation path.
>
> Please tell me how to fix?
>
>
> Thanks
> From Peter
>

Re: [VOTE] Gradle Icon Colors (Just some silly UI one)

[Alessandro]

+1 green

Il giorno mar 8 ott 2019 alle 05:23 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Dear all,
>
> This is not that serious vote, like a release, versioning scheme, or
> release process, just on some colors.
>
> We have and issue
> (NETBEANS-2417)[https://issues.apache.org/jira/browse/NETBEANS-2417] to
> follow the branding change happened ago in Gradle. Please take a look on
> the attached screenshots issue.
>
> We are voting on the green or the white elephants on dark scheme.
>
> You can vote:
>
> +1 white or +1 green
>
> If it is indifferent to you please do not cast a vote!
>
> This thread would be open for at least 72 hours, if no one would vote,
> then I decide what would be in the PR for this.
>
>
> Happy voting!
>
> Laszlo Kishalmi
>
>
> -
> 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: NetBeans 11.2-beta1: broken pom.xml files editing

[Alessandro]

Hi Laszlo,
  thank you very much for suggesting this method. Will try later today.

Greets,
Alex

Il giorno mer 2 ott 2019 alle ore 19:32 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

>
> You can remove the ergonomic cluster from etc/netbeans.clusters, that
> make the other clusters activated by default.
>
> On 10/2/19 2:19 AM, Alessandro wrote:
> > Solved, my mistake.
> >
> > The second NetBeans instance had unactivated features, once I activated
> the
> > JavaSE feature all went to normal.
> >
> > Is there a way to launch a NetBeans with some features pre-activated?
> >
> > Regards,
> > Alex
> >
> > Il giorno mar 1 ott 2019 alle ore 16:08 Alessandro <
> alex.fala...@gmail.com>
> > ha scritto:
> >
> >> On further investigation this is less severe, it happens in a NetBeans
> >> 11.2-beta1 instance launched from another NetBeans 11.2-beta1 instance
> from
> >> a Maven NetBeans Module project. Maven projects open just fine in the
> >> parent instance and pom.xml files are edited via the specialized editor
> in
> >> it.
> >>
> >> It is however annoying as it impacts developing NetBeans plugins.
> >>
> >> Apologise for the alarming head-up.
> >>
> >> Regards,
> >> Alex
> >>
> >> Il giorno mar 1 ott 2019 alle ore 15:56 Geertjan Wielenga <
> >> geert...@apache.org> ha scritto:
> >>
> >>> Can you reproduce the issue with fresh userdir and cachedir?
> >>>
> >>> Gj
> >>>
> >>> On Tue, 1 Oct 2019 at 15:55, Alessandro 
> wrote:
> >>>
> >>>> Hi all,
> >>>>I have just realized that with NetBeans 11.2-beta1 pom.xml files
> are
> >>>> opened in a vanilla XML editor instead of the specialized POM editor.
> >>>>
> >>>> This is a major regression in my opinion cause we loose code
> templates,
> >>>> groupId/artifactId/version completion for dependencies, code
> generation,
> >>>> effective POM inspection, POM dependency graph etc.
> >>>>
> >>>> Can anyone confirm?
> >>>>
> >>>> I also see a new "Open Advanced..." menu item in the context menu of a
> >>>> pom.xml file in Project view that does nothing.
> >>>>
> >>>> Should I open an issue on JIRA?
> >>>>
> >>>> Regards,
> >>>> Alex
> >>>>
>
> -
> 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: NetBeans 11.2-beta1: broken pom.xml files editing

[Alessandro]

Solved, my mistake.

The second NetBeans instance had unactivated features, once I activated the
JavaSE feature all went to normal.

Is there a way to launch a NetBeans with some features pre-activated?

Regards,
Alex

Il giorno mar 1 ott 2019 alle ore 16:08 Alessandro 
ha scritto:

> On further investigation this is less severe, it happens in a NetBeans
> 11.2-beta1 instance launched from another NetBeans 11.2-beta1 instance from
> a Maven NetBeans Module project. Maven projects open just fine in the
> parent instance and pom.xml files are edited via the specialized editor in
> it.
>
> It is however annoying as it impacts developing NetBeans plugins.
>
> Apologise for the alarming head-up.
>
> Regards,
> Alex
>
> Il giorno mar 1 ott 2019 alle ore 15:56 Geertjan Wielenga <
> geert...@apache.org> ha scritto:
>
>> Can you reproduce the issue with fresh userdir and cachedir?
>>
>> Gj
>>
>> On Tue, 1 Oct 2019 at 15:55, Alessandro  wrote:
>>
>> > Hi all,
>> >   I have just realized that with NetBeans 11.2-beta1 pom.xml files are
>> > opened in a vanilla XML editor instead of the specialized POM editor.
>> >
>> > This is a major regression in my opinion cause we loose code templates,
>> > groupId/artifactId/version completion for dependencies, code generation,
>> > effective POM inspection, POM dependency graph etc.
>> >
>> > Can anyone confirm?
>> >
>> > I also see a new "Open Advanced..." menu item in the context menu of a
>> > pom.xml file in Project view that does nothing.
>> >
>> > Should I open an issue on JIRA?
>> >
>> > Regards,
>> > Alex
>> >
>>
>

Re: NetBeans 11.2-beta1: broken pom.xml files editing

[Alessandro]

On further investigation this is less severe, it happens in a NetBeans
11.2-beta1 instance launched from another NetBeans 11.2-beta1 instance from
a Maven NetBeans Module project. Maven projects open just fine in the
parent instance and pom.xml files are edited via the specialized editor in
it.

It is however annoying as it impacts developing NetBeans plugins.

Apologise for the alarming head-up.

Regards,
Alex

Il giorno mar 1 ott 2019 alle ore 15:56 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> Can you reproduce the issue with fresh userdir and cachedir?
>
> Gj
>
> On Tue, 1 Oct 2019 at 15:55, Alessandro  wrote:
>
> > Hi all,
> >   I have just realized that with NetBeans 11.2-beta1 pom.xml files are
> > opened in a vanilla XML editor instead of the specialized POM editor.
> >
> > This is a major regression in my opinion cause we loose code templates,
> > groupId/artifactId/version completion for dependencies, code generation,
> > effective POM inspection, POM dependency graph etc.
> >
> > Can anyone confirm?
> >
> > I also see a new "Open Advanced..." menu item in the context menu of a
> > pom.xml file in Project view that does nothing.
> >
> > Should I open an issue on JIRA?
> >
> > Regards,
> > Alex
> >
>

NetBeans 11.2-beta1: broken pom.xml files editing

[Alessandro]

Hi all,
  I have just realized that with NetBeans 11.2-beta1 pom.xml files are
opened in a vanilla XML editor instead of the specialized POM editor.

This is a major regression in my opinion cause we loose code templates,
groupId/artifactId/version completion for dependencies, code generation,
effective POM inspection, POM dependency graph etc.

Can anyone confirm?

I also see a new "Open Advanced..." menu item in the context menu of a
pom.xml file in Project view that does nothing.

Should I open an issue on JIRA?

Regards,
Alex

Re: Apache NetBeans 11.2-beta1 Is Available for Testing!

[Alessandro]

Hi all,
   took NB11.2-beta1 for a spin. Tested on Windows10 with OpenJDK11.

Mostly played with maven projects, installed my favourite plugins, done
some NB plugin development. No new feature tested (e.g. no JDK 13 yet).

I just had a small glitch: just after feature activation compile on save in
maven project was greyed out, all solved after restarting.

As far as performance goes I have not "perceived" a lot of difference with
respect to NB11.1 on Windows 10. I am perceiving a difference between
Windows 10 (work) and Linux (home) but this is a different story.

I have yet to test the installer enhancements (selection of cluster at
installation time) and JDK 13 support (intrigued by text blocks).

All in all a solid point release.

Greets,
Alex

Il giorno mer 25 set 2019 alle ore 12:17 Neil C Smith 
ha scritto:

> Dear Community,
>
> I'd like to announce that the first beta build for Apache NetBeans
> 11.2 from the release112 branch is available for download. Apologies
> for the delay. Further betas will be released on Oct 2nd and 9th as
> required. Release is aimed for Oct ~15th.
>
> As per the release schedule, NB 11.2 is a non-LTS release, and will
> not have a full NetCAT process.  However, feedback and testing from
> those on the dev@ and netcat@ lists would still be appreciated,
> particularly around new features.  Please file issues in JIRA as
> necessary, with the affects and fix versions set to 11.2. Please take
> note of the Bug Priority Guidelines (link below), in particular so
> that we can address critical and blocking issues if they arise.
>
> **If making PRs to fix issues, please add the 11.2 milestone and add
> me as one of the reviewers**
>
> See the artefacts here:
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/14/artifact/dist/
>
> The binary you most likely need is:
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/job/netbeans/job/release112/14/artifact/dist/netbeans-11.2-bin.zip
>
> The SHA512 sums if you would like to check them are provided there as
> well as here:
>
> fc6a67d675048cf6631785b6dd604eb4ca904609c58832b6573194b8a4ecaf95c73bdc079a1db2ffe082d2ce1f49fd413ff0a8e8c711d50c3b667447df0700ae
>  ./netbeans-11.2-bin.zip
>
> 50430ccc87abd406979136b497e64830f34e31b8c778b38e7908d1297bb62e0b57fa33361f0ee2d80a62da3a622022e42b41a5e2d309e01bc39419f44c101a4b
>  ./netbeans-11.2-source.zip
>
>
> New build infrastructure - known issues / changes:
> As you may notice from the links, this is the first release using the
> new build templates and Jenkins task (thanks Eric!). One thing this
> does is switch from hardcoded versions across the code base to filling
> this in from a central configuration file based on git branch and
> hash.
>
> * Local building from the source bundle is not correctly picking up
> the git info file in the source bundle. Run `cp
> nbbuild/gitinfo.properties nbbuild/build/` before running Ant (or
> otherwise manually create the nbbuild/build folder and copy
> gitinfo.properties into it). Will be fixed before full release as it's
> a blocking issue.
> * A git checkout of the release branch will also not correctly pick up
> the required git info - this will be looked at before release too.
> * File names are not currently marked with the beta1 suffix. On the
> other hand, the splash and window are. Win some, lose some!
> * The userdir will now be named differently for each beta and the final
> release.
> * Implementation versions across builds of the same sources still
> differ. It is planned to fix this prior to release (separate thread to
> follow).
>
>
> Release schedule :
> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
> Bug Priority Guidelines :
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines
> NB 11.2 major changes :
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.2
> ( although that's not yet updated, so see also
> https://github.com/apache/netbeans/milestone/3?closed=1 )
>
>
> Thanks and best wishes,
>
> Neil
> Volunteer Release Manager for Apache NetBeans 11.2
>
> -
> 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: Can anyone give me a help about developing antlr formatter

[Alessandro]

Thanks everybody for the suggestions.

@Mario Schroeder i will start from your plugin project as it seems a small
focused example of how to add a new language editor to NetBeans.

@Eric Bresie the plugin you mention is to develop ANTLR grammars and it
will be certainly useful but it is not aimed to automatically generate the
NetBeans Lexer and Parser plumbing.

@Siddesh Rane the C++ module would be no doubt a thorough example of adding
a new language editor to NetBeans but I am afraid I would get lost in its
big sources.

Regards,
Alex

Il giorno lun 23 set 2019 alle ore 09:44 Siddhesh Rane <
siddheshr...@disroot.org> ha scritto:

> The C++ module uses ANTLR for parsing and also provides formatting
> support. That might be useful
>
> Regards
> Siddhesh Rane
>
> September 23, 2019 4:08 AM, "Eric Bresie"  wrote:
>
> > Also noticed there is a Netbeans plugin list on the Tools section of the
> ANTLR.org site.
> >
> > https://www.antlr.org/tools.html
> >
> > Eric Bresie
> > ebre...@gmail.com
> >
> >> On September 20, 2019 at 4:26:51 AM CDT, Mario Schroeder <
> ma.schroe...@gmail.com> wrote:
> >> Hi,
> >>
> >> maybe this one can help you as well:
> >> https://github.com/mario-s/nb-hyperledger
> >> It uses a ANTLR Grammar to generate Lexer and Parser.
> >>
> >> A lot of ANTLR samples can be found in this repository:
> >> https://github.com/antlr/grammars-v4
> >>
> >> Greetings,
> >> Mario
> >>
> >> Am Fr., 20. Sept. 2019 um 10:29 Uhr schrieb Alessandro <
> >> alex.fala...@gmail.com>:
> >>
> >> Hi Tim,
> >> I am interested too.
> >>
> >> I have a plugin with an editor using a JFlex based lexer and a Parboiled
> >> based parser and I would like to move to a unified solution with an
> ANTLR
> >> based lexer and parser.
> >>
> >> It would be wonderful if you could share something.
> >>
> >> Greets,
> >> Alex
> >>
> >> Il giorno lun 16 set 2019 alle ore 01:48 Tim Boudreau <
> niftin...@gmail.com
> >>>
> >> ha scritto:
> >>
> >>> I have some stuff under development that might be useful for that. You
> >> want
> >>> to format a language that has an Antlr grammar, right?
> >>>
> >>> -Tim
> >>>
> >>> On Sun, Sep 15, 2019 at 11:43 AM Peter Cheung 
> >>> wrote:
> >>>
> >>>> Hi All
> >>>> Can anyone give me a help about developing antlr formatter? Where
> >> i
> >>>> can get an example to develop a custom formatter?
> >>>> Thanks
> >>>> From Peter
> >>>>
> >>> M
> >>> --
> >>> http://timboudreau.com
> >>>
>
> -
> 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: Can anyone give me a help about developing antlr formatter

[Alessandro]

Hi Tim,
  I am interested too.

I have a plugin with an editor using a JFlex based lexer and a Parboiled
based parser and I would like to move to a unified solution with an ANTLR
based lexer and parser.

It would be wonderful if you could share something.

Greets,
Alex


Il giorno lun 16 set 2019 alle ore 01:48 Tim Boudreau 
ha scritto:

> I have some stuff under development that might be useful for that. You want
> to format a language that has an Antlr grammar, right?
>
> -Tim
>
> On Sun, Sep 15, 2019 at 11:43 AM Peter Cheung 
> wrote:
>
> > Hi All
> >  Can anyone give me a help about developing antlr formatter? Where i
> > can get an example to develop a custom formatter?
> > Thanks
> > From Peter
> >
> M
> --
> http://timboudreau.com
>

Re: Apache NetBeans 11.2 merge window closed

[Alessandro]

Ideally this is what GitHub Milestone concept is for.
If you assign a PR to a milestone a nice progress is shown at
https://github.com/apache/netbeans/milestone/3 while a summary view of all
milestones with due dates at https://github.com/apache/netbeans/milestones .
I think Junichi tagged all PR for the NB 11.2 cycle so the requested report
is at  https://github.com/apache/netbeans/milestone/3?closed=1 .

Greets,
Alex

Il giorno lun 16 set 2019 alle ore 14:41 Neil C Smith 
ha scritto:

> On Mon, 16 Sep 2019 at 13:28, Geertjan Wielenga 
> wrote:
> >
> > It would be good to have a link providing the full list of all PRs unique
> > to 11.2, then I'll make a draft 'what's new' document on the Wiki for
> that,
> > to be transferred once finalized to netbeans.apache.org.
>
> I'll have a look at that shortly, although if you use the link I
> shared with you for 11.1 and change the date range it should work.
>
> 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: Please fill in a new Java developer survey

[Alessandro]

Done, as well.

Il giorno lun 12 ago 2019 alle ore 11:55 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> Hi all,
>
> In many ways, developer surveys are problematic and their results dubious,
> however it would be nice to see NetBeans better represented in some of them
> -- there's a new one that takes about 5 minutes to complete and is focused
> on a number of recent developments in the Java ecosystem:
>
> https://t.co/Oc9OpLiB0A
>
> It really takes about 5 minutes, would be great if everyone would take a
> moment to fill it in and highlight in it their usage of NetBeans, will help
> a lot in terms of visibility and so on.
>
> Thanks,
>
> Gj
>

Re: Congratulations to Neil!

[Alessandro]

Hi,
big thumbs up to Neil for his work as  Release Manager! And of course to
all others involved!

Regards

Il giorno lun 22 lug 2019 alle ore 13:28 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> Hi all,
>
> With the 11.1 release wrapped up, let's take a moment to thank Neil for his
> great work as release manager.
>
> We can and will evaluate the release in various ways, though the most
> important aspect of it is that it succeeded, we have our first release as
> top level Apache project, and no small reason for that is Neil pulling
> everything together and getting everyone to work together smoothly and
> painlessly.
>
> Plus, thanks to Neil we now have a predictable release cycle with quarterly
> releases — that is fantastic and something I’d never have thought doable.
>
> I hope Neil will consider doing at least the 11.2 release too, since that
> will enable any kinks in the process to be ironed out in preparation for
> the next volunteer release manager, like Laszlo did two releases as well
> before him.
>
> Kind regards and congrats to all of us as well,
>
> Gj
>

Re: [VOTE] Release Apache NetBeans 11.1 [vote candidate 2]

[Alessandro]

+1 (not binding)

Downloaded and verified sha512 digest
Checked NOTICE and LICENSE
Built basic cluster with Oracle JDK 8 on Ubuntu Linux 18.04
Launched built artefact

Greets,
Alex


Il giorno mar 16 lug 2019 alle ore 17:58 Neil C Smith 
ha scritto:

> Dear all,
>
> This is our second voting candidate for the 11.1 release of Apache
> NetBeans, following 11.1-beta4 and a fix to the critical issue that
> made us pull the first vote.  There have been no changes between beta4
> and this voting candidate.
>
> Apache NetBeans 11.1 constitutes all clusters in the Apache NetBeans
> Git repo, 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/11.1-vc2/
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.1-vc2/
>
> Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and
> NOTICE files, as well as a README file with build instructions, which
> are the same as these:
> https://github.com/apache/netbeans/blob/release111/README.md
>
> We are voting on:
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc2/netbeans-11.1-vc2-source.zip
>
> SHA512:
>
> 44d551f579587eafea30b3b3d9a9095520fb2dc028d63a1e7a31c6e52882c371c8f8f1ac32d836694fefea269e52bf092e1976cf2c58accd36c816e009248e08
>  ./netbeans-11.1-vc2-source.zip
>
> KEYS file:
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
> Apache NetBeans Git Repo tag: 11.1-vc2 :
> https://github.com/apache/netbeans/tree/11.1-vc2
>
> Note: NetBeans license violation checks are managed via the
> rat-exclusions.txt file:
>
> https://github.com/apache/netbeans/blob/release111/nbbuild/rat-exclusions.txt
>
> Rat report shows no unknown licenses, except for license files:
>
> https://builds.apache.org/job/netbeans-release/428/artifact/rat-release-temp/nbbuild/build/rat-report.txt
>
> Release specific wiki page:
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1
>
>
> How (and what) to try out with the release:
>
> 1. Download the artefact to be voted on and unzip it.
> 2. Check that the artefact does not contain any jar files, except for:
> -
> platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar
> - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
> - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
> - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
> - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
> which are only jars by their name
> 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.
>
> This vote is going to be open at least 72 hours, vote with +1, 0, and
> -1 as usual.  Please mark your vote with (binding) if you're a
> NetBeans PMC member to help with voting admin.  NetBeans 11.1 will be
> released if and when this vote passes.
>
> Convenience binaries, not relevant for voting purposes, are staged at
> the build artefacts links above.
>
> Thank you for all the hard work!
>
> Best wishes,
>
> Neil
> Volunteer Release Manager for Apache NetBeans 11.1
>
> -
> 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 11.1-beta4 Is Available for Testing!

[Alessandro]

Hi all,
  took beta4 for a spin on Linux.

I can confirm the release fixes the major problems on JavaEE8 support
reported against vc1, I also verified that my previously reported
NETBEANS-2836  and
NETBEANS-2791  seem to
be fixed as well.
I will test drive beta4 on Windows next days and report back.

Keep up the good work!

Greets,
Alex

Il giorno sab 13 lug 2019 alle ore 18:43 Neil C Smith 
ha scritto:

> Dear Community,
>
> Please find details of Apache NetBeans 11.1-beta4 below.
> Unfortunately, we had to pull the release vote for NB 11.1 due to a
> critical issue being found -
> https://issues.apache.org/jira/browse/NETBEANS-2824  This only
> occurred after beta3 because another fix exposed it - c'est la vie.
>
> A fix for the critical issue, and fixes for a few other major issues,
> are now in this fourth beta - see the full details of changes between
> vc1 and beta4 at https://github.com/apache/netbeans/pull/1374
>
> Please give this beta a good battle test, particularly around the
> areas that have been fixed.  Please also check the sources as you
> would in a release vote, and ensure the few minor issues raised there
> are gone.
>
> All being well, we will have a vote on a second release build in the
> middle of next week.  Ideally without any code changes from this beta.
> Responses of "everything now looks OK", as well as problems, would be
> appreciated!
>
> See the artefacts here:
> https://builds.apache.org/job/netbeans-release/426/artifact/dist/
>
> The binary you most likely need is:
>
> https://builds.apache.org/job/netbeans-release/426/artifact/dist/netbeans-11.1-beta4-bin.zip
>
> Please also check the full sources used for voting:
>
> https://builds.apache.org/job/netbeans-release/426/artifact/dist/netbeans-11.1-beta4-source.zip
>
> The SHA512 sums if you would like to check them are provided there as
> well as here:
>
> 026b5d86b18f04f89aa096891e331c30973c0f6e0883daf2de13e31d5b8086eb5fc1b57973648caad6adc6d45a7678a5490a483ccd2426709e9b78abe1d5e8ec
>  ./netbeans-11.1-beta4-bin.zip
>
> 1ab9f36ea5287e68a141ade628860a28992b68d2033fbcddf8f90781309b112791db6278df98e3be1193a5bbc2ed2ae3c8d0c93c0ac431065dfd4a7f64f3f33c
>  ./netbeans-11.1-beta4-source.zip
>
> b02ec90165a432ecdac63f430f5a32e9bb6c993e0f7c38374246dc2abd45f17ee72e9c5232239d1c00ff843ae5b8eebad425d69161f97d8a86b15930bca489a2
>  ./netbeans-platform-11.1-beta4-bin.zip
>
> 363c64f0eb89c68e0d2cb220f1b34043c89625b7ce72692c427bdda9abf7fbfef7e0d9cf0a4ab84ed597456f664ff6b84bd11b91b2f199691c269d1e6d9ea557
>  ./netbeans-platform-11.1-beta4-source.zip
>
> Thanks those who helped sort issues, and thanks everyone for another
> round of testing,
>
> Best wishes,
>
> Neil
>
> Voluntary Release Manager for Apache NetBeans 11.1
>
> -
> 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: [URGENT] Java EE 8 support fixes / beta4?

[Alessandro]

Hi Neil,
  could the reason be this instead:

BUILD FAILED
/home/travis/build/apache/netbeans/scratch/nbbuild/build.xml:2167:
Failed Rat test(s):
Unapproved license in 1 file(s)
https://github.com/apache/netbeans/tree/master/enterprise/j2ee.dd/src/org/netbeans/modules/j2ee/dd/impl/resources/web-app_4_0.mdd

At the top of Travis log?
Just guessing honestly.

Hope this helps.

Greets,
Alex

Il giorno ven 12 lug 2019 alle ore 16:40 Neil C Smith 
ha scritto:

> Hi,
>
> Josh and I could do with someone having a quick look at why the Travis
> test on https://github.com/apache/netbeans/pull/1375 is failing?  It's
> been retriggered a couple of times so it's not a one-off glitch.
>
> It says it's failing on ant verify-libs-and-licenses.  Neither of us
> can replicate that locally.
>
> So, we either do beta4 (and therefore release) without this fix, or
> delay the beta, get a fresh pair of eyes on this, and hopefully
> include it.  I'm going with the latter for now, which means beta4
> won't be today.
>
> Full Travis message below.
>
> Thanks, Neil
>
> travis_time:start:204f886a
>  [0K$ if [ "x$LICENSE" == "xtrue" ]; then ant -quiet
> verify-libs-and-licenses
> -Dverify-libs-and-licenses.haltonfailure=true; fi
>  [echo] Bootstrapping NetBeans-specific Ant extensions...
>  [echo] Downloading external binaries (*/external/ directories)
> for cluster.config=release...
>
> BUILD FAILED
> /home/travis/build/apache/netbeans/nbbuild/build.xml:1584: Failed
> VerifyLibsAndLicenses test(s):
> Some binaries were found outside of /external/ directories
> (edit nbbuild/antsrc/org/netbeans/nbbuild/extlibs/ignored-binaries as
> needed)
> scratch/nb/ide.launcher/external/launchers-10.0.zip
> scratch/nbbuild/installer/jnlp/external/jnlp-definitions-7.0.jar
>
> scratch/nbbuild/installer/jnlp/external/webstart-jnlp-servlet-1.0-beta-7.jar
>
> -
> 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 11.1 [vote candidate 1]

[Alessandro]

Hi Laszlo,
  I already reported the NOTICE inconsistency.

Neil explained that the NOTICE file in the zip is generated by an Ant task
that takes nbbuild/notice-stub.txt as a header, the NOTICE file in the root
of the repo is not going to be distributed.
Maybe it would be better to delete it?

Greets,
Alex

Il giorno ven 12 lug 2019 alle ore 00:54 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Here is it: https://github.com/apache/netbeans/pull/1370
>
> As of the date in the NOTICE file, we need to check the build as both on
> master and on release111 the NOTICE file is different than the one ended
> up in the zip and both has the correct year: 2019.
>

Re: [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

[Alessandro]

+1

Don't know if this matters a lot but the NOTICE file in the source archive
is completely different from that on the git repository (copyright end
year, additional license statements for Kotlin, IntelliJ IDEA, Struts,
Jakarta Validator).

Steps:
- Verified sha512
- Unzipped source archives
- Verified LICENSE
- NOTICE file different from repo but okaish
- Compiled with OpenJDK8
- Run compiled binary with OpenJDK8

Further testing performed on convenience binary.

Regards,
Alex

Il giorno mer 10 lug 2019 alle ore 21:41 Neil C Smith 
ha scritto:

> Dear all,
>
> This is our first voting candidate for the 11.1 release of Apache NetBeans.
>
> Apache NetBeans 11.1 constitutes all clusters in the Apache NetBeans
> Git repo, 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/11.1-vc1/
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.1-vc1/
>
> Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and
> NOTICE files, as well as a README file with build instructions, which
> are the same as these:
> https://github.com/apache/netbeans/blob/release111/README.md
>
> We are voting on:
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc1/netbeans-11.1-vc1-source.zip
>
> SHA512:
>
> 7f49cfca8d27f2e08d0e5d9b4f61d70baddfdfa013f4a783feb2a1e203d7a1c7208321cdb0be7aa49d469c027e221999c8c0e4b9d911eec35a7d2e3cf8859466
>  ./netbeans-11.1-vc1-source.zip
>
> KEYS file:
> https://dist.apache.org/repos/dist/release/netbeans/KEYS
>
> Apache NetBeans Git Repo tag: 11.1-vc1 :
> https://github.com/apache/netbeans/tree/11.1-vc1
>
> Note: NetBeans license violation checks are managed via the
> rat-exclusions.txt file:
>
> https://github.com/apache/netbeans/blob/release111/nbbuild/rat-exclusions.txt
>
> Rat report shows no unknown licenses, except for license files:
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-release/423/artifact/rat-release-temp/nbbuild/build/rat-report.txt
>
> Release specific wiki page:
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1
>
>
> How (and what) to try out with the release:
>
> 1. Download the artefact to be voted on and unzip it.
> 2. Check that the artefact does not contain any jar files, except for:
> -
> platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar
> - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
> - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
> - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
> - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
> which are only jars by their name
> 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.
>
> This vote is going to be open at least 72 hours, vote with +1, 0, and
> -1 as usual.  Please mark your vote with (binding) if you're a
> NetBeans PMC member to help with voting admin.  NetBeans 11.1 will be
> released if and when this vote passes.
>
> Convenience binaries, not relevant for voting purposes, are staged at
> the build artefacts links above.
>
>
> Thank you for all the hard work!
> And fingers X'd my first release voting thread is all correct - speak
> up if there are any issues.
>
> Best wishes,
>
> Neil
> Volunteer Release Manager for Apache NetBeans 11.1
>
> -
> 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 11.1-beta3 Is Available for Testing!

[Alessandro]

Hi Neil,
  my bad I haven't looked if it was already reported. I have resolved my
issue as duplicate.

Greets,
Alex

Il giorno gio 4 lug 2019 alle ore 19:22 Neil C Smith 
ha scritto:

> On Thu, 4 Jul 2019 at 15:06, Alessandro  wrote:
> > I found and reported NETBEANS-2801
> > <https://issues.apache.org/jira/browse/NETBEANS-2801>
> IllegalSateException
> > thrown when installing nbjavac plugin with OpenJDK11
>
> Thanks!  This is duplicated a lot across every release we've had,
> although doesn't seem to have affected usage. Not great user
> experience though.  eg.
>
> https://issues.apache.org/jira/browse/NETBEANS-2558?jql=project%20%3D%20NETBEANS%20AND%20resolution%20%3D%20Unresolved%20AND%20text%20~%20%22accept%20fragment%20StandardModule%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>
> At some point we need to make some better sense of JIRA.
>
> 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 11.1-beta3 Is Available for Testing!

[Alessandro]

Dear all,
  I continued testing beta3, this time trying to run on OpenJDK11 instead
of OpenJDK8 there is something fishy with JavaShell when executed with the
classpath of a project but I must investigate. I can confirm some issues
with JavaEE maven projects have been fixed.

I found and reported NETBEANS-2801
  IllegalSateException
thrown when installing nbjavac plugin with OpenJDK11

On a side note, why an Apache Tomcat server cannot be used as a Java EE 8
Web application server? Version 9.x should support the necessary Servlet,
JSP, EL etc. specification versions.

Regards,
Alex

Il giorno gio 4 lug 2019 alle ore 10:23 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> Yes, Gaurav is working on this.
>
> Any other comments on beta-3?
>
> Gj
>
> On Thu, Jul 4, 2019 at 10:22 AM Patrick Musembi 
> wrote:
>
> > I also noticed this ...
> >
> > On Thu, Jul 4, 2019, 05:38 chege  wrote:
> >
> > > Payara micro wizard is still stuck at 'finding feature'.
> > > Ubuntu Linux 18.04, OpenJdk 11.
> > >
> > > On Wed, 2019-07-03 at 18:52 +0100, Neil C Smith wrote:
> > > > Dear Community,
> > > >
> > > > I'd like to announce that the third beta build for Apache NetBeans
> > > > 11.1 from the release111 branch is available for download.
> > > >
> > > > Details of changes between beta2 and beta3 are at
> > > > https://github.com/apache/netbeans/pull/1353
> > > >
> > > >
> > > > As per the recently agreed release schedule, NB 11.1 is a non-LTS
> > > > release, and will not have a full NetCAT process.  However, feedback
> > > > and testing from those on the dev@ and netcat@ lists would still be
> > > > appreciated, particularly around new features.  Please file issues in
> > > > JIRA as necessary, with the affects and fix versions set to 11.1.
> > > > Please take note of the Bug Priority Guidelines, in particular so
> > > > that
> > > > we can address critical and blocking issues if they arise.
> > > >
> > > > **If making PRs to fix issues, please tag with NB 11.1 and add me as
> > > > a
> > > > reviewer**
> > > >
> > > > All being well, this will be the final beta.  The voting candidate
> > > > will be created July ~10th assuming any critical and blocking issues
> > > > are resolved.  The final NB 11.1 release is scheduled for July ~15th.
> > > >
> > > > Release schedule :
> > > >
> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
> > > > Bug Priority Guidelines :
> > > >
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines
> > > > NB 11.1 major changes :
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1
> > > >
> > > >
> > > > See the artefacts here:
> > > > https://builds.apache.org/job/netbeans-release/419/artifact/dist/
> > > >
> > > > The binary you most likely need is:
> > > >
> > >
> > >
> >
> https://builds.apache.org/job/netbeans-release/419/artifact/dist/netbeans-11.1-beta3-bin.zip
> > > >
> > > > The SHA512 sums if you would like to check them are provided there as
> > > > well as here:
> > > >
> > > > d467538043e3d6aef921b583c8af9e5174afaaa442cf875b9e766d638d5c5e12cfebd
> > > > 3ba037daf906bff0584493fffa8c618fe5c253167c993d2510064b0c3da
> > > >  ./netbeans-11.1-beta3-bin.zip
> > > > 53afb6a9a625bde4f2e35f98748ae2b07b877db3f862f64ffc9c8ca1e14110feab87d
> > > > f3e3ea5dfa88f317e42748a16cccdf1af43c37eaa1413086528be76
> > > >  ./netbeans-11.1-beta3-source.zip
> > > > 1ffd0aaef2098439a3f1645bf90dd7e127fc5426154a891bf900e2dc2b355f4886dab
> > > > c3552ebe9411311d4e5e16f5a2921b3e911354b581eb9a21eb0332978e1
> > > >  ./netbeans-platform-11.1-beta3-bin.zip
> > > > 9460e85b39d455c0c0741ca99226bde1b92aa9ee0e86753515fccd33b159f766558e5
> > > > f5af48d617542dcaad231608e9b55b99abda137c824871c734e6065b460
> > > >  ./netbeans-platform-11.1-beta3-source.zip
> > > >
> > > >
> > > > Thanks and best wishes,
> > > >
> > > > Neil
> > > >
> > > > Voluntary Release Manager for Apache NetBeans 11.1
> > > >
> > > > -
> > > > 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 11.1-beta2 Is Available for Testing!

[Alessandro]

Hi Geertjan,
  I will try the recently released beta3 and hope to provide a PR for one
of the problems I found.

As far as contributing NB Spring Boot plugin to Apache it is certainly
doable and I am not against it.
The code is already Apache 2.0 licensed and all the dependencies used
should have a compatible license.
One advantage of continuing to maintain and distribute a plugin is that
allows to support users on different versions of NetBeans (back to NB 8.1
currently) while after moving into NetBeans new features would be available
only on newer versios of NetBeans.
Beware that due to real life impediments I have less free time to devote to
NB Spring Boot plugin thus I cannot guarantee to be able to actively
maintain it once donated.

Regards,
Alex

Il giorno mer 3 lug 2019 alle ore 16:06 Geertjan Wielenga <
geert...@apache.org> ha scritto:

> Hi Alex,
>
> I think Josh has changed the opinionatedness in the meantime. Thanks for
> your feedback and indeed please continue trying things out in beta-3, feel
> free also to provide pull requests, of course.
>
> On a different but related note -- maybe we could bring in your Spring Boot
> functionality as a standard part of Apache NetBeans in 11.2, i.e., October?
> I.e., would/could you donate that code to Apache NetBeans and work on it
> further within our shared Apache NetBeans GitHub? Something to think about,
> would be really cool.
>
> Gj
>
> On Wed, Jul 3, 2019 at 4:00 PM Alessandro  wrote:
>

Re: Beta 2 Installers - Re: Apache NetBeans 11.1-beta2 Is Available for Testing!

[Alessandro]

Dear all,
  I have tested the linux installer on an Ubuntu 18.04 linux distribution.

The executable shell script executed correctly, the installer succesfully
picked an Oracle JDK 8 default jdk (I also have an Oracle JDK 7 installed)
and presented the wizard to ask for installation location and to confirm
the JDK to use for running NetBeans.

Despite being only ca 180 Mb in size the installer correctly indicates that
the final occupied space will be 600 Mb. I wonder how this is achieved,
perhaps pack200 compression? As a comparison the corresponding convenience
binary zip is ca 330 Mb in size.

The installer correctly produces .desktop launcher files and places them
one in the desktop folder and one in the launchers folder (usually
$HOME/.local/share/applications) so that Apache NetBeans can be launched
either double clicking on the desktop icon or via the desktop environment
app launching mechanism. The launcher files specify the correct application
name and point correctly to the new Apache NetBeans logo icon.

If at all possible I would change the produced .desktop file name: it is
currently Apache NetBeans-11.1.desktop , note the space, while it would be
better apache-netbeans-11.1.desktop , all lowercase and no space. Note that
modern desktop environments show the value of the name property contained
in the desktop file not the desktop file name itself.

Wonderful work Reema. Looking forward to having convenience installers for
the final NetBeans 11.1 release.

Regards,
Alex

Il giorno ven 28 giu 2019 alle ore 09:19  ha
scritto:

> Hi,
>
> Apache NetBeans 11.1 beta 2 Installers are temporarily hosted for
> testing on a branch in my github fork here:
>
>
> https://github.com/rtaneja1/netbeans/blob/installer-bin-11-1/nbbuild/installer/binaries/Apache-NetBeans-11.1-bin-windows-x64.exe
>
>
> https://github.com/rtaneja1/netbeans/blob/installer-bin-11-1/nbbuild/installer/binaries/Apache-NetBeans-11.1-bin-linux-x64.sh
>
>
> https://github.com/rtaneja1/netbeans/blob/installer-bin-11-1/nbbuild/installer/binaries/Apache-NetBeans-11.1-bin-macosx.dmg
>
> You can use download button on respective pages.
>
>
> Windows installer(unsigned) and Linux installer are also available from
> Jenkins build job:
>
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/
>
>
> Thanks,
>
> Reema
>
>
>
> On 26/06/19 11:56 PM, Neil C Smith wrote:
> > Dear Community,
> >
> > I'd like to announce that the second beta build for Apache NetBeans
> > 11.1 from the release111 branch is available for download.
> >
> > Key changes since beta1 include integration of Java EE 8 and Payara
> > support via agreed feature freeze bypass - testing in these areas
> > would be very appreciated.  Full details of changes between beta1 and
> > beta2 are at
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_netbeans_pull_1330&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0&m=nteZCygUuT4srtcV4loU0XYSyVCAyWgSeDUCG0BZ-jo&s=IwOZYjJGK3HhXaOJRVLgtD-h-S6jDYNw1BZ9Jzk&e=
> >
> >
> > As this build is for testing purposes only, we are not going to do the
> > release dance and voting around it (and as we're not voting on it, the
> > files are tagged beta not vc!).
> >
> > As per the recently agreed release schedule, NB 11.1 is a non-LTS
> > release, and will not have a full NetCAT process.  However, feedback
> > and testing from those on the dev@ and netcat@ lists would still be
> > appreciated, particularly around new features.  Please file issues in
> > JIRA as necessary, with the affects and fix versions set to 11.1.
> >
> > Another beta will be released, as required, on July ~3rd.  The final
> > NB 11.1 release is scheduled for July ~15th.
> >
> > The next full NetCAT is scheduled for NB 12.0 in early 2020, which
> > will be the next LTS release.
> >
> > Release schedule :
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Release-2BSchedule&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0&m=nteZCygUuT4srtcV4loU0XYSyVCAyWgSeDUCG0BZ-jo&s=aXRFU2tCTj8rzBDlt-VpLG9F7luPpKZjsT95QV-JFSA&e=
> > NB 11.1 major changes :
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__cwiki.apache.org_confluence_display_NETBEANS_Apache-2BNetBeans-2B11.1&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0&m=nteZCygUuT4srtcV4loU0XYSyVCAyWgSeDUCG0BZ-jo&s=gyXLU-0x9dO7jpwp--m1Wodrze42BPUJI4WrJQzQcnM&e=
> >
> >
> > See the artefacts here:
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__builds.apache.org_job_netbeans-2Drelease_417_artifact_dist_&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=I_-Y15BecdUmuYLJbvbi0hFUs7JgHZnV_jPFSP8DQF0&m=nteZCygUuT4srtcV4loU0XYSyVCAyWgSeDUCG0BZ-jo&s=_avaiZ5vurj_oz-ZWAnTwJJHoOzdSsynaOYhg8y8CYM&e=
> >
> > The binary you most likely need is:
> >
> https://urldefense.proofpoint.com/v2/u

Re: Apache NetBeans 11.1-beta2 Is Available for Testing!

[Alessandro]

Dear all,
  I continued testing NB 11.1 beta2 trying some Java EE related
functionalities with both Maven and Gradle projects.

I reported two more minor issues:

   1. NETBEANS-2791
<https://issues.apache.org/jira/browse/NETBEANS-2791>Glassfish
   and Payara servers download leaves spurious directory on filesystem
  1. NETBEANS-2792
<https://issues.apache.org/jira/browse/NETBEANS-2792>Gradle
 EE Run output tab remains in running state (bold title) after
deployment

but otherwise I had a pleasant experience.

Loved the function to automatically download GlassFish and Payara from the
Servers dialog (Tool > Servers), it should be extended to Apache Tomcat as
well (and maybe Apache TomEE as well).

I tried Java EE 7 at the moment will try Java EE 8 with beta3 to wait for
the fixes to already reported issues.
I can say for now that with NB 11.1 the maven web application projects are
very different in content when using Java EE 8  over Java EE 7, is it
because of the different maven archetypes used under the hood? I found the
Java EE 8 maven web application project a bit too "opinionated".

Keep up the good work!

Regards,
Alex

Il giorno mar 2 lug 2019 alle ore 11:24 Alessandro 
ha scritto:

> Dear all,
>   I am test driving the new beta with a focus on Java development with
> Maven and Gradle: so far so good.
> No major problems encountered apart from NETBEANS-2783
> <https://issues.apache.org/jira/browse/NETBEANS-2783>, which affects also
> version 11.0 and probably earlier version back to 8.2.
>
> Will continue the tests and report back any problems.
>
> Keep up the good work!!!
>
> Regards,
> Alex
>

Re: Apache NetBeans 11.1-beta2 Is Available for Testing!

[Alessandro]

Dear all,
  I am test driving the new beta with a focus on Java development with
Maven and Gradle: so far so good.
No major problems encountered apart from NETBEANS-2783
, which affects also
version 11.0 and probably earlier version back to 8.2.

Will continue the tests and report back any problems.

Keep up the good work!!!

Regards,
Alex

Il giorno dom 30 giu 2019 alle ore 17:29 huang kai  ha
scritto:

> That's nice~!
>
> 在2019年06月30，下午 2:35，Laszlo Kishalmi  写道：
> I've updated the Snap release job to work with the new non-incubating
> project source artifact. As I side effect the 11.1 beta 2 is available as a
> snap from the snap store in the latest/edge channel. So anyone using snap
> would like to test the beta just switch the channel with: snap refresh
> --channel edge netbeans The previous version (11.0) can be easily  restored
> in need with: snap revert netbeans On 6/26/19 11:26 AM, Neil C Smith wrote:
> Dear Community, I'd like to announce that the second beta build for Apache
> NetBeans 11.1 from the release111 branch is available for download. Key
> changes since beta1 include integration of Java EE 8 and Payara support via
> agreed feature freeze bypass - testing in these areas would be very
> appreciated. Full details of changes between beta1 and beta2 are at
> https://github.com/apache/netbeans/pull/1330 As this build is for testing
> purposes only, we are not going to do the release dance and voting around
> it (and as we're not voting on it, the files are tagged beta not vc!). As
> per the recently agreed release schedule, NB 11.1 is a non-LTS release, and
> will not have a full NetCAT process. However, feedback and testing from
> those on the dev@ and netcat@ lists would still be appreciated,
> particularly around new features. Please file issues in JIRA as necessary,
> with the affects and fix versions set to 11.1. Another beta will be
> released, as required, on July ~3rd. The final NB 11.1 release is scheduled
> for July ~15th. The next full NetCAT is scheduled for NB 12.0 in early
> 2020, which will be the next LTS release. Release schedule :
> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule NB
> 11.1 major changes :
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1
> See the artefacts here:
> https://builds.apache.org/job/netbeans-release/417/artifact/dist/ The
> binary you most likely need is:
> https://builds.apache.org/job/netbeans-release/417/artifact/dist/netbeans-11.1-beta2-bin.zip
> Installers, as mentioned in the major changes link, are in progress. The
> SHA512 sums if you would like to check them are provided there as well as
> here:
> 19470a7c60bc58d1aeedf66ec1e4fc96aef2fd20c75218a943acd4f6c604bf2bfcf669b932651b1900ffab787589fae92838e068158fe963692ee00c109dd2e8
> ./netbeans-11.1-beta2-bin.zip
> b3e7471237485d2b28a5673988a093d32f881d98004f674035e7adb0d4b5461f6a3d7277a1f82a04be445d6ecacc6dceed0ff489ce3418ae50b9f197fa69cb20
> ./netbeans-11.1-beta2-source.zip
> 6d8819171d2795f877ac66f8689fe55c64d095293ae8c106f8f28207282e263b4d4d69375c6024640ae3173dad898e7117f3cb1a38c2400ceae04e2fdc5f99a4
> ./netbeans-platform-11.1-beta2-bin.zip
> f69ebbfbf0129e3cb650046f3887d23a299aa7625367414be400727c3b8386bc5322dffc043e930cc4c9b39c1febb60c2d11b48f1b622bc291cecec0acfdac92
> ./netbeans-platform-11.1-beta2-source.zip Thanks and best wishes, Neil
> Voluntary Release Manager for Apache NetBeans 11.1
> - To
> unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org 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 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: Call for Testers: Performance improvement on Windows?!

[Alessandro]

Hi Laszlo,
  just tried removing masterfs-windows on a NetBeans 11.1-beta2 install, I
made no exact measurements but it feels indeed snappier.
Will leave NIO2 file watcher enabled during my NetBeans 11.1-beta2 tryout
and report back any problems.

Greets,
Alex

Il giorno mar 2 lug 2019 alle ore 07:03 Laszlo Kishalmi <
laszlo.kisha...@gmail.com> ha scritto:

> Dear all,
>
> Especially Windows users. We would like to investigate how the Java NIO2
> based file watcher infrastructure works with Windows. According to
> https://issues.apache.org/jira/browse/NETBEANS-2291 it works quite good
> under Linux, but we need more testers on other platform too.
>
> In order to enable the NIO2 implementation all you need to do is remove
> the following file from your NetBeans installation:
>
> platform/modules/org-netbeans-modules-masterfs-.jar
>
> Please share your experience!
>
> UI: It might improve the IDE performance, but not a complete solution,
> just a baby step.
>
>
> -
> 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
>
>
>
>