Dear all,
I'm sorry to skip two weeks without reports, but life is never makes it
easy nowadays.
So the new splash screen has landed in git. Github landed at Microsoft,
and we are ready to do yet another RC as it seems we finished the IP
clearance of the first code drop. And yes the second c
I think it would be good. We already have dev and user. The same reason we
decided to start with the 2 until we had any real need for more, versus all
the tech specific lists we had at NetBeans.org, seems reasonable, and to
apply here as well. If it is an issue, we'll know/see it, and if not, then
And if we get a chance the branding when you create a new platform
application project is still the old branding.
(https://issues.apache.org/jira/browse/NETBEANS-990) I could not find
the code responsible for that at the first scan.
On 06/24/2018 12:16 PM, Geertjan Wielenga wrote:
Yes.
Gj
Hello,
I believe all the Apache NetBeans contributors should use the dev@ mailing list.
The dev@ mailing list is our Apache 'central square' so to speak and even if we
don't work on the same particular issue, we should get to know each-other, at
least by name.
The separate netcat@ mailing list
Could we refine/rewrite the criteria then?
Also as far as remember we had a bug/issue classifying table somewhere
on what is blocker, critical major, etc.
BTW, Thanks for your attention the number of critical issues are down to
16! Good progress!
On 06/24/2018 12:56 PM, Geertjan Wielenga w
I think what we're trying to do is merge the NetCAT concept into the Apache
Way of doing things.
The way I imagine that working is that the PPMC vote can only begin once
NetCAT gives its 'go'.
I.e., NetCAT gives us a dedicated testing community, which is a plus.
However, I agree, only blockers s
I don't mind if we delay the release, but I have some remarks regarding these
new (to me) criteria
I guess they are probably a copy-paste of the NetCAT criteria we had under Sun
/ Oracle?
The only voted policy we have under Apache is written here:
https://cwiki.apache.org/confluence/display/NE
Yes.
Gj
On Sun, Jun 24, 2018 at 8:56 PM, Sven Reimers
wrote:
> So we still need to update the updater as well for NetBeans 9.0 release?
>
> -Sven
>
> Geertjan Wielenga schrieb am
> So., 24. Juni 2018, 19:25:
>
> > I don't believe the update dialog has been updated -- I only updated the
> > spl
So we still need to update the updater as well for NetBeans 9.0 release?
-Sven
Geertjan Wielenga schrieb am
So., 24. Juni 2018, 19:25:
> I don't believe the update dialog has been updated -- I only updated the
> splash screen and the About box.
>
> Those new images are in 'ide.branding'.
>
> Gj
Change it ti ActionListener extension and use the annotations there. Better
still put it in a GitHub repo so me and others can take a look and help.
Gj
On Sun, Jun 24, 2018 at 7:49 PM, Peter Nabbefeld
wrote:
> Just because it's already there. ;-)
>
> I'm just hanging around with some old code
Just because it's already there. ;-)
I'm just hanging around with some old code ... will have to figure out,
how to exactly change it.
Peter
Am 24.06.2018 um 19:47 schrieb Geertjan Wielenga:
The real question is why you're using CookieAction at all.
http://bits.netbeans.org/8.2/javadoc/or
The real question is why you're using CookieAction at all.
http://bits.netbeans.org/8.2/javadoc/org-openide-nodes/org/openide/util/actions/CookieAction.html
Gj
On Sun, Jun 24, 2018 at 7:28 PM, Peter Nabbefeld
wrote:
>
> Hello,
>
> in my class file, I've got the following lines of code:
>
> @A
Hello,
in my class file, I've got the following lines of code:
@ActionRegistration(displayName = "#CTL_GotoHTMLAction", lazy = false)
public class GotoHTMLAction extends CookieAction {
...
}
Why do I still need to implement the "getName()" method? Short answer,
of course, it's declared abstr
I don't believe the update dialog has been updated -- I only updated the
splash screen and the About box.
Those new images are in 'ide.branding'.
Gj
On Sun, Jun 24, 2018 at 6:36 PM, Sven Reimers
wrote:
> Hi all,
>
> can anyone confirm that the branding of the update dialog has been updated?
>
Definitely initialize everything again if you're using daily builds and so
on, also nobody will be able to reproduce your scenario otherwise.
Gj
On Sun, Jun 24, 2018 at 6:40 PM, Peter Nabbefeld
wrote:
> No - usually I'm trying not to initialize everything again and again, if
> not absolutely ne
No - usually I'm trying not to initialize everything again and again, if
not absolutely necessary. That's why I asked if others do have the same
problems. If not, I really do have to clean my user directory ...
Regards
Peter
Am 24.06.2018 um 16:56 schrieb Geertjan Wielenga:
Are you using a f
Hi all,
can anyone confirm that the branding of the update dialog has been updated?
I just tried with a local build of the latest 90release branch and saw the
old blue updater splash (this is on mac os).
Just trying to figure out if this is just me seeing this..
Thanks
-Sven
--
Sven Reimers
Are you using a fresh user directory, i.e., just to make sure nothing's
corrupt or reused from some previous NetBeans installation?
Gj
On Sun, Jun 24, 2018 at 2:21 PM, Peter Nabbefeld
wrote:
>
> Hello,
>
> just switched from release build 316 to 320. When I try to start it, I get
> a message "m
Hello,
just switched from release build 316 to 320. When I try to start it, I
get a message "module org.netbeans.modules.java.hints/1 missing", but
I've checked that, the modules are present in their appropriate folders.
So I'm wondering what happened - does anybody else use this build? Jus
19 matches
Mail list logo
