Seems like a good candidate, only one I have seen recently.
Colors look a tad bit loud, but then it is supposed to be a "Splash" screen
isn't it?
Not at all a criticism: that would be when it is boring and flat colored.
-Original Message-
From: Geertjan Wielenga
I remember Netbeans used to produce file dumps for parsing errors and
ask users to attach them to bug reports... What happened to that?
Having run into many such bugs in the past I usually can't share the
full project because of its commercial nature, or I can't remember what
I did to
Could this be a case of someone importing java.sql.Date by accident when
only java.util.Date is needed? In JDK8 this would not cause an immediate
problem, but JDK9 might have moved the java.sql.* classes to a separate
now-inaccessible module.
On 3/28/18, 10:06 AM, "Antonio"
Yes, good point, I will try to gather more information and add it to the
JIRAs as each of these bugs reappear. Each of these bugs are intermittent,
so I'm not quite sure how to reproduce them yet.
For a start, I added some sample class files to
https://issues.apache.org/jira/browse/NETBEANS-430 ,
Mmmm java.sql.Date? That's weird.
AFAIK JIRA uses a JSON REST API, so no sql is involved (I think).
I wrote some instructions at [1] for setting up the JIRA plugin, but it
threw some NullPointerExceptions while running... :-(
[1]
Thank You, Geertjan!
BTW, when trying to add Apache NetBeans Jira to Services/Task
Repositories, I get an exception ("java.lang.NoClassDefFoundError:
java.sql.Date"). Probably a JDK 9 issue.
Kind regards
Peter
Am 28.03.2018 um 13:18 schrieb Geertjan Wielenga:
https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-491
Gj
On Wed, Mar 28, 2018 at 11:46 AM, Peter Nabbefeld
wrote:
>
> Hello,
>
> trying to submit an exception report leads me to
> http://statistics.netbeans.org/analytics/detail.do?id=232241
>
> As I'd
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 18 April 2018, 10:30 am PDT.
The report for your podling will form
Hi Eirik,
Thanks for reporting the bugs. One thing I'd like to point out is that
while it is sometimes possible for someone working on the code to fix a bug
based just on a stacktrace, having a way to reproduce a problem usually
leads to much faster and efficient fix.
This is particularly true
On Tue, 27 Mar 2018 at 20:45 Antonio wrote:
> In my case: Jira is very slow. Finding an issue is a pain in the neck.
>
Well, yes, there's that as well! :-) But we need somewhere it all comes
together somehow - the old bugzilla had issues, patches and code reviews
tied
Hello,
trying to submit an exception report leads me to
http://statistics.netbeans.org/analytics/detail.do?id=232241
As I'd expect JIRA on Apache web site should be used (and NetBeans
BugZilla seems to be empty now), I'd see this as a broken (important)
feature.
My original problem is a
I’m also for it, to sync Github with Jira, atm the bug section at Github for
incubator-netbeans is hidden. I think there was a reason for that, but this is
not that good, because as often as I said, not everyone is using JIRA and will
use it. They see github and will try to add a ticket and
On 28/03/18 04:26, cowwoc wrote:
No need to get upset. I'm more than happy to walk back my numbers if the
data backs it up.
Who's upset? I was just stating that people is busy doing work here.
Whoever is not happy with the current pace of development (issue solving
or any other aspect of
Hi Gili,
I think you’ll find most people would rather fix issues and improve
NetBeans than respond to these kinds of e-mails — and all this
investigation you’ve done and so on: maybe it is better spent on
investigating or highlighting some specific issues? Would you prefer I
spend time responding
14 matches
Mail list logo