Re: Fwd: Question about issue tracker

2018-01-02 Thread Dawn Raison
One more I'd add - 
http://statistics.netbeans.org/analytics/detail.do?id=225493 (The {{ 
exception)


Quite possibly the same root cause as some of the others below (editor 
state gets confused).


This happens maybe 4 times a week, but when it does you have to close 
out and restart or lines start to disappear from your file without the 
possibility of undo.


Dawn

On 02/01/2018 21:07, Jan Lahoda wrote:
I've accidentally responded only to Gili outside the list, apologizes. 
Forwarding the conversation.


Jan

-- Forwarded message --
From: *cowwoc* <cow...@bbs.darktech.org <mailto:cow...@bbs.darktech.org>>
Date: Sun, Dec 31, 2017 at 10:38 PM
Subject: Re: Question about issue tracker
To: Jan Lahoda <lah...@gmail.com <mailto:lah...@gmail.com>>


Yes. Go ahead.

Gili


On 2017-12-31 10:04 AM, Jan Lahoda wrote:

Hi Gili,

Thanks for the pointer. I'll look at what I can. I accidentally sent 
the e-mail just to you instead of the mailing list - is it OK to 
forward your e-mail back to the mailing lists?


Thanks,
    Jan


On Sun, Dec 31, 2017 at 2:02 PM, cowwoc <cow...@bbs.darktech.org 
<mailto:cow...@bbs.darktech.org>> wrote:


Hi Jan,

Here are some concrete examples:

https://netbeans.org/bugzilla/show_bug.cgi?id=270632
<https://netbeans.org/bugzilla/show_bug.cgi?id=270632> <-- makes
IDE slow to the point of being unusable
https://netbeans.org/bugzilla/show_bug.cgi?id=252602
<https://netbeans.org/bugzilla/show_bug.cgi?id=252602> <-- not as
bad, but still extremely annoying if you are using Find Usages
frequently
https://netbeans.org/bugzilla/show_bug.cgi?id=270272
<https://netbeans.org/bugzilla/show_bug.cgi?id=270272> <--
impossible to debug lambdas
https://netbeans.org/bugzilla/show_bug.cgi?id=250595
<https://netbeans.org/bugzilla/show_bug.cgi?id=250595> <-- error
that depends on your project state, but once you get into this
bad state it is extremely annoying (parsing errors get thrown
very frequently)
https://netbeans.org/bugzilla/show_bug.cgi?id=255791
<https://netbeans.org/bugzilla/show_bug.cgi?id=255791> <--
parsing issue similar to previous one
https://netbeans.org/bugzilla/show_bug.cgi?id=271633
<https://netbeans.org/bugzilla/show_bug.cgi?id=271633> <-- cannot
code-complete methods in enums. I've recently seen a similar
problem for non-enum anonymous classes. End result: I keep on
having to type method prototypes by hand.

Some of these issues have been around for years. There are
stack-traces, profiler dumps, and sometimes even full-out repro
steps but there has been no follow-up from the committers' end.
Communication is very important to prevent bug reports from
becoming stale, so if you are unable to reproduce the issue the
sooner you tell me the better so we can collect more logs.

Anyway, fixing some/most of these bugs would go a long way
towards improving my working experience with Netbeans. For the
past couple of years I have felt that we should dedicate an
entire release towards bug fixing (no new features) to make
Netbeans more reliable and performant. It's still a good IDE but
compared to Intellij there is no comparison (this was not always
the case). I want to keep on using Netbeans, so I hope we can
streamline this process.

PS: It is absolutely vital that the Exception Reporter
infrastructure be moved over to the new bug tracker. I can't
imagine having to report all these issues by hand... The vast
majority of bugs I run into on a daily basis are
NullPointerExceptions, parsing errors, and such. In these cases,
the Exception Reporter does a better job than I would collecting
all the relevant files (and keystoke history) to help you
reproduce the problem.

PS2: If you want to save users even more time, try detecting if a
bug is known before asking us to enter a description. Very often
I see a report is fully fleshed out and all I need to log my vote
("I'm impacted by this bug"). Asking me to enter a description
each time is annoying and discourages me from reporting bugs in
the first place.

Thanks,
Gili


On 2017-12-31 3:04 AM, Jan Lahoda wrote:

Hi Gili,

On Sun, Dec 31, 2017 at 7:28 AM, cowwoc <cow...@bbs.darktech.org
<mailto:cow...@bbs.darktech.org>> wrote:

Hi,

Are there any plans to open up (migrate) the issue tracker
for the broader apache community to tackle existing/old
Netbeans bugs?

I ask because I feel like the bandwidth for fixing Java
Editor bugs is like sucking a milkshake through a straw:
major bugs are being reported at an expoentially-growing
rate and they are being fixed at a rate of 1-2 a week. The
nightly builds are frankly bare

Re: Question about issue tracker

2018-01-01 Thread cowwoc

Done: https://github.com/apache/incubator-netbeans/pull/351

Gili

On 2017-12-31 4:49 PM, John McDonnell wrote:
You could, but for something this small, maybe we could convince you 
to join the effort :)  then there's no need to file a JIRA ticket, you 
could always fork the repo, make the change in your local repo and 
then submit a PR, explicitly pointing out why you think the change is 
needed.


All of this could be done quicker than a ticket, as it would probably 
be viewed as a low priority item ;)


Details are found here: 
https://cwiki.apache.org/confluence/display/NETBEANS/Development+Environment 
and 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408 
(still work in progress)


Regards

John

On 31 December 2017 at 21:44, cowwoc > wrote:


Hi John,

Thank you! Is it okay if I file a RFE asking for the download link
to get added to README.md?

Gili


On 2017-12-31 8:52 AM, John McDonnell wrote:

Hi Cowwoc,

At the moment NetBeans in migrating over to Apache, and in the
latter half of 2017, the first initial code drop took place
containing the NetBeans platform and the basic Java modules,
etc...  As a result the old codebase stored in Oracle, i.e.
https://netbeans.org/community/sources/
 is no longer applicable
for use since the more up to date changes are happening in the
code base found: https://github.com/apache/incubator-netbeans


This means the daily builds should be taken from here:

https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/




In relation to the exception reporter I believe there was some
discussion about this, but I cannot seem to find it on the
mailing lists, so maybe I'm imagining this.  But your right,
something will need to be done about this.


Please check out the new daily builds and please file any defects
against the JIRA link previously provided. - If there are any
high profile defects that might block you please report them as
soon as possible thanks.

John

On 31 December 2017 at 12:42, cowwoc > wrote:

Hi Geertjan,

I am getting the nightly builds from
http://bits.netbeans.org/download/trunk/nightly/latest/


Gili


On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:

Which nightly builds are you referring to specifically?

Can you provide a URL just to make sure we’re talking about
the same thing?

Gj

On Sunday, December 31, 2017, cowwoc
>
wrote:

Hi,

Are there any plans to open up (migrate) the issue
tracker for the broader apache community to tackle
existing/old Netbeans bugs?

I ask because I feel like the bandwidth for fixing Java
Editor bugs is like sucking a milkshake through a straw:
major bugs are being reported at an expoentially-growing
rate and they are being fixed at a rate of 1-2 a week.
The nightly builds are frankly barely usable anymore. I
am specifically concerned about Maven + Java projects
where I routinely get NullPointerExceptions and "slow
action" errors (actions taking 13-20 seconds to complete
on a seemingly random basis).

This component needs more love. And soon. Can you please
prioritize accordingly?

Thank you,
Gili

(For context, I've been using Netbeans since 1999 so
when I say things are unstable I've got a long
track-record to judge by)



-
To unsubscribe, e-mail:
users-unsubscr...@netbeans.apache.org

For additional commands, e-mail:
users-h...@netbeans.apache.org


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












Re: Question about issue tracker

2018-01-01 Thread Emilian Bold
See https://issues.apache.org/jira/browse/NETBEANS-164

--emi
​

> Original Message 
>Subject: Re: Question about issue tracker
>Local Time: 31 December 2017 3:52 PM
>UTC Time: 31 December 2017 13:52
>From: mcdonnell.j...@gmail.com
>To: cowwoc <cow...@bbs.darktech.org>
>users@netbeans.apache.org
>
>Hi Cowwoc,
>
>At the moment NetBeans in migrating over to Apache, and in the latter half of 
>2017, the first initial code drop took place containing the NetBeans platform 
>and the basic Java modules, etc...  As a result the old codebase stored in 
>Oracle, i.e. https://netbeans.org/community/sources/ is no longer applicable 
>for use since the more up to date changes are happening in the code base 
>found: https://github.com/apache/incubator-netbeans
>
>This means the daily builds should be taken from here: 
>https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/
>
>In relation to the exception reporter I believe there was some discussion 
>about this, but I cannot seem to find it on the mailing lists, so maybe I'm 
>imagining this.  But your right, something will need to be done about this.  
>
>
>Please check out the new daily builds and please file any defects against the 
>JIRA link previously provided. - If there are any high profile defects that 
>might block you please report them as soon as possible thanks.
>
>John
>
>On 31 December 2017 at 12:42, cowwoc <cow...@bbs.darktech.org> wrote:
>>Hi Geertjan,
>>
>> I am getting the nightly builds from 
>> http://bits.netbeans.org/download/trunk/nightly/latest/
>>
>> Gili
>>
>>
>>On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:
>>>Which
>>>  nightly builds are you referring to specifically? 
>>>
>>>Can you provide a URL just to make sure we’re talking about
>>>the same thing?
>>>
>>>
>>>Gj
>>>
>>> On Sunday, December 31, 2017, cowwoc <cow...@bbs.darktech.org>
>>>  wrote:
>>>
>>>>Hi,
>>>>
>>>> Are there any plans to open up (migrate) the issue tracker
>>>>for the broader apache community to tackle existing/old
>>>>Netbeans bugs?
>>>>
>>>> I ask because I feel like the bandwidth for fixing Java
>>>>Editor bugs is like sucking a milkshake through a straw:
>>>>major bugs are being reported at an expoentially-growing
>>>>rate and they are being fixed at a rate of 1-2 a week. The
>>>>nightly builds are frankly barely usable anymore. I am
>>>>specifically concerned about Maven + Java projects where I
>>>>routinely get NullPointerExceptions and "slow action" errors
>>>>(actions taking 13-20 seconds to complete on a seemingly
>>>>random basis).
>>>>
>>>> This component needs more love. And soon. Can you please
>>>>prioritize accordingly?
>>>>
>>>> Thank you,
>>>> Gili
>>>>
>>>> (For context, I've been using Netbeans since 1999 so when I
>>>>say things are unstable I've got a long track-record to
>>>>judge by)
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>>>> For additional commands, e-mail: users-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: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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



Re: Question about issue tracker

2017-12-31 Thread John McDonnell
You could, but for something this small, maybe we could convince you to
join the effort :)  then there's no need to file a JIRA ticket, you could
always fork the repo, make the change in your local repo and then submit a
PR, explicitly pointing out why you think the change is needed.

All of this could be done quicker than a ticket, as it would probably be
viewed as a low priority item ;)

Details are found here:
https://cwiki.apache.org/confluence/display/NETBEANS/Development+Environment
and
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74681408
(still work in progress)

Regards

John

On 31 December 2017 at 21:44, cowwoc  wrote:

> Hi John,
>
> Thank you! Is it okay if I file a RFE asking for the download link to get
> added to README.md?
>
> Gili
>
>
> On 2017-12-31 8:52 AM, John McDonnell wrote:
>
> Hi Cowwoc,
>
> At the moment NetBeans in migrating over to Apache, and in the latter half
> of 2017, the first initial code drop took place containing the NetBeans
> platform and the basic Java modules, etc...  As a result the old codebase
> stored in Oracle, i.e. https://netbeans.org/community/sources/ is no
> longer applicable for use since the more up to date changes are happening
> in the code base found: https://github.com/apache/incubator-netbeans
>
> This means the daily builds should be taken from here:
> https://builds.apache.org/view/Incubator%20Projects/
> job/incubator-netbeans-release/
>
> In relation to the exception reporter I believe there was some discussion
> about this, but I cannot seem to find it on the mailing lists, so maybe
> I'm imagining this.  But your right, something will need to be done about
> this.
>
>
> Please check out the new daily builds and please file any defects against
> the JIRA link previously provided. - If there are any high profile defects
> that might block you please report them as soon as possible thanks.
>
> John
>
> On 31 December 2017 at 12:42, cowwoc  wrote:
>
>> Hi Geertjan,
>>
>> I am getting the nightly builds from http://bits.netbeans.org/downl
>> oad/trunk/nightly/latest/
>>
>> Gili
>>
>>
>> On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:
>>
>> Which nightly builds are you referring to specifically?
>>
>> Can you provide a URL just to make sure we’re talking about the same
>> thing?
>>
>> Gj
>>
>> On Sunday, December 31, 2017, cowwoc  wrote:
>>
>>> Hi,
>>>
>>> Are there any plans to open up (migrate) the issue tracker for the
>>> broader apache community to tackle existing/old Netbeans bugs?
>>>
>>> I ask because I feel like the bandwidth for fixing Java Editor bugs is
>>> like sucking a milkshake through a straw: major bugs are being reported at
>>> an expoentially-growing rate and they are being fixed at a rate of 1-2 a
>>> week. The nightly builds are frankly barely usable anymore. I am
>>> specifically concerned about Maven + Java projects where I routinely get
>>> NullPointerExceptions and "slow action" errors (actions taking 13-20
>>> seconds to complete on a seemingly random basis).
>>>
>>> This component needs more love. And soon. Can you please prioritize
>>> accordingly?
>>>
>>> Thank you,
>>> Gili
>>>
>>> (For context, I've been using Netbeans since 1999 so when I say things
>>> are unstable I've got a long track-record to judge by)
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>
>
>


Re: Question about issue tracker

2017-12-31 Thread cowwoc

Hi John,

Thank you! Is it okay if I file a RFE asking for the download link to 
get added to README.md?


Gili

On 2017-12-31 8:52 AM, John McDonnell wrote:

Hi Cowwoc,

At the moment NetBeans in migrating over to Apache, and in the latter 
half of 2017, the first initial code drop took place containing the 
NetBeans platform and the basic Java modules, etc...  As a result the 
old codebase stored in Oracle, i.e. 
https://netbeans.org/community/sources/ is no longer applicable 
for use since the more up to date changes are happening in the code 
base found: https://github.com/apache/incubator-netbeans


This means the daily builds should be taken from here: 
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/ 



In relation to the exception reporter I believe there was some 
discussion about this, but I cannot seem to find it on the mailing 
lists, so maybe I'm imagining this.  But your right, something will 
need to be done about this.



Please check out the new daily builds and please file any defects 
against the JIRA link previously provided. - If there are any high 
profile defects that might block you please report them as soon as 
possible thanks.


John

On 31 December 2017 at 12:42, cowwoc > wrote:


Hi Geertjan,

I am getting the nightly builds from
http://bits.netbeans.org/download/trunk/nightly/latest/


Gili


On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:

Which nightly builds are you referring to specifically?

Can you provide a URL just to make sure we’re talking about the
same thing?

Gj

On Sunday, December 31, 2017, cowwoc > wrote:

Hi,

Are there any plans to open up (migrate) the issue tracker
for the broader apache community to tackle existing/old
Netbeans bugs?

I ask because I feel like the bandwidth for fixing Java
Editor bugs is like sucking a milkshake through a straw:
major bugs are being reported at an expoentially-growing rate
and they are being fixed at a rate of 1-2 a week. The nightly
builds are frankly barely usable anymore. I am specifically
concerned about Maven + Java projects where I routinely get
NullPointerExceptions and "slow action" errors (actions
taking 13-20 seconds to complete on a seemingly random basis).

This component needs more love. And soon. Can you please
prioritize accordingly?

Thank you,
Gili

(For context, I've been using Netbeans since 1999 so when I
say things are unstable I've got a long track-record to judge by)


-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org

For additional commands, e-mail:
users-h...@netbeans.apache.org


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









Re: Question about issue tracker

2017-12-31 Thread John McDonnell
Hi Cowwoc,

At the moment NetBeans in migrating over to Apache, and in the latter half
of 2017, the first initial code drop took place containing the NetBeans
platform and the basic Java modules, etc...  As a result the old codebase
stored in Oracle, i.e. https://netbeans.org/community/sources/ is no longer
applicable for use since the more up to date changes are happening in the
code base found: https://github.com/apache/incubator-netbeans

This means the daily builds should be taken from here:
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/


In relation to the exception reporter I believe there was some discussion
about this, but I cannot seem to find it on the mailing lists, so maybe
I'm imagining this.  But your right, something will need to be done about
this.


Please check out the new daily builds and please file any defects against
the JIRA link previously provided. - If there are any high profile defects
that might block you please report them as soon as possible thanks.

John

On 31 December 2017 at 12:42, cowwoc  wrote:

> Hi Geertjan,
>
> I am getting the nightly builds from http://bits.netbeans.org/
> download/trunk/nightly/latest/
>
> Gili
>
>
> On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:
>
> Which nightly builds are you referring to specifically?
>
> Can you provide a URL just to make sure we’re talking about the same thing?
>
> Gj
>
> On Sunday, December 31, 2017, cowwoc  wrote:
>
>> Hi,
>>
>> Are there any plans to open up (migrate) the issue tracker for the
>> broader apache community to tackle existing/old Netbeans bugs?
>>
>> I ask because I feel like the bandwidth for fixing Java Editor bugs is
>> like sucking a milkshake through a straw: major bugs are being reported at
>> an expoentially-growing rate and they are being fixed at a rate of 1-2 a
>> week. The nightly builds are frankly barely usable anymore. I am
>> specifically concerned about Maven + Java projects where I routinely get
>> NullPointerExceptions and "slow action" errors (actions taking 13-20
>> seconds to complete on a seemingly random basis).
>>
>> This component needs more love. And soon. Can you please prioritize
>> accordingly?
>>
>> Thank you,
>> Gili
>>
>> (For context, I've been using Netbeans since 1999 so when I say things
>> are unstable I've got a long track-record to judge by)
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>


Re: Question about issue tracker

2017-12-31 Thread cowwoc

Hi Geertjan,

I am getting the nightly builds from 
http://bits.netbeans.org/download/trunk/nightly/latest/


Gili

On 2017-12-31 3:10 AM, Geertjan Wielenga wrote:

Which nightly builds are you referring to specifically?

Can you provide a URL just to make sure we’re talking about the same 
thing?


Gj

On Sunday, December 31, 2017, cowwoc > wrote:


Hi,

Are there any plans to open up (migrate) the issue tracker for the
broader apache community to tackle existing/old Netbeans bugs?

I ask because I feel like the bandwidth for fixing Java Editor
bugs is like sucking a milkshake through a straw: major bugs are
being reported at an expoentially-growing rate and they are being
fixed at a rate of 1-2 a week. The nightly builds are frankly
barely usable anymore. I am specifically concerned about Maven +
Java projects where I routinely get NullPointerExceptions and
"slow action" errors (actions taking 13-20 seconds to complete on
a seemingly random basis).

This component needs more love. And soon. Can you please
prioritize accordingly?

Thank you,
Gili

(For context, I've been using Netbeans since 1999 so when I say
things are unstable I've got a long track-record to judge by)


-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org

For additional commands, e-mail: users-h...@netbeans.apache.org


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






Re: Question about issue tracker

2017-12-31 Thread John McDonnell
Hi,

Which Nightly builds are you referring too? i.e. where are you getting them
from?

As for the bug tracker, there are no current plans to migrate bugs from
https://netbeans.org/bugzilla/ to
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=216 If you
know of any bugs that are on the old Bugzilla and there still affecting you
then please make sure you open the defect in JIRA and maybe post on this
mailing list to help draw attention to it.

Regards

John



On 31 December 2017 at 06:28, cowwoc  wrote:

> Hi,
>
> Are there any plans to open up (migrate) the issue tracker for the broader
> apache community to tackle existing/old Netbeans bugs?
>
> I ask because I feel like the bandwidth for fixing Java Editor bugs is
> like sucking a milkshake through a straw: major bugs are being reported at
> an expoentially-growing rate and they are being fixed at a rate of 1-2 a
> week. The nightly builds are frankly barely usable anymore. I am
> specifically concerned about Maven + Java projects where I routinely get
> NullPointerExceptions and "slow action" errors (actions taking 13-20
> seconds to complete on a seemingly random basis).
>
> This component needs more love. And soon. Can you please prioritize
> accordingly?
>
> Thank you,
> Gili
>
> (For context, I've been using Netbeans since 1999 so when I say things are
> unstable I've got a long track-record to judge by)
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>


Re: Question about issue tracker

2017-12-31 Thread Geertjan Wielenga
Which nightly builds are you referring to specifically?

Can you provide a URL just to make sure we’re talking about the same thing?

Gj

On Sunday, December 31, 2017, cowwoc  wrote:

> Hi,
>
> Are there any plans to open up (migrate) the issue tracker for the broader
> apache community to tackle existing/old Netbeans bugs?
>
> I ask because I feel like the bandwidth for fixing Java Editor bugs is
> like sucking a milkshake through a straw: major bugs are being reported at
> an expoentially-growing rate and they are being fixed at a rate of 1-2 a
> week. The nightly builds are frankly barely usable anymore. I am
> specifically concerned about Maven + Java projects where I routinely get
> NullPointerExceptions and "slow action" errors (actions taking 13-20
> seconds to complete on a seemingly random basis).
>
> This component needs more love. And soon. Can you please prioritize
> accordingly?
>
> Thank you,
> Gili
>
> (For context, I've been using Netbeans since 1999 so when I say things are
> unstable I've got a long track-record to judge by)
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>