Hi,
I'm currently working on adding support for NetBeans 11.3 to the NBAndroid
project.
I think this project would benefit a lot from the integration into the
NetBeans core. For example CI-Builds could show incompatibilities early and
more hands on the code would be highly appreciated.
What I wo
How can we get that data?
On Sun, 9 Feb 2020, 18:00 Eirik Bakke, wrote:
> > We can already identify any single client. So this could also be
> achieved by removing duplicates from the log in any month?
>
> Oh, in that case, yes--we should already be able to compile real usage
> statistics then.
I had a similar problem on an earlier release which I resolved by some have
cert store manipulation. This may be a workaround. Added similar comments to
ticket.
http://mail-archives.apache.org/mod_mbox/netbeans-dev/201912.mbox/%3ccahw6w1t64cvdktjeufsvp+cvhp_ipe6qapb+hxwe2-k82ps...@mail.gmail.com
So on one of the deltas listed I see it removing gnu debugger in place of what
looked like the proprietary one. Could the gnu debugger be resurrection and
used instead?
If clank is basically a third party product can an external dependency be added
and used instead of including it directly as p
Thanks for reporting this issue Ken. It would be good to get something in
the issue tracker for this problem. I haven't used the auto-generation of
new JPA controllers. I usually create my own so I haven't come across this
issue...but I'll see if I can replicate this problem. I may not personal
Hi folks,
I will go for preparing voting candidate 1 for Apache NetBeans 11.3.
If you found a major issue in 11.3 beta 3 please report.
Best Regards
Eric
On Fri, Feb 14, 2020 at 3:13 PM Eric Barboni wrote:
> No problem
>
> An issue was tagged as blocker for 11.3 but it seems that workaround by
> configuration make user go through the issue.
> https://issues.apache.org/jira/browse/NETBEANS-3810
> For me it's not a blocker, it's annoying for people
Ok,
As I was "RC" for NetBeans maven artefacts.
I will prepare and append the standard vote with the maven artefacts. Saving
72h.
(for each VC needed of course)
Regards
Eric
-Message d'origine-
De : Geertjan Wielenga
Envoyé : vendredi 14 février 2020 15:32
À : dev
Objet : Re: A
Hi Eric,
I think you should do a last call on this mailing list, maybe the users
mailing list as well, for any blockers on 11.3 beta3 and then setup the
voting candidate.
Thanks for your excellent work on this release.
Gj
On Fri, Feb 14, 2020 at 3:13 PM Eric Barboni wrote:
> No problem
>
> An
I have calmed down and wish to apologize for the harshness of my comments last
night. I will download the latest source and review the code that generates the
controllers et all. I will suggest that there should be two choices for JPA
Controllers, one for stand alone and one for application serv
No problem
An issue was tagged as blocker for 11.3 but it seems that workaround by
configuration make user go through the issue.
https://issues.apache.org/jira/browse/NETBEANS-3810
For me it's not a blocker, it's annoying for people wanting to adopt Apache
NetBeans.
Do you feel that I can setup
On Fri, 14 Feb 2020 at 13:55, Eric Bresie wrote:
>
> For more specific example, on the page for 12 could have references like:
>
> Milestones for 12:
> https://github.com/apache/netbeans/milestone/5
>
> Labels for 12
> https://github.com/apache/netbeans/labels/NB12.0
So, we still have labels and
Why not,
If we refactor a bit the table to start with LTS .0 at the beginning we can
remove release column and add 11.X 12.X ... column and put the link to
milestone and confluence.
Will make documentation more browsable too.
Best Regards
Eric
-Message d'origine-
De : Eric Bresie
For more specific example, on the page for 12 could have references like:
Milestones for 12:
https://github.com/apache/netbeans/milestone/5
Labels for 12
https://github.com/apache/netbeans/labels/NB12.0
And if and when a Pull request is made for 12 that could be regencies as
well.
On Fri, Feb 1
Slightly off topic and a little bit of a brain dump on some thoughts around
this topic but
On the quarterly release schedule page, is it worth wild to add references to
the expected or already released changes in some way?
Maybe add references to github milestone tags, labels, or pr that is the
Hi Ivan,
Am 14.02.20 um 07:30 schrieb Ivan Soleimanipour:
On 2/13/20 6:23 AM, Peter Kovacs wrote:
Okay,
I had to remove validation.nb.cluster.cnd=cnd.kit, too.
Now I get the Target "all-cnd" does not exist in the project "main".
error.
However I get the same error when trying to build dli
16 matches
Mail list logo