Re: [VOTE] Release Apache NetBeans 11.2-u1 update

+1: Successfully passed all steps and runs well. Thanks for your time and effort! Josh Juneau juneau...@gmail.com http://jj-blogger.blogspot.com https://www.apress.com/us/search?query=Juneau On Wed, Nov 27, 2019 at 9:21 AM Neil C Sm

Re: release verification/validation practices

On Thu, 28 Nov 2019, 23:52 Ernie Rael, wrote: > There might be something with simpler output. > Do check the page at https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README That covers both the signing process and some of the checks. I'm less sure what the best comma

Re: release verification/validation practices

The .asc check should look like for i in $(find nbms -name '*.asc'); do echo === $i; gpg2 --verify $i ${i%.asc};done There might be something with simpler output. -ernie On 11/28/2019 3:29 PM, Ernie Rael wrote: Going through the verification steps for 11.2-u1, I first downloaded the sou

release verification/validation practices

Going through the verification steps for 11.2-u1, I first downloaded the source (with a browser), built, tested. Then saw request to check convenience NBMs. I downloaded a set of nbm/asc/sha512 and discovered that sha512sum wanted to run from the parent of the nbms directory. I wanted to fetch

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Hi Ken, I think your input is needed on these legal-discuss threads: https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201911.mbox/%3C4169588f-731b-df79-de80-d6640a9e9fa8%40gmail.com%3E https://mail-archives.apache.org/mod_mbox/www-legal-discuss/201911.mbox/%3CCEB62E1B-B884-4DD3-92BA-5A9

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Does this work: https://github.com/OpenBeans/NetBeans/releases/tag/11.2 ? --emi On Thu, Nov 28, 2019 at 11:11 PM Geertjan Wielenga wrote: > > Sure, I don’t see why not. The question is (1) who will make it, (2) what > will its name and brand be, (3) which JDK will be included, (4) who will > pr

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Sure, I don’t see why not. The question is (1) who will make it, (2) what will its name and brand be, (3) which JDK will be included, (4) who will provide active support when things go wrong. Gj On Thu, 28 Nov 2019 at 21:44, Ernie Rael wrote: > Is it possible, and legal, to put an install bund

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Is it possible, and legal, to put an install bundle on github and point to it? -ernie On 11/28/2019 9:23 AM, Geertjan Wielenga wrote: Just note that nb-javac won’t be with us forever, work is being done to remove our need for it. Once that is done, we’ll be in a really good state. In the mean

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

It's not clear to me who would be putting together this bundle. The apache NB team or Adopt? -ernie On 11/28/2019 8:56 AM, Geertjan Wielenga wrote: If we have AdoptOpenJDK officially providing a bundle together with NetBeans, then I think we should consider not providing an installer at all —

Re: Issue with Gradle projects - requires manual delete of .nb-gradle folder

Yes, I know it can be hard to track down. Is there something I can do to collect useful information if it happens again? Scott > On Nov 28, 2019, at 3:14 PM, Laszlo Kishalmi > wrote: > > Issues like these are really hard to tackle. Most likely some cache files > got corrupted. > > FYI the d

Re: Issue with Gradle projects - requires manual delete of .nb-gradle folder

Issues like these are really hard to tackle. Most likely some cache files got corrupted. FYI the default Gradle implementation does not use .nb-gradle folder we put our cached things under .gradle. BTW deleting .gradle directory is safe you just removed the corrupted cached content. On 11/

Issue with Gradle projects - requires manual delete of .nb-gradle folder

[Testing with 11.2-u1 nbms installed from the binaries recently posted...] Many imports in the project source are erroneously showing errors like this: cannot access NativeComponent bad class file: NativeComponent.class illegal start of class file Please remove or make sure it appears i

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Hey Kirk, Well, on this side we’re ready to move forward, just tell us what we need to do to proceed. Looking forward to this happening, Gj On Thu, 28 Nov 2019 at 18:43, Kirk Pepperdine wrote: > Hi Geertjan, > > I can’t personally speak for adopt but my understanding from previous > conversat

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Hi Geertjan, I can’t personally speak for adopt but my understanding from previous conversation was Adopt was amicable to this. I think the only issue is man power to get it done. Kind regards, Kirk > On Nov 28, 2019, at 8:56 AM, Geertjan Wielenga wrote: > > If we have AdoptOpenJDK official

Re: [DISCUSS] What to do with old community contributed plugins?

Excellent! Gj On Thu, 28 Nov 2019 at 18:22, Emilian Bold wrote: > I have downloaded that Plugin Portal data (which includes the NBMs and > catalog.xml) and am serving all the files from another server. I seem > to be able to register it in the IDE. Looking good. > > Once I get some confirmation

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Just note that nb-javac won’t be with us forever, work is being done to remove our need for it. Once that is done, we’ll be in a really good state. In the meantime, as well as atter that, we should do everything we can to work with Kirk and anyone else to provide a bundle of their JDK with NetBean

Re: [DISCUSS] What to do with old community contributed plugins?

I have downloaded that Plugin Portal data (which includes the NBMs and catalog.xml) and am serving all the files from another server. I seem to be able to register it in the IDE. Looking good. Once I get some confirmations I can make the URL public. --emi On Thu, Nov 21, 2019 at 10:12 PM Jiří Ko

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Just adding some info: It is not just about the JDK, but JDK, nb-javac and probably a fitting JavaFX runtime. If someone can bundle those up and provide an installer most probably based on the installer code we have, then that would be the best end user experience, like in the old days when

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

On Thu, 28 Nov 2019 at 16:52, Geertjan Wielenga wrote: > .. Neil, make their own > JDK+NetBeans available, That wasn't what I was referring to above. I was looking at how easy it would be to make an InnoSetup installer that included the ability to select and download a JDK. To do all that, we w

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

If we have AdoptOpenJDK officially providing a bundle together with NetBeans, then I think we should consider not providing an installer at all — and just make the convenience binary available as a ZIP and point to AdoptOpenJDK and OpenBeans and any other bundlers/distributors. Gj On Thu, 28 No

Re: [VOTE] Release Apache NetBeans nb-repository-plugin version 1.5

+1 - mvn clean install without issues Josh Juneau juneau...@gmail.com http://jj-blogger.blogspot.com https://www.apress.com/us/search?query=Juneau On Wed, Nov 27, 2019 at 5:02 AM Eric Barboni wrote: > Dear members of Apache NetBean

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Excellent news, Kirk. How do we get this done? Gj On Thu, 28 Nov 2019 at 17:49, Kirk Pepperdine wrote: > Hi all, > > Again, I believe that you could distribute from Adopt with a JDK bundled. > So maybe this is a case where using a 3rd party makes sense. > > Kind regards, > Kirk > > > > On Nov

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

That’s what we’re trying to achieve, though it looks unlikely that we’ll win this one. And in some ways it is better that we are not and cannot bundle the JDK because then the question would be “which JDK” and the answer is not so obvious — it would have more impact for AdoptOpenJDK to provide its

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Hi all, Again, I believe that you could distribute from Adopt with a JDK bundled. So maybe this is a case where using a 3rd party makes sense. Kind regards, Kirk > On Nov 28, 2019, at 8:45 AM, Kenneth Fogel wrote: > > I apologize if I misunderstood but the conversation appeared to me, likely

RE: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

I apologize if I misunderstood but the conversation appeared to me, likely incorrectly, to go beyond just bundling a Java JDK. The installers that are already there, are they downloading a JDK if one is not present? Requiring a separate install of Java is the status quo. If we could make that pa

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

On Thu, 28 Nov 2019, 16:20 Kenneth Fogel, wrote: > > It is unfortunates, as someone has pointed out, that Apache is not end > user friendly but that is no excuse. NetBeans is an end user program and > must be as easy to install as any other IDE and have an official installer. > What happens if t

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

You’re aware that we’re already distributing an installer, right? And that that is not what we’re talking about? We’re talking about the fact that we can’t bundle the JDK with that installer and then distribute that installer from Apache. A simple link on our download page to OpenBeans and AdoptO

RE: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

This is a bad idea. I personally feel that an installer is mandatory. Eclipse and IntelliJ have installers for all platforms. Leaving it to third parties will mean that we have no oversight on the quality and ease of use of the installer. Only distributing a zip file implies that skills beyond l

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Awesome! How can we support this? Gj On Thu, 28 Nov 2019 at 16:06, Kirk Pepperdine wrote: > Hi, > > I believe adopt would very much like to host a NB download. > > Kirk > > On Wed, Nov 27, 2019 at 22:03 Emilian Bold wrote: > > > Apache rules do not go well with end user applications such as Ne

Re: Travis is failing on building hibernateweb

I noticed that as well.. On Thu, Nov 28, 2019 at 2:09 AM Matthias Bläsing wrote: > That is an old problem and the build works with it. Yesterday the htmlui > tests began to fail on Travis. Maybe the Xvfb server does not work? > > > Am 28. November 2019 09:11:28 MEZ schrieb Laszlo Kishalmi < > l

Re: [DISCUSS] Dropping Installers from the Release Process leave that work to Third Party Distributors

Hi, I believe adopt would very much like to host a NB download. Kirk On Wed, Nov 27, 2019 at 22:03 Emilian Bold wrote: > Apache rules do not go well with end user applications such as NetBeans > IDE. > > The binary zip could be used as a baseline for building the installers > and this fact its

Re: Error when building from current git

On Wed, 27 Nov 2019 at 14:31, Laszlo Kishalmi wrote: > Actually I've seen that when I added the dark LAF to the build. > > But master builds fine for Travis and for me as well. > > I don't know what caused the problem but I have done an `ant clean` and then `ant build` which was successful. Than

Re: [VOTE] Release Apache NetBeans 11.2-u1 update

On Thu, 28 Nov 2019 at 01:54, Ernie Rael wrote: > OFF TOPIC Please start a separate thread for discussion rather than using the voting thread - although, please do, I think it's worth looking into! > to fetch the individual artifacts. I expected to see only the nbms > directory. I was surprised

Re: Travis is failing on building hibernateweb

That is an old problem and the build works with it. Yesterday the htmlui tests began to fail on Travis. Maybe the Xvfb server does not work? Am 28. November 2019 09:11:28 MEZ schrieb Laszlo Kishalmi : >I see this one in the recent logs: > >Cannot find build prerequisite org.netbeans.modules.hi

Travis is failing on building hibernateweb

I see this one in the recent logs: Cannot find build prerequisite org.netbeans.modules.hibernate of /home/travis/build/apache/netbeans/contrib/hibernateweb /home/travis/build/apache/netbeans/nbbuild/netbeans