[RESULT] [VOTE] 2nd voting candidate for NetBeans HTML/Java API version 1.7
The release of HTML/Java API version 1.7 has been approved:
+1 binding votes :
Josh Juneau http://people.apache.org/phonebook.html?uid=javajuneau
Geertjan Wielenga http://people.apache.org/phonebook.html?uid=geertjan
Jan Lahoda http://people.apache.org/phonebook.html?uid=jlahoda
Eric Barboni http://people.apache.org/phonebook.html?uid=skygo
As such I have just moved the release bits to:
https://dist.apache.org/repos/dist/release/netbeans/netbeans-html4j/netbeans-html4j-1.7/
and I released the Maven staging repository to the central. Thanks for your
help!
-jt
PS: Next time I will include SHAxyz in the voting email.
PPS: I've published my key to https://www.apache.org/dist/netbeans/KEYS
st 6. 11. 2019 v 4:39 odesílatel Josh Juneau napsal:
> +1 (binding)
> - Verified checksums, signatures
> - Built successfully
> - mvn package successfully on OS X 10.13.6
>
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
>
> > On Nov 4, 2019, at 12:11 AM, Jaroslav Tulach
> wrote:
> >
> > Hi.
> > As my first attempt to accommodate the recent donation of various
> > presenters by DukeHoff GmbH, and release 1.7 of Apache NetBeans HTML/Java
> > API failed with a NOTICE file error and a bug in WebKitPresenterTest, I
> had
> > to prepare new bits. Please find the source at
> >
> >
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-html4j/netbeans-html4j-1.7/
> >
> > and the staged Maven artifacts at
> >
> https://repository.apache.org/content/repositories/orgapachenetbeans-1052/
> >
> > Please evaluate them again and cast your vote during next 72h. The
> process
> > of evaluation is the same as last week.
> >
> > What can you verify?
> >
> > ## checksums, signatures, etc.
> >
> > Obviously those should be correct.
> >
> > ## if it builds
> >
> > I used "mvn package -DskipTests" and I believe the compilation shall
> > succeed on JDK8, JDK11, JDK13 (Eric reported problem building on JDK13,
> but
> > it works for me).
> >
> > ## if the tests pass
> >
> > Use "mvn package". They may not - especially the newly donated modules
> are
> > very sensitive to surrounding environment. Getting them run on all
> > important platforms may take some time.
> >
> > If you want to report your findings, then please include the version of
> > operating system, version of JDK, version of the browser, etc. You may
> also
> > want to run them individually. E.g. "mvn -f browser test" or "mvn -f
> webkit
> > test".
> >
> > I know that browser doesn't seem to run on Windows 8 with Internet
> Explorer
> > (but it runs with Firefox instead). I know that webkit does run on Ubuntu
> > 18.04 with proper libraries ("libwebkit") installed. But those libraries
> > aren't present in Ubuntu 19.10 - there is "libwebkit2" and somebody would
> > have to adjust the code to use the "libwebkit2" code. In short, there are
> > many broken things in the browser and webkit modules - volunteers
> welcomed
> > to make them run!
> >
> > ## How to cast your vote?
> >
> > I propose the goal of 1.7 release to be to compile and execute its tests
> > (except browser and webkit modules) on all supported platforms. We should
> > collect the test failures in browser and webkit modules and find some
> > volunteers to fix them for some upcoming update release.
>
Re: [NETBEANS-3346] Upgrade asm to 5.2+
I do not have privileges to close the PR
https://github.com/apache/netbeans/pull/1108
Jose Contreras
El jue., 7 nov. 2019 a las 17:20, Jose Ch () escribió:
> I will, thanks for bringing it to my attention.
>
> Jose Contreras
>
> El jue., 7 nov. 2019 a las 16:28, Laszlo Kishalmi (<
> laszlo.kisha...@gmail.com>) escribió:
>
>> When you create your PR for 7.2, please close this one in favor of that:
>> https://github.com/apache/netbeans/pull/1108
>>
>>
>> On 11/7/19 1:41 PM, Jose Ch wrote:
>> > Thanks for your help Peter.
>> >
>> > I tested the PR and it works for both the asm5.2 and the asm7.2
>> branches. I
>> > also compare the output from the original asm5.0.1 with the new ones
>> > (ams5.2-asm7.2) and it was the same.
>> >
>> > I also tested using ASM API v6 & v7, the output was the same and I
>> worked
>> > without problems my daily projects. I will prepare the PR today.
>> >
>> > Jose Contreras
>> >
>> > El jue., 7 nov. 2019 a las 3:58, Peter Hull ()
>> > escribió:
>> >
>> >> On Wed, 6 Nov 2019 at 22:24, Jose Ch wrote:
>> >>> I will test the PR and do as you suggest Pete.
>> >> For what it's worth my implementation was a bit different:
>> >> private static class CtorDelVisitor extends AnnotationVisitor {
>> >> int[] indices;
>> >> /**
>> >> * Constructs a new {@link AnnotationVisitor}.
>> >> *
>> >> * @param api the ASM API version implemented by this
>> visitor. Must
>> >> be one of {@link
>> >> * Opcodes#ASM4}, {@link Opcodes#ASM5}, {@link
>> Opcodes#ASM6} or
>> >> {@link Opcodes#ASM7}.
>> >> */
>> >> public CtorDelVisitor(int api) {
>> >> super(api);
>> >> }
>> >> @Override
>> >> public AnnotationVisitor visitArray(String name) {
>> >> if ("delegateParams".equals(name)) { // NOI18N
>> >> return new AnnotationVisitor(api) {
>> >> List list = new ArrayList<>();
>> >> @Override
>> >> public void visit(String name, Object value) {
>> >> list.add((Integer) value);
>> >> }
>> >> @Override
>> >> public void visitEnd() {
>> >> int[] indices = new int[list.size()];
>> >> for (int i = 0; i < indices.length; ++i) {
>> >> indices[i] = list.get(i);
>> >> }
>> >> CtorDelVisitor.this.indices = indices;
>> >> }
>> >> };
>> >> } else {
>> >> return super.visitArray(name); // Not interested
>> >> }
>> >> }
>> >> }
>> >> I guess Svata's will be more efficient.
>> >>
>> >> It's a bit frustrating that the AnnotationNode forces us to visit each
>> >> array element in turn when all we need is the complete list, but I
>> think
>> >> there's no way around that. Visitor pattern makes my head spin, it
>> always
>> >> seems inside-out to me.
>> >>
>> >> Pete
>> >>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
>> For additional commands, e-mail: dev-h...@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
Blog Writer Access
Dear Geertjan, From time to time I'd like to post an article or two on our project blog, make the startup page more lively. Could you grant me the necessary rights to do that. I'm registered as lkihalmi in Apache Roller. Thank you! - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Debian and NetBeans
On 11/7/19 3:06 PM, stevenhrosenb...@gmail.com wrote: On Sat, 2019-11-02 at 11:37 -0700, Laszlo Kishalmi wrote: The maintenance burden is probably too high especially compared to the alternative ways (installes, flatpack, snap). Having it in the repo is just another source of confusion. I just installed Netbeans 11.2 on Debian with a Flatpak from Flathub: https://flathub.org/apps/details/org.apache.netbeans While the process took a little long to finish, the end result was a perfectly working version of NetBeans 11.2 that found my Netbeans projects automatically. This is a quick and easy way to get an up-to-date Netbeans on most Linux distros, even something as old as Debian Stable, which I am using. Thank you for the flatpak people updating NetBeans so quickly. That said, I would still like to see Netbeans packaged for Debian. Hopefully we can get it in the next stable release -- and also hopefully Ubuntu will update its version. As of we have Flatpak and Snapcraft distribution, the real question is does it worth to maintain the Debian package. As the package maintainer explained, Debian has its policies which needs to be met. Unless we replace it with a script which just downloads the binaries and unpacks it somewhere (which pretty much Flatpak is doing under the hood), I see no reason to continue packaging the full IDE on Debian, while we have more reliable options. The Fedora power-user world is MAD about Fedora Silverblue ( https://silverblue.fedoraproject.org/) and using Flatpaks for applications, and if it works as well as it does in Debian, so much the better. Thanks to whoever put this Flatpak together (it is credited to Flathub maintainers). - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-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: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [NETBEANS-3346] Upgrade asm to 5.2+
I will, thanks for bringing it to my attention.
Jose Contreras
El jue., 7 nov. 2019 a las 16:28, Laszlo Kishalmi (<
laszlo.kisha...@gmail.com>) escribió:
> When you create your PR for 7.2, please close this one in favor of that:
> https://github.com/apache/netbeans/pull/1108
>
>
> On 11/7/19 1:41 PM, Jose Ch wrote:
> > Thanks for your help Peter.
> >
> > I tested the PR and it works for both the asm5.2 and the asm7.2
> branches. I
> > also compare the output from the original asm5.0.1 with the new ones
> > (ams5.2-asm7.2) and it was the same.
> >
> > I also tested using ASM API v6 & v7, the output was the same and I worked
> > without problems my daily projects. I will prepare the PR today.
> >
> > Jose Contreras
> >
> > El jue., 7 nov. 2019 a las 3:58, Peter Hull ()
> > escribió:
> >
> >> On Wed, 6 Nov 2019 at 22:24, Jose Ch wrote:
> >>> I will test the PR and do as you suggest Pete.
> >> For what it's worth my implementation was a bit different:
> >> private static class CtorDelVisitor extends AnnotationVisitor {
> >> int[] indices;
> >> /**
> >> * Constructs a new {@link AnnotationVisitor}.
> >> *
> >> * @param api the ASM API version implemented by this visitor.
> Must
> >> be one of {@link
> >> * Opcodes#ASM4}, {@link Opcodes#ASM5}, {@link
> Opcodes#ASM6} or
> >> {@link Opcodes#ASM7}.
> >> */
> >> public CtorDelVisitor(int api) {
> >> super(api);
> >> }
> >> @Override
> >> public AnnotationVisitor visitArray(String name) {
> >> if ("delegateParams".equals(name)) { // NOI18N
> >> return new AnnotationVisitor(api) {
> >> List list = new ArrayList<>();
> >> @Override
> >> public void visit(String name, Object value) {
> >> list.add((Integer) value);
> >> }
> >> @Override
> >> public void visitEnd() {
> >> int[] indices = new int[list.size()];
> >> for (int i = 0; i < indices.length; ++i) {
> >> indices[i] = list.get(i);
> >> }
> >> CtorDelVisitor.this.indices = indices;
> >> }
> >> };
> >> } else {
> >> return super.visitArray(name); // Not interested
> >> }
> >> }
> >> }
> >> I guess Svata's will be more efficient.
> >>
> >> It's a bit frustrating that the AnnotationNode forces us to visit each
> >> array element in turn when all we need is the complete list, but I think
> >> there's no way around that. Visitor pattern makes my head spin, it
> always
> >> seems inside-out to me.
> >>
> >> Pete
> >>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Debian and NetBeans
On Sat, 2019-11-02 at 11:37 -0700, Laszlo Kishalmi wrote: > The maintenance burden is probably too high especially compared to > the > alternative ways (installes, flatpack, snap). Having it in the repo > is > just another source of confusion. I just installed Netbeans 11.2 on Debian with a Flatpak from Flathub: https://flathub.org/apps/details/org.apache.netbeans While the process took a little long to finish, the end result was a perfectly working version of NetBeans 11.2 that found my Netbeans projects automatically. This is a quick and easy way to get an up-to-date Netbeans on most Linux distros, even something as old as Debian Stable, which I am using. That said, I would still like to see Netbeans packaged for Debian. Hopefully we can get it in the next stable release -- and also hopefully Ubuntu will update its version. The Fedora power-user world is MAD about Fedora Silverblue ( https://silverblue.fedoraproject.org/) and using Flatpaks for applications, and if it works as well as it does in Debian, so much the better. Thanks to whoever put this Flatpak together (it is credited to Flathub maintainers). - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [NETBEANS-3346] Upgrade asm to 5.2+
When you create your PR for 7.2, please close this one in favor of that:
https://github.com/apache/netbeans/pull/1108
On 11/7/19 1:41 PM, Jose Ch wrote:
Thanks for your help Peter.
I tested the PR and it works for both the asm5.2 and the asm7.2 branches. I
also compare the output from the original asm5.0.1 with the new ones
(ams5.2-asm7.2) and it was the same.
I also tested using ASM API v6 & v7, the output was the same and I worked
without problems my daily projects. I will prepare the PR today.
Jose Contreras
El jue., 7 nov. 2019 a las 3:58, Peter Hull ()
escribió:
On Wed, 6 Nov 2019 at 22:24, Jose Ch wrote:
I will test the PR and do as you suggest Pete.
For what it's worth my implementation was a bit different:
private static class CtorDelVisitor extends AnnotationVisitor {
int[] indices;
/**
* Constructs a new {@link AnnotationVisitor}.
*
* @param api the ASM API version implemented by this visitor. Must
be one of {@link
* Opcodes#ASM4}, {@link Opcodes#ASM5}, {@link Opcodes#ASM6} or
{@link Opcodes#ASM7}.
*/
public CtorDelVisitor(int api) {
super(api);
}
@Override
public AnnotationVisitor visitArray(String name) {
if ("delegateParams".equals(name)) { // NOI18N
return new AnnotationVisitor(api) {
List list = new ArrayList<>();
@Override
public void visit(String name, Object value) {
list.add((Integer) value);
}
@Override
public void visitEnd() {
int[] indices = new int[list.size()];
for (int i = 0; i < indices.length; ++i) {
indices[i] = list.get(i);
}
CtorDelVisitor.this.indices = indices;
}
};
} else {
return super.visitArray(name); // Not interested
}
}
}
I guess Svata's will be more efficient.
It's a bit frustrating that the AnnotationNode forces us to visit each
array element in turn when all we need is the complete list, but I think
there's no way around that. Visitor pattern makes my head spin, it always
seems inside-out to me.
Pete
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [NETBEANS-3346] Upgrade asm to 5.2+
Thanks for your help Peter.
I tested the PR and it works for both the asm5.2 and the asm7.2 branches. I
also compare the output from the original asm5.0.1 with the new ones
(ams5.2-asm7.2) and it was the same.
I also tested using ASM API v6 & v7, the output was the same and I worked
without problems my daily projects. I will prepare the PR today.
Jose Contreras
El jue., 7 nov. 2019 a las 3:58, Peter Hull ()
escribió:
> On Wed, 6 Nov 2019 at 22:24, Jose Ch wrote:
> >
> > I will test the PR and do as you suggest Pete.
> For what it's worth my implementation was a bit different:
> private static class CtorDelVisitor extends AnnotationVisitor {
> int[] indices;
> /**
> * Constructs a new {@link AnnotationVisitor}.
> *
> * @param api the ASM API version implemented by this visitor. Must
> be one of {@link
> * Opcodes#ASM4}, {@link Opcodes#ASM5}, {@link Opcodes#ASM6} or
> {@link Opcodes#ASM7}.
> */
> public CtorDelVisitor(int api) {
> super(api);
> }
> @Override
> public AnnotationVisitor visitArray(String name) {
> if ("delegateParams".equals(name)) { // NOI18N
> return new AnnotationVisitor(api) {
> List list = new ArrayList<>();
> @Override
> public void visit(String name, Object value) {
> list.add((Integer) value);
> }
> @Override
> public void visitEnd() {
> int[] indices = new int[list.size()];
> for (int i = 0; i < indices.length; ++i) {
> indices[i] = list.get(i);
> }
> CtorDelVisitor.this.indices = indices;
> }
> };
> } else {
> return super.visitArray(name); // Not interested
> }
> }
> }
> I guess Svata's will be more efficient.
>
> It's a bit frustrating that the AnnotationNode forces us to visit each
> array element in turn when all we need is the complete list, but I think
> there's no way around that. Visitor pattern makes my head spin, it always
> seems inside-out to me.
>
> Pete
>
Re: Netbeans hangs in Mac since Netbeans 8.2 to now
When i was in eclipse, i was using a plugin call maven runner. Just a list of shortcut of maven goals. From: Carl Mosca Sent: Thursday, November 7, 2019 6:34 PM To: dev@netbeans.apache.org Cc: Geertjan Wielenga Subject: Re: Netbeans hangs in Mac since Netbeans 8.2 to now Ok I am now slightly more confused. What does your plugin do that can’t already be done in netbeans? Will try to look when at a computer next. On Thu, Nov 7, 2019 at 4:12 AM Peter Cheung wrote: > Dear Sir > Sorry my bad english, my plugins source is updated in. So if you > install my plugin in your netbeans, i believe netbeans will hangs in after > few starts. > https://peter.quantr.hk/2019/11/netbeans-hangs-in-mac-since-netbeans-8-2-to-now/ > > Thanks > From Peter > > From: Geertjan Wielenga > Sent: Wednesday, November 6, 2019 7:32 PM > To: dev > Subject: Re: Netbeans hangs in Mac since Netbeans 8.2 to now > > Your subject line should be "My plugin hangs in Mac since NetBeans IDE > 8.2.". > > And then you would point to the sources and to the steps to reproduce the > problem. > > Gj > > On Wed, Nov 6, 2019 at 3:23 AM Carl Mosca wrote: > > > Where can we get additional details? Perhaps I missed something in the > > post. > > > > Regards, > > Carl > > > > On Tue, Nov 5, 2019 at 9:19 PM Peter Cheung > wrote: > > > > > Hi All > > >Netbeans hangs in Mac since Netbeans 8.2 to now. > > > > > > https://peter.quantr.hk/2019/11/netbeans-hangs-in-mac-since-netbeans-8-2-to-now/ > > > thanks > > > Peter > > > > > > > > > -- > > Carl J. Mosca > > > -- Regards, Carl
Re: Attaching JavaFX Javadoc and Sources
On 11/3/19 1:58 AM, Thomas Zimmermann wrote: until the maintainers find the time, would you mind testing what problems remain after merging my PR? I posted my test results as a comment on the pull request: https://github.com/apache/netbeans/pull/1548#issuecomment-551237510 It's a *huge* improvement. In fact, some things that work now I didn't even know were supposed to work -- that's how broken they were. So thank you very much for all the progress. Adding the Javadoc works great, but there are some regressions when you then add the Sources in addition to the Javadoc. Also, there are some things that work with only the Sources in an Ant project that don't work in a Maven project. The details are in my comment. Thank you again, Thomas. John - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Functional tests (docker support)
Hi All Maybe I am wrong but I cannot find any high-level functional tests for docker module. Are there any? Do we want such? What's policy on crating/running these (I assume that we would need to run them on travis?) -- regards Bartosz Tomasik - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Handling release updates
On Thu, 7 Nov 2019 at 17:05, Korney Czukowski wrote: > Although even with almost > everything in place, there's still this issue with nbm signing, so > practically the Update Center cannot be used for now, right (else you > would have already used it)? If this is the case, then a (trusted) > offline installed could be used as a temporarily and somewhat ugly solution. The UC is useful now, and can be used for things like RCP harness building. However, the iDE will show a warning for nbms there. All binary elements, including the zips and nbms, are already gpg signed locally. We just need a temporary solution to (jar) sign the updated nbm files as well. The solution you suggest would actually be more complicated not less. We still have to sign them! Getting them in the existing UC is easy after that. Thanks, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Handling release updates
Then I must have misunderstood your earlier comment about issues due to changes in the build system, my apologies. Although even with almost everything in place, there's still this issue with nbm signing, so practically the Update Center cannot be used for now, right (else you would have already used it)? If this is the case, then a (trusted) offline installed could be used as a temporarily and somewhat ugly solution. And yes, I meant generally any release within the quarterly cycle that is assigned a version number, sorry for not being clear. Regards! On 2019/11/07 16:24:54, Neil C Smith On Thu, 7 Nov 2019 at 16:14, Korney Czukowski If the Update Center is out of the question for now, it isn't! That bit is not the problem. The only problem to delivery at the moment is signing the nbm with a certificate that's trusted by the IDE. Of course, both options should be viewed only as a temporary solution for situations where you guys really want to push an update ASAP. IMO, the end goal should be that any module that NetBeans platform can possibly live without, can be installed or updated from the Update Center by default, and the incremental releases with the version numbers would just include the most recent stable versions of those modules. That is already the case, although not quite sure what you mean by incremental releases - note that 11.2. is not an incremental release. There is just the issue again that the nbms in that distribution update centre are not signed at present. eg. 11.2 is all at https://dist.apache.org/repos/dist/release/netbeans/netbeans/11.2/nbms/ Longer term the Apache mirrors may not be the best way to distribute the modules though. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-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: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Handling release updates
On Thu, 7 Nov 2019 at 16:14, Korney Czukowski wrote: > If the Update Center is out of the question for now, it isn't! That bit is not the problem. The only problem to delivery at the moment is signing the nbm with a certificate that's trusted by the IDE. > Of course, both options should be viewed only as a temporary solution > for situations where you guys really want to push an update ASAP. IMO, > the end goal should be that any module that NetBeans platform can > possibly live without, can be installed or updated from the Update > Center by default, and the incremental releases with the version numbers > would just include the most recent stable versions of those modules. That is already the case, although not quite sure what you mean by incremental releases - note that 11.2. is not an incremental release. There is just the issue again that the nbms in that distribution update centre are not signed at present. eg. 11.2 is all at https://dist.apache.org/repos/dist/release/netbeans/netbeans/11.2/nbms/ Longer term the Apache mirrors may not be the best way to distribute the modules though. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Handling release updates
If the Update Center is out of the question for now, maybe it would be feasible to create an offline update installer consisting only of a couple of nbms that need to be updated, that would update an existing NetBeans installation? Then it should be possible to vote for just for this very limited portion of the sources and avoid issues with early merging. If the installer is signed, there should not be any trust issues regarding the content it carries. If this is hard to do, maybe even just posting the patched nbms somewhere and instructing the affected users how to replace them manually could suffice, given the NetBeans userbase profile, it might be acceptable to many. Of course, both options should be viewed only as a temporary solution for situations where you guys really want to push an update ASAP. IMO, the end goal should be that any module that NetBeans platform can possibly live without, can be installed or updated from the Update Center by default, and the incremental releases with the version numbers would just include the most recent stable versions of those modules. On 2019/11/07 10:56:49, Neil C Smith wrote: > On Thu, 7 Nov 2019 at 10:43, Geertjan Wielenga wrote:> > > Can someone -- preferably Eric, Neil, Laszlo, Jan, or Matthias, suggest a> > > way forward to get an update out, i.e., we could even call it 11.2.1,> > > maybe, if we can't figure out how to release the two modules (what would be> > > the problem with doing it as Laszlo did for Gradle)?> > > We can't do it as Laszlo did for Gradle because of changes in the> > build system. And in many respects this should be simpler.> > > We need to> > > * merge the relevant PRs to master and test. (perhaps provide nbms via> > temporary UC?)> > * (ideally) cherry pick locally and open new PRs on top of release112> > (better than pushing to release branch IMO because of Travis, etc.)> > * Merge to release branch.> > * write the hash into the release JSON file (probably 11.2-patch1) and> > trigger a build.> > * ***somehow*** sign the relevant nbms.> > * vote on source zip and required nbms.> > > There is one more potential PR for the patch update. They all have> > Cherry Pick labels on them.> > > https://github.com/apache/netbeans/pulls?q=is%3Apr+is%3Aopen+label%3A%22Cherry+Pick%22> > > I'm happy to RM the process from point 3, but I'd rather the current> > PR authors handled steps 1 and 2. If I do, add me as a reviewer on> > the step 2 PR when they're ready.> > > And we still need an answer for the signing part for 11.2 updates -> > perhaps the web signing via Apache is the way, but I'll need to follow> > up with infra. Few suggestions for 11.3+ are great there but don't> > help us with this update.> > > Best wishes,> > > Neil> > > -> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org> > For additional commands, e-mail: dev-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: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Updating the quarter release for xx.3
On Thu, 7 Nov 2019, 13:33 Eric Barboni, wrote: >Can we shift by a month the schedule of xx.3 eventually whiteout messing > quarterly release ? Allowing maybe more volunteers (me for example :D ) > Given problems with 11.2 related to late testing with latest JDK, I think there's a conversation to be had about shifting the whole schedule back a month anyway. If only 11.3 is a month late, that means no development *at all* before 12.0 freeze! Some people may have more free time then, but I'll admit I had reservations suggesting those dates. Best wishes, Neil >
[DISCUSS] Updating the quarter release for xx.3
Hi, I'm not sure how to be neutral on this mail. The current release schedule for x.3 is around and December and beginning of January. This is a particular period of time where I'm personally can't connect in an efficient manner. (Christmas, new year's, and also ski) That prevents me (and maybe others) to volunteers for being RM for this particular timeframe xx.3. Can we shift by a month the schedule of xx.3 eventually whiteout messing quarterly release ? Allowing maybe more volunteers (me for example :D ) Best Regards Eric
Re: [DISCUSS] Handling release updates
On Thu, 7 Nov 2019 at 10:43, Geertjan Wielenga wrote: > Can someone -- preferably Eric, Neil, Laszlo, Jan, or Matthias, suggest a > way forward to get an update out, i.e., we could even call it 11.2.1, > maybe, if we can't figure out how to release the two modules (what would be > the problem with doing it as Laszlo did for Gradle)? We can't do it as Laszlo did for Gradle because of changes in the build system. And in many respects this should be simpler. We need to * merge the relevant PRs to master and test. (perhaps provide nbms via temporary UC?) * (ideally) cherry pick locally and open new PRs on top of release112 (better than pushing to release branch IMO because of Travis, etc.) * Merge to release branch. * write the hash into the release JSON file (probably 11.2-patch1) and trigger a build. * ***somehow*** sign the relevant nbms. * vote on source zip and required nbms. There is one more potential PR for the patch update. They all have Cherry Pick labels on them. https://github.com/apache/netbeans/pulls?q=is%3Apr+is%3Aopen+label%3A%22Cherry+Pick%22 I'm happy to RM the process from point 3, but I'd rather the current PR authors handled steps 1 and 2. If I do, add me as a reviewer on the step 2 PR when they're ready. And we still need an answer for the signing part for 11.2 updates - perhaps the web signing via Apache is the way, but I'll need to follow up with infra. Few suggestions for 11.3+ are great there but don't help us with this update. Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: [DISCUSS] Handling release updates
Can someone -- preferably Eric, Neil, Laszlo, Jan, or Matthias, suggest a way forward to get an update out, i.e., we could even call it 11.2.1, maybe, if we can't figure out how to release the two modules (what would be the problem with doing it as Laszlo did for Gradle)? Gj On Thu, Nov 7, 2019 at 11:05 AM Geertjan Wielenga wrote: > There appear to be two issues that would be best to make available as > updates as soon as we can -- relating to nb-javac and HTML parsing. > > What would be the problem with voting on the sources of those two modules > and then making them available via the plugin portal? > > Gj > > On Mon, Nov 4, 2019 at 6:54 PM Eric Barboni wrote: > >> Hi, >> Not sure what the needs exactly. >> But If you rebuild a patched NetBeans with a forced version >> RELEASE112-update1. You can pick the patched nbm you want. And alter pom to >> put RELEASE112 for dep (you know are were not modified). >> >> Then vote with sources + the limited artefacts RELEASE112-update1 to be >> able to release them in central >> >> Best Regards >> Eric >> >> >> >> >> -Message d'origine- >> De : Neil C Smith >> Envoyé : mardi 29 octobre 2019 18:42 >> À : dev >> Objet : Re: [DISCUSS] Handling release updates >> >> On Tue, 29 Oct 2019 at 15:53, Eric Barboni wrote: >> > You cannot do a RELEASE112.1 in the >> org.netbeans(api,modules,clusters,external) without rebuild the whole >> NetBeans stack because every pom will need the RELEASE112.1 version on >> dependencies nbm being a side artefacts. >> > It's not possible to overwrite a released artefacts you cannot do a >> RELEASE112 again. >> >> Yes, I know artefacts can't be overwritten, so thought as much. Kind of >> makes it even harder to push a patch release for Maven modules. >> Would be good if that was not the case, but I guess it's not a short term >> (ie. 11.2 update) mechanism. And Maven probably won't get nb-javac module >> fix, although that's probably not that much of an issue. >> >> Still think it worth considering longer term. Means only one set of NBMs >> need signing and maintaining, and may remove some issues around using >> Apache mirrors for the UCs. How feasible is changing the modules to use >> spec version and RELEASE11X just for overarching POM files? >> >> Best wishes, >> >> Neil >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org >> For additional commands, e-mail: dev-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: dev-unsubscr...@netbeans.apache.org >> For additional commands, e-mail: dev-h...@netbeans.apache.org >> >> For further information about the NetBeans mailing lists, visit: >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists >> >> >> >>
Re: Netbeans hangs in Mac since Netbeans 8.2 to now
Ok I am now slightly more confused. What does your plugin do that can’t already be done in netbeans? Will try to look when at a computer next. On Thu, Nov 7, 2019 at 4:12 AM Peter Cheung wrote: > Dear Sir > Sorry my bad english, my plugins source is updated in. So if you > install my plugin in your netbeans, i believe netbeans will hangs in after > few starts. > https://peter.quantr.hk/2019/11/netbeans-hangs-in-mac-since-netbeans-8-2-to-now/ > > Thanks > From Peter > > From: Geertjan Wielenga > Sent: Wednesday, November 6, 2019 7:32 PM > To: dev > Subject: Re: Netbeans hangs in Mac since Netbeans 8.2 to now > > Your subject line should be "My plugin hangs in Mac since NetBeans IDE > 8.2.". > > And then you would point to the sources and to the steps to reproduce the > problem. > > Gj > > On Wed, Nov 6, 2019 at 3:23 AM Carl Mosca wrote: > > > Where can we get additional details? Perhaps I missed something in the > > post. > > > > Regards, > > Carl > > > > On Tue, Nov 5, 2019 at 9:19 PM Peter Cheung > wrote: > > > > > Hi All > > >Netbeans hangs in Mac since Netbeans 8.2 to now. > > > > > > https://peter.quantr.hk/2019/11/netbeans-hangs-in-mac-since-netbeans-8-2-to-now/ > > > thanks > > > Peter > > > > > > > > > -- > > Carl J. Mosca > > > -- Regards, Carl
Re: [DISCUSS] Handling release updates
There appear to be two issues that would be best to make available as updates as soon as we can -- relating to nb-javac and HTML parsing. What would be the problem with voting on the sources of those two modules and then making them available via the plugin portal? Gj On Mon, Nov 4, 2019 at 6:54 PM Eric Barboni wrote: > Hi, > Not sure what the needs exactly. > But If you rebuild a patched NetBeans with a forced version > RELEASE112-update1. You can pick the patched nbm you want. And alter pom to > put RELEASE112 for dep (you know are were not modified). > > Then vote with sources + the limited artefacts RELEASE112-update1 to be > able to release them in central > > Best Regards > Eric > > > > > -Message d'origine- > De : Neil C Smith > Envoyé : mardi 29 octobre 2019 18:42 > À : dev > Objet : Re: [DISCUSS] Handling release updates > > On Tue, 29 Oct 2019 at 15:53, Eric Barboni wrote: > > You cannot do a RELEASE112.1 in the > org.netbeans(api,modules,clusters,external) without rebuild the whole > NetBeans stack because every pom will need the RELEASE112.1 version on > dependencies nbm being a side artefacts. > > It's not possible to overwrite a released artefacts you cannot do a > RELEASE112 again. > > Yes, I know artefacts can't be overwritten, so thought as much. Kind of > makes it even harder to push a patch release for Maven modules. > Would be good if that was not the case, but I guess it's not a short term > (ie. 11.2 update) mechanism. And Maven probably won't get nb-javac module > fix, although that's probably not that much of an issue. > > Still think it worth considering longer term. Means only one set of NBMs > need signing and maintaining, and may remove some issues around using > Apache mirrors for the UCs. How feasible is changing the modules to use > spec version and RELEASE11X just for overarching POM files? > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-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: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: [NETBEANS-3346] Upgrade asm to 5.2+
On Wed, 6 Nov 2019 at 22:24, Jose Ch wrote:
>
> I will test the PR and do as you suggest Pete.
For what it's worth my implementation was a bit different:
private static class CtorDelVisitor extends AnnotationVisitor {
int[] indices;
/**
* Constructs a new {@link AnnotationVisitor}.
*
* @param api the ASM API version implemented by this visitor. Must
be one of {@link
* Opcodes#ASM4}, {@link Opcodes#ASM5}, {@link Opcodes#ASM6} or
{@link Opcodes#ASM7}.
*/
public CtorDelVisitor(int api) {
super(api);
}
@Override
public AnnotationVisitor visitArray(String name) {
if ("delegateParams".equals(name)) { // NOI18N
return new AnnotationVisitor(api) {
List list = new ArrayList<>();
@Override
public void visit(String name, Object value) {
list.add((Integer) value);
}
@Override
public void visitEnd() {
int[] indices = new int[list.size()];
for (int i = 0; i < indices.length; ++i) {
indices[i] = list.get(i);
}
CtorDelVisitor.this.indices = indices;
}
};
} else {
return super.visitArray(name); // Not interested
}
}
}
I guess Svata's will be more efficient.
It's a bit frustrating that the AnnotationNode forces us to visit each
array element in turn when all we need is the complete list, but I think
there's no way around that. Visitor pattern makes my head spin, it always
seems inside-out to me.
Pete
Re: NetBeans Design
On Thu, Nov 7, 2019 at 9:47 AM Jeremy Cavanagh wrote: > Hi Tim, > > That is most impressive, and yet terrifying at the same time. It raises > even more questions for me. How does anyone know where anything is? > > You've had several responses to that question already in this thread. The NetBeans source code is structured in functional areas -- called clusters, each cluster containing modules that together provide the features defining the cluster. E.g., the 'java' cluster provides all the modules defining the Java features, the 'php' cluster provides all the modules defining the PHP features. Take a look at the GitHub repo -- the clusters are the top level folders: https://github.com/apache/netbeans Gj > Probably not for discussion here but, what use is software engineering, > design methodologies etc., is software development just an enormous > hackathon? > > Food for thought. > > Many thanks to everyone who replied to my original post. > > Jeremy > > > On 07/11/2019 03:29, Tim Boudreau wrote: > > A few people asked for a visual representation. I pulled this together a > > few years ago. Mostly it just illustrates why those kinds of > > representations are useless at scale. > > > > Package dependencies: > > > > https://timboudreau.com/files/nb-packagegraph/ > > > > Classes (IIRC trimmed down a LOT): > > > > https://timboudreau.com/files/netbeans-classes/ > > > > On Wed, Nov 6, 2019 at 7:57 PM Eric Bresie wrote: > > > >> Is this a reason to push for the UML plugin ;-) > > > > > > There are no reasons to push for uml, ever :-) > > > > -Tim > > > > > > > >> > >> Eric Bresie > >> ebre...@gmail.com > >>> On November 6, 2019 at 9:02:49 AM CST, Eric Barboni > >> wrote: > >>> Hi, > >>> Not sure that is what you want. > >>> > >>> ((A small help can be > >>> If you get the sources, do a first build: > >>> ant > >>> you can then do > >>> ant index-layer-paths > >>> > >>> this will create in nbbuild/build/generated layers.txt and services.txt > >>> where given a " UI element" " mimetype" "project type" you can find > >> which module provide it (this is a bit too textual). > >>> )) > >>> > >>> Maybe you want a more complex visualization, with rectangle and edge > but > >> I guess should be some layout and "dynamic page" to filter ( or 8K > monitors > >> :p). Modules are legion. > >>> > >>> Best Regards > >>> Eric > >>> -Message d'origine- > >>> De : Christian Lenz > >>> Envoyé : mercredi 6 novembre 2019 15:43 > >>> À : dev@netbeans.apache.org > >>> Objet : AW: NetBeans Design > >>> > >>> ➢ And this IMHO continues to be the best book on the NetBeans Platform: > >>> > >>> ➢ https://leanpub.com/nbp4beginners > >>> > >>> ➢ Gj > >>> > >>> Hey Geertjan, > >>> > >>> how does that fit in the reworked/categorized structure. Is the book > >> still up to date? Just asking. > >>> > >>> > >>> Cheers > >>> > >>> Chris > >>> > >>> > >>> Von: Geertjan Wielenga > >>> Gesendet: Mittwoch, 6. November 2019 15:34 > >>> An: dev > >>> Betreff: Re: NetBeans Design > >>> > >>> On Wed, Nov 6, 2019 at 3:09 PM Christoph Theis wrote: > >>> > I have the same problem: > E.g., NB doesn't accept a current javahl. So, where would I find the > module where the check happened (I grep'ed for the error message and > found it). Are there dependencies? If I want to improve the error > message (right now it is hidden in the log files), how to do it? > > So, summarizing, an eagles view of what NB is composed of, would be a > start. Sthg., that would help newcomers to understand the code of NB. > > >>> > >>> > >>> In many ways, the current GitHub structure provides the eagle's view > you > >>> seek: > >>> > >>> https://github.com/apache/netbeans > >>> > >>> Rather than it being a long list of modules, the above categorizes them > >> into their clusters, reflecting what you see in your NetBeans > installation > >> directory. > >>> > >>> Indeed, grepping is a good approach to find the code you need to work > >> with. > >>> > >>> You can also search directly in the GitHub repo on-line in the web > >> interface. > >>> > >>> The dependencies of any modules are always listed in the project.xml > >> file of a module. > >>> > >>> And this IMHO continues to be the best book on the NetBeans Platform: > >>> > >>> https://leanpub.com/nbp4beginners > >>> > >>> Gj > >>> > >>> > >>> > >>> > >>> > > @Jeremy: I hope I got your point. > > > Best regards > > Christoph > > On 06.11.2019 14:24, Geertjan Wielenga wrote: > > What specific things are you looking for? > > > > Gj > > > > On Wed, 6 Nov 2019 at 14:05, Jeremy Cavanagh > > > > wrote: > > > >> Hi All, > >> > >> I was just wondering if there was a design document for NetBeans > >> which shows how all the pieces fit together? I ask this because > >> whenever I look at incubator-netbeans I have no idea of what I'm > >> looking at, or where to find things.
Re: Netbeans hangs in Mac since Netbeans 8.2 to now
Dear Sir Sorry my bad english, my plugins source is updated in. So if you install my plugin in your netbeans, i believe netbeans will hangs in after few starts. https://peter.quantr.hk/2019/11/netbeans-hangs-in-mac-since-netbeans-8-2-to-now/ Thanks >From Peter From: Geertjan Wielenga Sent: Wednesday, November 6, 2019 7:32 PM To: dev Subject: Re: Netbeans hangs in Mac since Netbeans 8.2 to now Your subject line should be "My plugin hangs in Mac since NetBeans IDE 8.2.". And then you would point to the sources and to the steps to reproduce the problem. Gj On Wed, Nov 6, 2019 at 3:23 AM Carl Mosca wrote: > Where can we get additional details? Perhaps I missed something in the > post. > > Regards, > Carl > > On Tue, Nov 5, 2019 at 9:19 PM Peter Cheung wrote: > > > Hi All > >Netbeans hangs in Mac since Netbeans 8.2 to now. > > > https://peter.quantr.hk/2019/11/netbeans-hangs-in-mac-since-netbeans-8-2-to-now/ > > thanks > > Peter > > > > > -- > Carl J. Mosca >
Re: NetBeans Design
Hi Tim, That is most impressive, and yet terrifying at the same time. It raises even more questions for me. How does anyone know where anything is? Probably not for discussion here but, what use is software engineering, design methodologies etc., is software development just an enormous hackathon? Food for thought. Many thanks to everyone who replied to my original post. Jeremy On 07/11/2019 03:29, Tim Boudreau wrote: A few people asked for a visual representation. I pulled this together a few years ago. Mostly it just illustrates why those kinds of representations are useless at scale. Package dependencies: https://timboudreau.com/files/nb-packagegraph/ Classes (IIRC trimmed down a LOT): https://timboudreau.com/files/netbeans-classes/ On Wed, Nov 6, 2019 at 7:57 PM Eric Bresie wrote: Is this a reason to push for the UML plugin ;-) There are no reasons to push for uml, ever :-) -Tim Eric Bresie ebre...@gmail.com On November 6, 2019 at 9:02:49 AM CST, Eric Barboni wrote: Hi, Not sure that is what you want. ((A small help can be If you get the sources, do a first build: ant you can then do ant index-layer-paths this will create in nbbuild/build/generated layers.txt and services.txt where given a " UI element" " mimetype" "project type" you can find which module provide it (this is a bit too textual). )) Maybe you want a more complex visualization, with rectangle and edge but I guess should be some layout and "dynamic page" to filter ( or 8K monitors :p). Modules are legion. Best Regards Eric -Message d'origine- De : Christian Lenz Envoyé : mercredi 6 novembre 2019 15:43 À : dev@netbeans.apache.org Objet : AW: NetBeans Design ➢ And this IMHO continues to be the best book on the NetBeans Platform: ➢ https://leanpub.com/nbp4beginners ➢ Gj Hey Geertjan, how does that fit in the reworked/categorized structure. Is the book still up to date? Just asking. Cheers Chris Von: Geertjan Wielenga Gesendet: Mittwoch, 6. November 2019 15:34 An: dev Betreff: Re: NetBeans Design On Wed, Nov 6, 2019 at 3:09 PM Christoph Theis wrote: I have the same problem: E.g., NB doesn't accept a current javahl. So, where would I find the module where the check happened (I grep'ed for the error message and found it). Are there dependencies? If I want to improve the error message (right now it is hidden in the log files), how to do it? So, summarizing, an eagles view of what NB is composed of, would be a start. Sthg., that would help newcomers to understand the code of NB. In many ways, the current GitHub structure provides the eagle's view you seek: https://github.com/apache/netbeans Rather than it being a long list of modules, the above categorizes them into their clusters, reflecting what you see in your NetBeans installation directory. Indeed, grepping is a good approach to find the code you need to work with. You can also search directly in the GitHub repo on-line in the web interface. The dependencies of any modules are always listed in the project.xml file of a module. And this IMHO continues to be the best book on the NetBeans Platform: https://leanpub.com/nbp4beginners Gj @Jeremy: I hope I got your point. Best regards Christoph On 06.11.2019 14:24, Geertjan Wielenga wrote: What specific things are you looking for? Gj On Wed, 6 Nov 2019 at 14:05, Jeremy Cavanagh wrote: Hi All, I was just wondering if there was a design document for NetBeans which shows how all the pieces fit together? I ask this because whenever I look at incubator-netbeans I have no idea of what I'm looking at, or where to find things. I really hope there is, particularly if it includes structure diagrams etc. Regards Jeremy - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-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: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-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: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
