Re: Syntax highlighting question

2019-10-16 Thread Tim Boudreau
Hi, Peter,

I would strongly suggest we collaborate on that here:
https://github.com/timboudreau/ANTLR4-Plugins-for-NetBeans - since that
way, not only would it be implementable for Antlr, but for *any* language
using an Antlr grammar (it is two layers of modules - one for writing
language modules with most features generated for you from *any *Antlr
grammar, and then modules for Antlr grammar language built on top of that -
here are some docs on general-language support -
https://github.com/timboudreau/ANTLR4-Plugins-for-NetBeans/blob/master/api.md
- and I hope to have a continuous build w/ javadocs up soon).

NetBeans lexer and parser APIs have straightforward support for this - see
LanguagePath and the method on Parser.Result that takes an integer and
gives you a Parser.Result for an embedded language.

Done right, supporting an embedded language would be as simple as

@EmbeddedLanguage("text/x-java")
public static final RegionsKey THE_KEY = ...

(the generic language support API revolves around defining typed keys, and
then extracting what you're actually going to use from the parse tree as
character ranges with any data you need tied to those ranges, and then you
can retrieve the actual results from a parser result when a file is parsed).

That's been on my todo list too - the original antlr plugin author had
included a crude Antlr grammar for Java to do that, which isn't a terribly
sensible way to do it when you have a really good Java parser available for
use.

-Tim


On Tue, Oct 15, 2019 at 6:16 AM Peter Cheung  wrote:

> Dear All
>I have developed a module (https://gitlab.com/mcheung63/netbeans-antlr)
> for antlr, it provides antlr grammar syntax highlight, but it is not
> perfect. I want to enhance it but problem is : antlr supports "embed
> action", which is in Java, so two languages in same file.
>
>To provide the best syntax highlight, i need to send those embed
> actions to "java lexer", this point has no problem to me. But Is there
> anyway merge those tokens (java-lexer) back to the one (antlr-lexer) which
> used by netbeans to provide syntax highlight?
>
> Is there any way to provide syntax highlight but not using lexer? Let
> say i want to hight the second line from character 2-4 in red. Whatever the
> text is, i just want to highlight those positions, is it possible?
>
> Thanks
> From Peter
>
>
>

-- 
http://timboudreau.com


Re: Apache NetBeans 11.2-beta3 is Available for Testing!

2019-10-16 Thread Patrick Musembi
>
> I will test this version starting tomorrow Thur

Congrats all for the good work guys.


Re: Apache NetBeans 11.2-beta3 is Available for Testing!

2019-10-16 Thread Laszlo Kishalmi
I know it is not the installer, though 11.2-beta3 is available on the 
edge channel on https://snapcraft.io/netbeans


On 10/16/19 6:55 AM, Glenn Holmer wrote:

On 10/16/19 5:41 AM, Neil C Smith wrote:

I'd like to announce that the third beta build for Apache NetBeans
11.2 from the release112 branch is available for download.

Please remind us where to find the installers (e.g. Linux) for this beta
if we'd like to test them?


-
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.2-beta3 is Available for Testing!

2019-10-16 Thread Neil C Smith
On Wed, 16 Oct 2019 at 15:34, Geertjan Wielenga  wrote:
>
> No installers until the final release.

Would be nice if we could get into a state where we could better test
installers before release.  However, just tried to trigger the
netbeans-installer build and it failed.  I assume this is recent
Jenkins environment changes, but I'll leave it for Reema to look at.

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.2-beta3 is Available for Testing!

2019-10-16 Thread Geertjan Wielenga
No installers until the final release.

Gj

On Wed, Oct 16, 2019 at 3:55 PM Glenn Holmer 
wrote:

> On 10/16/19 5:41 AM, Neil C Smith wrote:
> > I'd like to announce that the third beta build for Apache NetBeans
> > 11.2 from the release112 branch is available for download.
>
> Please remind us where to find the installers (e.g. Linux) for this beta
> if we'd like to test them?
>
> --
> Glenn Holmer (Linux registered user #16682)
> "After the vintage season came the aftermath -- and Cenbe."
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>


Re: Apache NetBeans 11.2-beta3 is Available for Testing!

2019-10-16 Thread Glenn Holmer
On 10/16/19 5:41 AM, Neil C Smith wrote:
> I'd like to announce that the third beta build for Apache NetBeans
> 11.2 from the release112 branch is available for download.

Please remind us where to find the installers (e.g. Linux) for this beta
if we'd like to test them?

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Re: [DISCUSS] Handling convenience binary vote(?) for 11.2

2019-10-16 Thread Neil C Smith
On Wed, 16 Oct 2019 at 12:58, Eric Barboni  wrote:
> What if,
>  In Release 11.2, Linux  Installer is not ok. And fix implies NetBeans 
> sources changes.
>
>  We would vote again on source to make release 11.2fix1 with installer and 
> still have a 11.2 with missing one missing convenience?

Not a "what if" I particularly like! :-)  But yes, if picked up in
time we decide whether to pull the vote or make a later fix for vote
before or after public release.  That's no different or worse than
what we've done before, potentially somewhat better given they weren't
voted on before!

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: Using JIRA Id of external issue tracker

2019-10-16 Thread Gaurav Gupta
Hi Eric,

Thanks for your suggestion. In the future, I will create the Jira ticket
and prefix the PR title with *NETBEANS-XXX*.

Thanks and kind regards,
Gaurav Gupta






On Wed, Oct 16, 2019 at 5:34 PM Eric Barboni  wrote:

> Hi Gaurav,
>
>  AFAIK It's not mandatory to have issue in the title. It's better for
> connecting to jira.
>  But on the Apache side we have only NETBEANS-XXX jira so NP-XX is
> confusing seen from Apache NetBeans.
>
>  Regards
> Eric
> -Message d'origine-
> De : Gaurav Gupta 
> Envoyé : vendredi 11 octobre 2019 09:51
> À : dev@netbeans.apache.org
> Objet : Using JIRA Id of external issue tracker
>
> Hi all,
>
> For Payara NetBeans module's bugs & features, Payara Jira tracker is used
> which helps us in monthly sprint planning. See the PR title for example (
> https://github.com/apache/netbeans/pull/1562) starts with NP-38.
>
> Is it mandatory to use NetBeans JIRA Id in Github PR title?
>
> Thanks and kind regards,
> Gaurav Gupta
>
>
> -
> 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: Using JIRA Id of external issue tracker

2019-10-16 Thread Eric Barboni
Hi Gaurav,
 
 AFAIK It's not mandatory to have issue in the title. It's better for 
connecting to jira.
 But on the Apache side we have only NETBEANS-XXX jira so NP-XX is confusing 
seen from Apache NetBeans.

 Regards
Eric
-Message d'origine-
De : Gaurav Gupta  
Envoyé : vendredi 11 octobre 2019 09:51
À : dev@netbeans.apache.org
Objet : Using JIRA Id of external issue tracker

Hi all,

For Payara NetBeans module's bugs & features, Payara Jira tracker is used which 
helps us in monthly sprint planning. See the PR title for example (
https://github.com/apache/netbeans/pull/1562) starts with NP-38.

Is it mandatory to use NetBeans JIRA Id in Github PR title?

Thanks and kind regards,
Gaurav Gupta


-
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.2-beta3 is Available for Testing!

2019-10-16 Thread Josh Juneau
Nice work Neil and everyone else involved.  I will begin testing today.  +1
to 72 hrs for final testing of beta3 and final voting on Saturday.

On Wed, Oct 16, 2019 at 6:18 AM Geertjan Wielenga 
wrote:

> Agree with that!
>
> Let’s really kick the tires a lot between now and then though, especially
> around the nb-javac installation experience and identify all possible
> points of failure and troubleshooting tips.
>
> Gj
>
> On Wed, 16 Oct 2019 at 13:14, Neil C Smith  wrote:
>
> > On Wed, 16 Oct 2019 at 11:41, Neil C Smith 
> wrote:
> > > This will hopefully be our final beta for NB 11.2 and all being
> > > well the release vote will be based on the same code.
> >
> > dev@ only addition.  Anyone feel that we need to give more than 72hrs
> > for final testing of beta3?  I'm inclined to aim at making the voting
> > candidate on Saturday.
> >
> > 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
> >
> >
> >
> >
>
-- 
Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau



RE: [DISCUSS] Handling convenience binary vote(?) for 11.2

2019-10-16 Thread Eric Barboni
What if,  
 In Release 11.2, Linux  Installer is not ok. And fix implies NetBeans sources 
changes.

 We would vote again on source to make release 11.2fix1 with installer and 
still have a 11.2 with missing one missing convenience?

Regards
Eric
-Message d'origine-
De : Geertjan Wielenga  
Envoyé : mercredi 16 octobre 2019 13:29
À : dev@netbeans.apache.org
Objet : Re: [DISCUSS] Handling convenience binary vote(?) for 11.2

Makes sense, thanks.

Gj

On Wed, 16 Oct 2019 at 13:26, Neil C Smith  wrote:

> On Wed, 16 Oct 2019 at 12:13, Geertjan Wielenga 
> wrote:
> >
> > But can’t they all be handled in the same vote thread? (Sorry this 
> > has probably been explained multiple times, but maybe just in this 
> > part of
> the
> > thread too it would help.)
>
> Ideally, no.  I think we need to require that people who are voting 
> have tested everything that is there to be voted on.  Otherwise we 
> have no way of knowing if anyone has actually checked eg. the Linux 
> installer.
>
> I don't think it's feasible to expect that everyone who votes can test 
> every binary.  We've not voted on binaries before, and I was not the 
> one pushing for it.  But if we're going to do it, I want to at least 
> make sure everything does get checked against the ASF requirements by 
> other PMC members.
>
> It also allows to run some votes later if required.  We don't have to 
> hold up voting on the initial release build for things that require 
> additional steps.
>
> Best wishes,
>
> Neil
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: [DISCUSS] Handling convenience binary vote(?) for 11.2

2019-10-16 Thread Geertjan Wielenga
Makes sense, thanks.

Gj

On Wed, 16 Oct 2019 at 13:26, Neil C Smith  wrote:

> On Wed, 16 Oct 2019 at 12:13, Geertjan Wielenga 
> wrote:
> >
> > But can’t they all be handled in the same vote thread? (Sorry this has
> > probably been explained multiple times, but maybe just in this part of
> the
> > thread too it would help.)
>
> Ideally, no.  I think we need to require that people who are voting
> have tested everything that is there to be voted on.  Otherwise we
> have no way of knowing if anyone has actually checked eg. the Linux
> installer.
>
> I don't think it's feasible to expect that everyone who votes can test
> every binary.  We've not voted on binaries before, and I was not the
> one pushing for it.  But if we're going to do it, I want to at least
> make sure everything does get checked against the ASF requirements by
> other PMC members.
>
> It also allows to run some votes later if required.  We don't have to
> hold up voting on the initial release build for things that require
> additional steps.
>
> 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: [DISCUSS] Handling convenience binary vote(?) for 11.2

2019-10-16 Thread Neil C Smith
On Wed, 16 Oct 2019 at 12:13, Geertjan Wielenga  wrote:
>
> But can’t they all be handled in the same vote thread? (Sorry this has
> probably been explained multiple times, but maybe just in this part of the
> thread too it would help.)

Ideally, no.  I think we need to require that people who are voting
have tested everything that is there to be voted on.  Otherwise we
have no way of knowing if anyone has actually checked eg. the Linux
installer.

I don't think it's feasible to expect that everyone who votes can test
every binary.  We've not voted on binaries before, and I was not the
one pushing for it.  But if we're going to do it, I want to at least
make sure everything does get checked against the ASF requirements by
other PMC members.

It also allows to run some votes later if required.  We don't have to
hold up voting on the initial release build for things that require
additional steps.

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.2-beta3 is Available for Testing!

2019-10-16 Thread Geertjan Wielenga
Agree with that!

Let’s really kick the tires a lot between now and then though, especially
around the nb-javac installation experience and identify all possible
points of failure and troubleshooting tips.

Gj

On Wed, 16 Oct 2019 at 13:14, Neil C Smith  wrote:

> On Wed, 16 Oct 2019 at 11:41, Neil C Smith  wrote:
> > This will hopefully be our final beta for NB 11.2 and all being
> > well the release vote will be based on the same code.
>
> dev@ only addition.  Anyone feel that we need to give more than 72hrs
> for final testing of beta3?  I'm inclined to aim at making the voting
> candidate on Saturday.
>
> 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: Apache NetBeans 11.2-beta3 is Available for Testing!

2019-10-16 Thread Neil C Smith
On Wed, 16 Oct 2019 at 11:41, Neil C Smith  wrote:
> This will hopefully be our final beta for NB 11.2 and all being
> well the release vote will be based on the same code.

dev@ only addition.  Anyone feel that we need to give more than 72hrs
for final testing of beta3?  I'm inclined to aim at making the voting
candidate on Saturday.

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: [DISCUSS] Handling convenience binary vote(?) for 11.2

2019-10-16 Thread Geertjan Wielenga
But can’t they all be handled in the same vote thread? (Sorry this has
probably been explained multiple times, but maybe just in this part of the
thread too it would help.)

Gj

On Wed, 16 Oct 2019 at 13:09, Neil C Smith  wrote:

> On Fri, 4 Oct 2019 at 16:49, Neil C Smith  wrote:
> > I'm still not totally sold on doing that instead of multiple vote
> > threads, but we do need to be clearer on all the stuff we release, and
> > what we expect everyone to actually check before voting.  With more
> > thought, I'm veering towards Laszlo's suggestion of adding binary zip
> > and nbms into release vote, and separate votes on the other artefacts.
> > This also reflects different OS concerns, additional build processes,
> > and different people signing.
>
> OK, as the day gets closer for the 11.2 vote (although should have
> been a few days ago! :-) ) ..
>
> My plan, unless anyone has major objections, is to run this roughly as
> Laszlo suggested and we see how that goes.
>
> I will add the zip and nbm binaries into the release vote thread,
> along with specifics of what else needs to be done with them in order
> to vote.  That means anyone who votes must now do checks on sources
> and those binaries.
>
> Then we will have separate votes on -
>
> * Maven artefacts (Eric?)
> * Windows installer (Reema?)
> * macOS installer (Reema?)
> * Linux installer (Reema?)
> * anything else ???
>
> That keeps OS concerns and different signer concerns separate, as well
> as acknowledging that zip and nbms are built in the same build process
> as the source bundle.
>
> Obviously the other convenience binary threads are also dependent on
> the main release vote passing.  The additional threads can run
> concurrently or slightly later as required.
>
> 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: [DISCUSS] Handling convenience binary vote(?) for 11.2

2019-10-16 Thread Neil C Smith
On Fri, 4 Oct 2019 at 16:49, Neil C Smith  wrote:
> I'm still not totally sold on doing that instead of multiple vote
> threads, but we do need to be clearer on all the stuff we release, and
> what we expect everyone to actually check before voting.  With more
> thought, I'm veering towards Laszlo's suggestion of adding binary zip
> and nbms into release vote, and separate votes on the other artefacts.
> This also reflects different OS concerns, additional build processes,
> and different people signing.

OK, as the day gets closer for the 11.2 vote (although should have
been a few days ago! :-) ) ..

My plan, unless anyone has major objections, is to run this roughly as
Laszlo suggested and we see how that goes.

I will add the zip and nbm binaries into the release vote thread,
along with specifics of what else needs to be done with them in order
to vote.  That means anyone who votes must now do checks on sources
and those binaries.

Then we will have separate votes on -

* Maven artefacts (Eric?)
* Windows installer (Reema?)
* macOS installer (Reema?)
* Linux installer (Reema?)
* anything else ???

That keeps OS concerns and different signer concerns separate, as well
as acknowledging that zip and nbms are built in the same build process
as the source bundle.

Obviously the other convenience binary threads are also dependent on
the main release vote passing.  The additional threads can run
concurrently or slightly later as required.

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: Switch plugin portal in NetBeans 11.2 to new one?

2019-10-16 Thread Christian Pervoelz
Thanks Jiri.
(Most) Questions answered. :)

Now it's (at least for me) only the question whether the 'old' UCs should
be inactive by default or not. In the first case, I think, a note on the
'Available Plugins' tab would be great (as mentioned by Neil).

Ps: About forcing: I was just confused/irritated about that phrase, as I
didn't suppose 'forcing' a part of the Apache way.

Am Mi., 16. Okt. 2019 um 08:50 Uhr schrieb Jiří Kovalský <
jiri.koval...@oracle.com>:

> Dne 15. 10. 19 v 18:14 Christian Pervoelz napsal(a):
>
> [snip]
>
> > So, there is a couple of question now:
> > What should happen with those plugins not moved over at all, but which
> are
> > maybe still useful?
>
> This generic question results in a generic answer so we should rather
> talk about such useful plugins individually but we have e-mail addresses
> for all plugin authors so we can at least try approaching them via
> e-mail. If that does not help, some plugins contain links to their
> websites which often means source code repositories hence if someone is
> a true fan s/he can clone the repository and take over maintenance or
> even development of the popular plugins.
>
> > Should authors of plugins (dedicated to old NB versions) also be forced
> to
> > move them and by that update them?
>
> We could ask them at best. Forcing someone is not an Apache style of
> open discussion and meritocracy.
>
> > How can authors be forced? Do we know, how we can address them?
>
> Plugin owner usern...@netbeans.org
>
> -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
>
>
>
>


Fwd: Deprecated versions Maven/Ant/Java to be removed soon.

2019-10-16 Thread Antonio

Hi all,

FYI: ASF Infra will be deprecating older versions of Ant/Maven/Java in 
the Jenkins nodes.


This caused some of our build scripts to fail in the past. Maybe we want 
to make sure we're using the latest versions of those tools in our 
Jenkins scripts.


Cheers,
Antonio


 Mensaje reenviado 
Asunto: Deprecated versions Maven/Ant/Java to be removed soon.
Fecha: Mon, 7 Oct 2019 11:39:46 +0100
De: Gavin McDonald 
Responder a: bui...@apache.org, gmcdon...@apache.org
Para: builds ,  



Hi All,

As part of migrating all our Jenkins nodes to Ubuntu 18.04 and as per Infra
Policy in maintaining the build nodes, older versions of Maven, Ant and
Java are to be removed over the next few days. All of the versions being
removed have newer versions available. (Example 3.0.4 has 3.0.5 available
as replacement)

Note that, as the H nodes have been rebuilt as 18.04, most of these
deprecated versions have not been re-installed.

Buildbot nodes will be having the same removals done.

Please find below a summary of each; and links to their cwiki documentation
page. Any questions please let me know.

Thanks

Gav...

[Maven]

3.0.4 (3.0.5 available)
3.2.1 (3.2.5 available)
3.3.3 (3.3.9 available)
3.5.0, 3.5.2 (3.5.4 available)
3.6.0, 3.6.1 (3.6.2 available)

https://cwiki.apache.org/confluence/display/INFRA/Maven+Installation+Matrix

[Ant]

1.9.4, 1.9.9, 1.9.11, 1.9.13 (1.9.14 available)
1.10.1, 1.10.3, 1.10.5 (1.10.6, 1.10.7 available)

https://cwiki.apache.org/confluence/display/INFRA/Ant+Installation+Matrix

[Java]

JDK 1.8.0 - 121,131,144,152,172 (191 available)
JDK 9 - ea156, ea179, ea181 (9.0.4 available)
JDK10 - ea36, ea46
JDK11 - ea8, ea19, ea22 (11.0.4 available)
openjdk 12 - ea18, ea28 (ea33 available)
openjdk 13 - ea4, ea9, ea23, ea25 (ea33 available)
openjdk 14 - ea1, ea10 (ea17 available)

https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix


-
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: Switch plugin portal in NetBeans 11.2 to new one?

2019-10-16 Thread Jiří Kovalský

Dne 15. 10. 19 v 18:14 Christian Pervoelz napsal(a):

[snip]


So, there is a couple of question now:
What should happen with those plugins not moved over at all, but which are
maybe still useful?


This generic question results in a generic answer so we should rather 
talk about such useful plugins individually but we have e-mail addresses 
for all plugin authors so we can at least try approaching them via 
e-mail. If that does not help, some plugins contain links to their 
websites which often means source code repositories hence if someone is 
a true fan s/he can clone the repository and take over maintenance or 
even development of the popular plugins.



Should authors of plugins (dedicated to old NB versions) also be forced to
move them and by that update them?


We could ask them at best. Forcing someone is not an Apache style of 
open discussion and meritocracy.



How can authors be forced? Do we know, how we can address them?


Plugin owner usern...@netbeans.org

-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