On 14-07-2022 17:57, Simon IJskes - QCG wrote:
On 14-07-2022 15:34, Jean-Marc Borer wrote:
Maybe this can help as well to start searching at the right place:
https://netbeans.apache.org/wiki/DevFaqFindLocationInSourcesFromUi.asciidoc
Thanks!
BTW:
I've researched further into class hierach
On 14-07-2022 15:34, Jean-Marc Borer wrote:
Maybe this can help as well to start searching at the right place:
https://netbeans.apache.org/wiki/DevFaqFindLocationInSourcesFromUi.asciidoc
Thanks!
BTW:
I've researched further into class hierachy behaviour, and i've found
another class hierarc
+ 1
Tested on Ubuntu 18.04.2 LTS
Petr
Od: Jan Horvath
Odesláno: středa 13. července 2022 16:03
Komu: dev@netbeans.apache.org
Předmět: [External] : Re: [VOTE] Release Apache NetBeans VSCode extension
14.0.301
+1
Tested on MacOS 12.4, SHA check is OK.
Jan
> O
On 7/14/22 6:02 AM, Jiří Kovalský wrote:
Dne 14. 07. 22 v 13:15 Michael Bien napsal(a):
On 14.07.22 12:44, Neil C Smith wrote:
So we can .. use
the NB15 baseline as initial set for NB16+ as suggested by Matthias.
just an idea,
Yes. Using the previous release as the baseline set is far from
On 14.07.22 15:51, Jean-Marc Borer wrote:
Is there a possibility to preview the changed asciidoctor page without
saving (committing) it?
you commit to your clone of the website. Then you can create a PR to the
actual website. You can preview the markup on github which looks
similar. Don't k
On 14.07.22 15:42, Jean-Marc Borer wrote:
Hi there,
I started reviewing some asciidoctor pages of the netbeans apache
site. I read the instructions on
https://netbeans.apache.org/kb/docs/contributing.html to understand
how to proceed.
However, it doesn't tell what to do when the review is f
Once I get all the required instructions, I will update the contributing
page accordingly.
I the meantime I guess that:
1) one shall add :reviewed: -mm-dd metadata tag
2) remove the footer text: "*NOTE:* This document was automatically
converted... "
3) remove the needsreview tag
Correct? Am
Hi there,
I started reviewing some asciidoctor pages of the netbeans apache site. I
read the instructions on
https://netbeans.apache.org/kb/docs/contributing.html to understand how to
proceed.
However, it doesn't tell what to do when the review is finished: shall we
remove the footer that say it
Maybe this can help as well to start searching at the right place:
https://netbeans.apache.org/wiki/DevFaqFindLocationInSourcesFromUi.asciidoc
On Tue, Jul 12, 2022 at 7:58 PM Simon IJskes - QCG wrote:
> filed a bug report
>
> https://github.com/apache/netbeans/issues/4366
>
>
>
After searching I found it again:
https://netbeans.apache.org/wiki/DevFaqFindLocationInSourcesFromUi.asciidoc
On Thu, Jul 14, 2022 at 12:05 PM Jean-Marc Borer wrote:
> Hello,
>
> Does anyone remember the command line switch that allows to debug the
> labels in the IDE and therefore source bundl
On Thu, 14 Jul 2022 at 14:02, Jiří Kovalský wrote:
> Anyway, I very much like the idea of notification button which would
> give owners of plugins supporting already released version 14 a chance
> to quickly double check that their plugins work in version 15 and then
> request official verificatio
Dne 14. 07. 22 v 13:15 Michael Bien napsal(a):
On 14.07.22 12:44, Neil C Smith wrote:
So we can .. use
the NB15 baseline as initial set for NB16+ as suggested by Matthias.
just an idea,
Yes. Using the previous release as the baseline set is far from a new
suggestion though,
well this was onl
Hello,
Does anyone remember the command line switch that allows to debug the
labels in the IDE and therefore source bundles they come from? I remember
it exists, but I am not able to find this information again.
Cheers,
JM
On 14.07.22 12:44, Neil C Smith wrote:
So we can .. use
the NB15 baseline as initial set for NB16+ as suggested by Matthias.
just an idea,
Yes. Using the previous release as the baseline set is far from a new
suggestion though,
well this was only a part what i was suggesting, it was supposed
On Thu, 14 Jul 2022 at 11:05, Michael Bien wrote:
> as already mentioned in other threads about the same topic, I have the
> suspicion that many plugin maintainers don't know that they have to
> press verify after every NB release. (I do know but i forgot at least
> twice so far but thats me)
Tha
Hi,
as already mentioned in other threads about the same topic, I have the
suspicion that many plugin maintainers don't know that they have to
press verify after every NB release. (I do know but i forgot at least
twice so far but thats me)
I believe a temporary solution would be to send a no
On Wed, 13 Jul 2022 at 18:17, Matthias Bläsing
wrote:
> from my perspective all "Verification" can do is to check a plugin
> looks normal and does not immediately destroys your data. Everything
> else will not scale (and yes not doing verification at all is IMHO an
> option).
>
> What we could do
17 matches
Mail list logo