Re: Resolving GPLv2-CPE categorization as Category X (was: Re: Still Plugging Away on Java EE Support)

On Thu, 16 May 2019 at 20:18, Matthias Bläsing wrote: > The points raised in the referenced issue target the CPE. And the CPE > is started with "Certain source files distributed by Oracle America > and/or its affiliates[...]". So yes, this is Oracle specific and Oracle > lawyers could give their

Re: [DISCUSS] Draft release schedule

On Fri, 17 May 2019, 19:02 Geertjan Wielenga, wrote: > We’re a friendly community and I imagine happy to unwind decisions if > needed. > Absolutely! Only a few things feel difficult to unwind, because they'll be public, like if at 11.1 release we advertise 11.0 as the first LTS. But time

Re: [DISCUSS] Draft release schedule

Hi, Quick bump, just to see if there are any further thoughts on this? If there aren't objections I'd really like to run a vote thread on this next week - not the whole text - lots still to discuss - just key points around release dates, LTS, version numbering and feature/master freeze.

Re: [DISCUSS] Draft release schedule

On Fri, 17 May 2019 at 17:14, Geertjan Wielenga wrote: > > I'd recommend using lazy consensus rather than voting. I think it's great > and you should go ahead. I'm happy with that too if you prefer. Shall we vote on it? :-) So, let's turn this into a prod to raise concerns in the next week

Re: Users banned from apache.org due to downloading updates.xml.gz

On Fri, 17 May 2019, 20:24 Antonio, wrote: > What they suggest is to try to find a closest mirror for the first > module (using closer.lua) and then keep on using that mirror directly > for the rest of modules (even if we redirect through n.a.o for each of > them to keep track of downloads). >

Re: Users banned from apache.org due to downloading updates.xml.gz

On Fri, 17 May 2019 at 21:04, Antonio wrote: > Downloading updates.xml.gz from n.a.o and the rest of NBMs through n.a.o > > netbeans-vm.a.o > closer.lua should be easy. I meant the bit where you mentioned getting the mirror for the first module and then downloading the rest directly from that

Re: Users banned from apache.org due to downloading updates.xml.gz

On Fri, 17 May 2019, 20:32 Antonio, wrote: > Forgot to mention that they recommend the updates.xml.gz _NOT_ being > downloaded through closer.lua. > > I don't know if Jiri wants to keep track of statistics on this file, > though. > Well, my assumption from the other thread was that it was

Re: [DISCUSS] Draft release schedule

On Fri, 17 May 2019 at 20:35, Jan Lahoda wrote: > I'd like to ask: is there a plan for a "next" branch to which one could > merge stuff for the next release while the master is closed (and which > would be automatically merged into master when the merge window would > open)? As master is going to

Re: 11.1 info publicly available

On Tue, 4 Jun 2019 at 11:49, Geertjan Wielenga wrote: > > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule > > That's it, that's what I'll be linking into netbeans.apache.org. Yep, that's it! As for your other question, there's a NB 11.1 label in GitHub - this was already

Re: 11.1 info publicly available

On Tue, 4 Jun 2019, 12:01 Geertjan Wielenga, wrote: > Also, I believe the mentions of 12.1 should be removed here, i.e., in the > Release column in the table, there should now only be 11.x, if I'm right? > Why? The idea was to demonstrate how the same schedule could work from year to year.

Re: Schedule of 11.1 release was: 11.1 info publicly available

Hi, On Wed, 5 Jun 2019 at 08:39, Jaroslav Tulach wrote: > Hello Neil, > what is the schedule of 11.1 release? Feature freeze June 15th. Release ~15th July. > When the release branch is going to > be created? There will be a release branch made as soon as possible after June 15th. BUT,

Re: Schedule of 11.1 release was: 11.1 info publicly available

On Wed, 5 Jun 2019, 12:59 Jaroslav Tulach, wrote: > I see. The release will happen from a master branch. Thanks. > Effectively, yes. There will still be a release branch but merging all commits in master. A few people suggested releasing non-LTS off a master tag but not sure we're there yet

Re: Installers -- making them official for 11.1?

On Thu, 30 May 2019, 18:47 Kodewerk, wrote: > For example, I believe we can’t call the distro Apache-NetBeans so we’re > thinking of calling it Adopt-NetBeans. > While l wouldn't want to stop use of Adopt NetBeans, because it sounds great, I'm not sure you can't use Apache NetBeans. If I recall

Re: Installers -- making them official for 11.1?

On Fri, 31 May 2019, 09:21 Geertjan Wielenga, wrote: > I believe so, but cannot confirm with 100% certainty. > Is there ever 100% certainty?! :-) The first example of nominative fair use here appears to cover exactly this though? https://www.apache.org/foundation/marks/#guidelines I assume

Re: Installers -- making them official for 11.1?

On Thu, 30 May 2019, 23:02 Kodewerk, wrote: > I would personally prefer Apache-NetBeans… but I’ve been told that we > needed to rebrand. > Well, this is the thread I'm thinking of -

Re: Unsuccessful NB Run after a successful build on Windows.

On Thu, 13 Jun 2019 at 20:18, Geertjan Wielenga wrote: > > But all these things are true whether you build NetBeans yourself or > whether you run NetBeans after downloading and running the binary from the > Download page, right? I mean, if you can't connect to an update center to > get nb-javac

Re: JIRA permissions / releases?

On Fri, 14 Jun 2019 at 16:00, Geertjan Wielenga wrote: > > Refresh the page, you should see 11.1 and 11.2 now. Thanks! - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail:

Re: NB11.1 spec version increment?

On Fri, 14 Jun 2019 at 16:39, Laszlo Kishalmi wrote: > > Am I right in thinking you linked directly to the build artefacts > > rather than staging the testing releases? > Yes, for 11.0. Since we didn't have an announced beta/rc/vc releases it > seemed to be easier. Thanks. Yes, have since found

Re: JIRA permissions / releases?

On Fri, 14 Jun 2019 at 16:06, Geertjan Wielenga wrote: > > I've also found the place where to give you admin permissions and have > given them, so when you refresh or maybe log in/out, you should be able to > create those release tags and edit the existing ones yourself. Great, thanks, I see it

JIRA permissions / releases?

Hi, I'd like to set up release tags for 11.1 and 11.2 in JIRA. Am I missing where to add this, or just missing the relevant permissions? Thanks, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For

NB11.1 inbound - what is NetCAT lite?

Hi, So, it's feature-freeze day for NB11.1 tomorrow*. That came around quick! I've blocked out some time early next week for branching and rolling a first beta - I'll get it up as soon as I can, but bear with me if I get stuck on a couple of things as I get my head around the process! Now, one

Re: JIRA permissions / releases?

On Fri, 14 Jun 2019 at 15:54, Geertjan Wielenga wrote: > > I can do it here, I think: > > https://issues.apache.org/jira/projects/NETBEANS?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page > > Can you? Not that I can see - that's the page I was looking for it on. Neil

AutoUpdate and Installer hard-coded versions?!

Hi, I've cloned the release task list for 11.0 to 11.1 and started revising what needs to be done. Ideally given our faster release schedule it would be good to move to everything being configurable in the build. I'm intrigued why we need to keep hard coding release versions in the AutoUpdate

Re: Updating the website for the new release

On Fri, 14 Jun 2019 at 20:11, Geertjan Wielenga wrote: > > One thing we need is the complete list of PRs that are new in 11.1. From > that, we can pick the items that are most significant etc. > > Is there a way to get such a list? Something like

Re: AutoUpdate and Installer hard-coded versions?!

On Fri, 14 Jun 2019 at 17:47, Geertjan Wielenga wrote: > > There's reasons for that. Jirka will explain, I confess I keep > forgetting/not completely understanding this part. Well, I assumed there was. :-) I've made a PR adding 11.0 here - https://github.com/apache/netbeans/pull/1302 It's

Re: Apache NetBeans 11.1-beta1 Is Available for Testing!

On Tue, 18 Jun 2019 at 15:29, Sven Reimers wrote: > I activated all plugins, got some follow up install messages, once Java > plugins was active nb-javac installation was triggered... > > After all was over I saw this: ... >

Re: Installers for 11.1 release

On Tue, 18 Jun 2019 at 14:56, wrote: > On 18/06/19 5:40 PM, Neil C Smith wrote: > > On Mon, 17 Jun 2019 at 13:32, wrote: > >> I have created build job [1] for generating installers for Windows > >> and Linux. Mac installer needs to be built locally. >

Re: NB11.1 Feature Freeze - master branch closed except for fixes!

On Mon, 17 Jun 2019 at 19:37, Geertjan Wielenga wrote: > > So where should that PR 1301 go, i.e., I guess, it should not be merged at > all unless it should go into 11.1? Ideally, no, particularly because it's intended for 11.2 anyway. In general, it depends where the urge to merge comes from.

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

Hi All, OK, looks like we have consensus on merging these then. I will merge to master on Monday, unless someone else does before, and then sync everything across to release111 for our next beta. My inclination is to squash and merge these unless anyone has a reason not to before then? Thanks

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

On Sat, 22 Jun 2019 at 17:41, Geertjan Wielenga wrote: > > One thing — how can the betas and final release be distinguished from each > other? Right now we have beta-1, soon beta-2, eventually final release, but > one day when someone reports an issue how will we know which one they’re > using?

Re: Request for Cherry-picking for NB-11.1(https://github.com/apache/netbeans/pull/1323)

On Tue, 25 Jun 2019, 16:58 Arunava Sinha, wrote: > Wants to check with you the possibility of cherry-picking the below PR. > There is no cherry picking as such. Master will be merged into the release branch tomorrow morning for the second beta. If this is reviewed and merged before then it'll

NB11.1 Feature Freeze - master branch closed except for fixes!

Hi All, Just a reminder that the feature freeze deadline for NB 11.1 was on Saturday. The release branch was made earlier today, and the branding / config changes made - first beta should be ready tomorrow. The only merges to master between now and release date should be intended for NB11.1

Re: Apache NetBeans 11.1-beta1 Is Available for Testing!

On Wed, 19 Jun 2019 at 14:17, Sven Reimers wrote: > > For the activation, > > - open plugins dialog > - select installed tab. > - check all checkboxes > - press activate button. Thanks, that triggers it for me too - so looks like it's installing from the notification bubble? Out of interest,

Merging of PRs for 11.1 and 11.2

Hi All, We're obviously still getting our heads around how the new release process will work in practice, and one thing we still need to firm up is how to handle tagging and merging PRs to master outside of the merge windows. I'd like to propose the following for NB 11.1, to be reviewed after

[Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

Hi All, This email follows some off-list discussion with various people including Geertjan and the relevant contributors. The release schedule we agreed has an open question about allowing selective feature freeze bypass based on mailing list agreement - hence ... I propose we allow the pending

Re: Files to License List

On Thu, 20 Jun 2019 at 15:15, Glenn Holmer wrote: > > On 6/19/19 12:35 PM, Geertjan Wielenga wrote: > > It means those Oracle apps are built on top of NetBeans and the devs from > > Oracle Labs are about to move to the latest Apache NetBeans release. In > > short, “import”, in a way. > >

Re: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

On Sat, 22 Jun 2019 at 17:32, Neil C Smith wrote: > My inclination is to squash and merge these unless anyone has a reason > not to before then? I've squashed and merged two. https://github.com/apache/netbeans/pull/1290 now has a merge conflict. Seems a simple and obvious reason, but b

NB11.1 spec version increment?

Hi, I'm just doing some checking up on the release process and wondering how we want to handle incrementing spec versions with the revised release plan? With NB11.0 as far as I can tell, the release branch was made, the spec version in the branch was incremented immediately (with -branch) and

Apache NetBeans 11.1-beta1 Is Available for Testing!

Dear Community, I'd like to announce that the first beta build for Apache NetBeans 11.1 from the release111 branch is available for download. As this build is for testing purposes only, we are not going to do the release dance and voting around it (and as we're not voting on it, the files are

Re: Installers for 11.1 release

On Mon, 17 Jun 2019 at 13:32, wrote: > I have created build job [1] for generating installers for Windows > and Linux. Mac installer needs to be built locally. Can you confirm the reasons and requirements for the local Mac build? > This build job currently points to zip generated from a

Re: PR-1245 Splash Screens and About Dialogs

On Sat, 11 May 2019 at 09:29, Antonio wrote: > As discussed in the splash screen thread and NETBEANS-2455 [1], I > submitted PR-1245 [2] based on the ASF Identity Guide and the > contributions by J. Gosling and others. Thank you all for the contributions! ... > I've uploaded a new binary with a

[DISCUSS] Draft release schedule

Hi, As part of taking on release managing the next release, I said I'd like to try and tie up the various things people have suggested around quarterly / time-based releases into one plan. I admit to having some reluctance volunteering for that role while there were still discussions around how

Re: [DISCUSS] Draft release schedule

On Mon, 13 May 2019 at 19:11, Glenn Holmer wrote: > NetCAT test specs should be reviewed *between releases* to have any hope > of completing the testing in a timely manner. What is the overall plan > for NetCAT? Does it need to change and adapt now that we are at Apache? > Does Synergy work the

Re: Users banned from apache.org due to downloading updates.xml.gz

On Wed, 15 May 2019 at 02:50, Wade Chandler wrote: > On Tue, May 14, 2019, 11:04 Bertrand Delacretaz > wrote: > > I'm not sure if http://netbeans-vm.apache.org/uc/11.0/updates.xml.gz > > is reliable enough to be used for that, a CDN seems more appropriate. ... > Indeed, and I assume if everyone

Re: NBM Signing...

On Thu, 23 May 2019 at 19:06, Laszlo Kishalmi wrote: > What do we know about the NBM signing inside of Apache? Tangentially related I know, but I've wondered whether we should also have a file hash in the catalog and validate that as well? And of course, longer term we'll also have reproducible

Re: [DISCUSS] Draft release schedule

On Fri, 17 May 2019 at 19:51, Laszlo Kishalmi wrote: > > It might be my bad, and a long night night work on DNS troubles, but it > took me a while to get around the first column of the table. At the I > could figure it out, I'd just order it by the second column as ho we see > the dates in a

Re: Request for Help : Java Hint to enable Preview feature in gradle project

On Mon, 20 May 2019 at 11:12, Geertjan Wielenga wrote: > Maybe read “enable-preview” as a fallback in netbeans.conf? I.e., if not > set anywhere else, check in netbeans.conf for -J-Denable-preview and, if > present, apply to all Java projects, which would include Gradle projects? If you really

Release process - update center configuration problem?

Hi, As part of preparing for the next release (or more accurately, preparing me for it!) I'm looking through https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README and will make some edits soon (eg. removing incubating where necessary) In #7 we have the following two

Re: Still Plugging Away on Java EE Support

On Thu, 16 May 2019 at 17:53, Matthias Bläsing wrote: > Even better, Oracle would be in the > position to change the wording of the license if necessary and they are > the only ones, that could do it. Actually, they can't - and I'm going on the basis that they're not going to write a completely

Re: [DISCUSS] Draft release schedule

On Tue, 14 May 2019 at 13:04, Jiří Kovalský wrote: > thanks a lot for taking the time and putting this plan together! Thanks! > I like the LTS idea of annual feature releases in April with > full-fledged NetCAT programs. I assume that only these LTS releases > would have Update Centers,

Re: Users banned from apache.org due to downloading updates.xml.gz

On Tue, 14 May 2019 at 16:04, Bertrand Delacretaz wrote: > I'm not sure if http://netbeans-vm.apache.org/uc/11.0/updates.xml.gz > is reliable enough to be used for that, Well, it's currently more reliable than the alternative which fails every time due to the relative links. However, I've just

Re: Users banned from apache.org due to downloading updates.xml.gz

Hi, On Tue, 14 May 2019 at 14:55, Bertrand Delacretaz wrote: > It might be worth discussing with infra how to avoid this - my > understanding (to be verified) is that it's the amount of requests to > closer.lua that's problematic, even if the download themselves go to > download mirrors. I

Ant build of NetBeans RCP with --release

Hi All, I'm currently working on updating PraxisLIVE to use NB11 as a base. I was looking at making it possible (not for releases for now) to compile on JDK11 using the --release flag. At the moment I've just added that in as an attribute for the javac task in the harness common.xml Might be a

Re: Ant build of NetBeans RCP with --release

On Tue, 30 Apr 2019 at 18:37, Neil C Smith wrote: > So, the problem is that this works fine from the command line, but > fails from the IDE with the message "error: release version 8 not > supported". JFTR it looks like any use of the javac Ant task with the release att

Re: git repo - NB10?

On Wed, 1 May 2019 at 18:51, Mike Ryan wrote: > > I checked out master here https://github.com/apache/netbeans > > But when I run it the splash screen is saying NetBeans 10. Is that > expected? I want to be checking out NB 11. Am I using the wrong repo? No. Try checking out the release110

Re: Volunteer Release Manager(s) Needed for Apache NetBeans 11.1

Hi, On Sat, 4 May 2019 at 07:10, Laszlo Kishalmi wrote: > Probably we shall agree on how would we imagine the 11.1 release. OK, following up on other thread email, and a little off-list cajoling! ;-) I'd happily volunteer to take this on, but I'd like to do as described in the other thread

Re: [DISCUSS] import Bugzilla to Jira or Plan to Drop Bugzilla

On Sat, 20 Apr 2019, 02:37 Geertjan Wielenga, wrote: > My understanding is Oracle NetBeans bugzilla is being kept in readonly > state. That’s how e.g., Reema, is using and needing it. > IIRC we were told a while back that hosting a read-only (or even read-write) bugzilla on Apache

Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

On Sun, 28 Apr 2019, 07:44 Matthias Bläsing, wrote: > > at some point in the past we said, that we wanted to do time based > releases and I would still follow that thinking. > > I would branch any release of master, as late as possible, (not some > random other base), do testing and only minimal

Re: What will be in 11.1/12?

Hi, On Sun, 5 May 2019 at 16:32, Geertjan Wielenga wrote: > Regardless of who becomes the next release manager, can we get an easy view > into which pull requests will be part of the release? IMO, if we're doing this June release we should be freezing master at the end of May and releasing

Re: 11.1 beta-3 status

On Tue, 2 Jul 2019 at 23:00, Geertjan Wielenga wrote: > > PS: Sorry, wasn't aware you requested to be added as reviewer to the nb11.1 > tagged PRs, would have done so if I had known, can still do so, if you > like. I think everything tagged as nb11.1 is really important to include in > 11.1, have

Re: 11.1 -- separate convenience binary for frontend development?

On Wed, 3 Jul 2019 at 10:13, Geertjan Wielenga wrote: > What do we need to do this and do we think this is doable for 11.1? No! Well, we only release sources! :-) So while additional convenience binaries might be a good thing, and feasible post-release, given our inability to ship with a JDK

Re: 11.1 -- separate convenience binary for frontend development?

On Wed, 3 Jul 2019 at 10:20, Geertjan Wielenga wrote: > > Well, we already do produce a convenience binary. This would just be an > additional one. We can add steps to the build task, yes. What I mean is, we could do this after the vote - we could theoretically do it for 11.0 even now too. But

Re: 11.1 beta-3 status

On Wed, 3 Jul 2019 at 10:13, Neil C Smith wrote: > Looking through and merging now. OK, all bar two merged to master, and relevant JIRA issues marked resolved. The two pending are - https://github.com/apache/netbeans/pull/1285 https://github.com/apache/netbeans/pull/1338 The first is st

Re: 11.1 beta-3 status

On Wed, 3 Jul 2019 at 11:30, Geertjan Wielenga wrote: > I think both those two PRs you list can be merged at this point — and > rolled back if needed prior to the vc which (I believe) is the next one > after beta-3. Both are merged. Although I preferred to wait for Travis to go green, which it

Re: 11.1 beta-3 status

On Tue, 2 Jul 2019 at 23:01, Laszlo Kishalmi wrote: > I'm sorry, my bad (as I had a free weekend to form a few PR-s). Not a bad! :-) Looking through and merging now. Unfortunately, having been away since last beta, I'm somewhat behind on merging for this one - no travels between now and

Re: Apache NetBeans 11.1-beta3 Is Available for Testing!

On Thu, 4 Jul 2019 at 15:06, Alessandro wrote: > I found and reported NETBEANS-2801 > IllegalSateException > thrown when installing nbjavac plugin with OpenJDK11 Thanks! This is duplicated a lot across every release we've had, although

Re: 11.1 beta-3 status

On Wed, 3 Jul 2019 at 12:44, Geertjan Wielenga wrote: > Agreed, and all by or approved by jlahoda, so as safe as can be. My thoughts exactly! :-) Created the sync PR - https://github.com/apache/netbeans/pull/1353 Full list of changes from beta2 to beta3 there. Hopefully nothing missing! Time

Re: 11.1 beta-3 status

On Wed, 3 Jul 2019 at 13:00, Eric Barboni wrote: > Is it possible to consider this one for 11.1. As the ecosystem of maven > plugins/archetype is now ready. This may help. > Should I tag the PR ? > > https://github.com/apache/netbeans/pull/1324 OK, looking now. Missed it because the NB11.1

Re: 11.1 beta-3 status

On Wed, 3 Jul 2019 at 13:03, Neil C Smith wrote: > > On Wed, 3 Jul 2019 at 13:00, Eric Barboni wrote: > > Is it possible to consider this one for 11.1. As the ecosystem of maven > > plugins/archetype is now ready. This may help. > > Should I tag the PR ? > >

Re: 11.1 beta-3 status

On pending PRs the following look like possible NB11.1 candidates although are not marked as such - any thoughts? https://github.com/apache/netbeans/pull/1325 https://github.com/apache/netbeans/pull/1342 https://github.com/apache/netbeans/pull/1352 Best wishes, Neil

Re: Apache NetBeans 11.1-beta3 Is Available for Testing!

On Fri, 5 Jul 2019 at 08:39, Alessandro wrote: > my bad I haven't looked if it was already reported. I have resolved my > issue as duplicate. Thanks and no problem! Filed a couple of duplicates myself already this week. Have I mentioned how much I dislike JIRA again recently?! :-) Best

Re: Beta 3 installers : Re: Apache NetBeans 11.1-beta3 Is Available for Testing!

On Fri, 5 Jul 2019 at 11:10, joe schmo wrote: > Is there a zip file with 11.1 beta3? I'd rather that then an installer. Yes, in the original announcement thread. Best wishes, Neil - To unsubscribe, e-mail:

Re: Maven repo for Apache NetBeans

On Wed, 26 Jun 2019 at 10:52, Geertjan Wielenga wrote: > > There is no 110 there, e.g.: > > http://137.254.56.27/nexus/content/groups/netbeans/org/netbeans/modules/org-netbeans-bootstrap/ It's here though https://search.maven.org/artifact/org.netbeans.cluster/platform/RELEASE110/pom so should be

Travis failures?

Hi, Seems we're getting a lot of Travis failures at the moment. There were some commits changing travis config in master the other day, which doesn't seem great timing, but I'm not sure that's the reason. A few messages suggesting failures with osuosl downloads? Somewhat playing havoc with

Re: nb-javac and Oracle JS Parser on Maven Central

On Wed, 26 Jun 2019, 08:21 Geertjan Wielenga, wrote: > I.e., these would not be sources but NBM binary files > Why not the source bundles as well? Sources for both these should be available according to their licenses, and currently at least nb-javac could do with clearer information on what

Re: Travis failures?

On Wed, 26 Jun 2019 at 11:59, Geertjan Wielenga wrote: > > Since it’s a beta release, I wouldn’t let Travis stop you, especially if we > can identify the problem to fix post beta-2. OK, I'll merge the Payara Server PR at least then. Not ideal, but it was passing until the last commit to merge

Re: Travis failures?

On Wed, 26 Jun 2019 at 16:47, Gaurav Gupta wrote: > > Thanks Neil, I am looking at the attributes conflicts. Great, thanks. There also seems to be a versioning issue (possibly with a plugin elsewhere?) so the IDE wants to update your plugin immediately. Need to check if that happens when beta2

Re: Beta 2 Installers - Re: Apache NetBeans 11.1-beta2 Is Available for Testing!

gt;> >> >> >> https://github.com/rtaneja1/netbeans/blob/installer-bin-11-1/nbbuild/installer/binaries/Apache-NetBeans-11.1-bin-windows-x64.exe >> >> >> >> https://github.com/rtaneja1/netbeans/blob/installer-bin-11-1/nbbuild/installer/binaries/Apache

Re: Final preparation for NB 11.1 voting

On Wed, 10 Jul 2019 at 12:43, Eric Barboni wrote: > I guess that the "new" Jenkins task do the same than the release job (need > review to be sure)). Yes, not exactly filling me with confidence there! :-) Anyway, other build tasks (Snap, Installers, etc.) rely on the netbeans-release task.

Re: Final preparation for NB 11.1 voting

On Wed, 10 Jul 2019 at 13:39, Geertjan Wielenga wrote: > > Just a note -- there's quite some new code, especially around Java EE 8 and > Payara, that will be in the vc for the first time -- and therefore we > should not be surprised if we might need a vc2 to solve issues that might > come up

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

On Thu, 11 Jul 2019, 20:05 Josh Juneau, wrote: > > I have not yet created the PR, but I will do so. One question though, when > I compare files on the PR within my project on GitHub, it shows all of the > commit history for the Java EE 8 commits...so there are 13 commits showing > up in the PR.

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

Hi Josh, On Thu, 11 Jul 2019 at 04:05, Josh Juneau wrote: > At this point, I would like to request that we create a vc2 to include > these new enhancements. That way, the Java EE 8 support should be much > more stable, as the web.xml 4.0 would now being recognized correctly by the > IDE. Looks

Re: Final preparation for NB 11.1 voting

On Wed, 10 Jul 2019 at 14:33, Eric Barboni wrote: > > My bad, I wrote a mail last week for the building pipeline. No problem, I just hadn't realised you'd intended that pipeline to be used in the release process (yet) Just found an issue with sig tests that's also delaying the release thread -

[VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

Dear all, This is our first voting candidate for the 11.1 release of Apache NetBeans. Apache NetBeans 11.1 constitutes all clusters in the Apache NetBeans Git repo, which together provide the NetBeans Platform (i.e., the underlying application framework), as well as all the modules that provide

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

On Thu, 11 Jul 2019, 04:05 Josh Juneau, wrote: > At this point, I would like to request that we create a vc2 to include > these new enhancements. That way, the Java EE 8 support should be much > more stable, as the web.xml 4.0 would now being recognized correctly by the > IDE. > How major is

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

On Thu, 11 Jul 2019 at 09:18, Geertjan Wielenga wrote: > We should just document the various features that aren’t quite right yet > and create issues for them. If we don’t, this is potentially the start of a > very significant slip that we can’t afford. Agreed, particularly now I can get into

Re: [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

On Thu, 11 Jul 2019 at 14:54, Alessandro wrote: > Don't know if this matters a lot but the NOTICE file in the source archive > is completely different from that on the git repository (copyright end > year, additional license statements for Kotlin, IntelliJ IDEA, Struts, > Jakarta Validator).

Re: Website changes for NB 11.1

On Thu, 11 Jul 2019 at 09:42, huang kai wrote: > > +1 and I think there should be a group of links that link to the older build > of netbeans. Thanks! Yes, my intention is for the [Find out more] button under Older Releases to link across to a sub-page to group all those links and related

Re: Is this design weird

On Thu, 11 Jul 2019 at 12:17, Emilian Bold wrote: > I think it's an editor bug to show that hyperlink for every word when > Cmd is pressed. It normally should show that only if there is some > action possible, but I guess there might be some design considerations > that make querying that a bit

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

On Thu, 11 Jul 2019 at 12:51, Josh Juneau wrote: > > Thanks Geertjan...I will provide some details of the Java EE 8 support in > 11.1 on the wiki page. > Could you also add a known issues and workarounds section? That would be useful to add on the website. I wonder if we should also use

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

On Thu, 11 Jul 2019 at 13:06, Geertjan Wielenga wrote: > > Makes sense to me. The other approach is to consider all non-LTS releases > as preview releases by default, i.e., preview release for the next LTS > release. Yes, that was definitely my thoughts on the schedule and making use of

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

On Thu, 11 Jul 2019 at 10:24, Geertjan Wielenga wrote: > > The other thing to bear in mind is that Josh is now really in the groove, > or whatever the term is, in terms of his Java EE 8 / NetBeans development > skills -- this is excellent news. It's all good from here, since everything > he does

Re: a couple of fixes..

On Thu, 11 Jul 2019 at 19:06, Brad Walker wrote: > > I have a couple of very simple fixes that I'm hoping didn't get forgotten > about since they are trivial. Merging to master is currently closed for anything not going into the NB 11.1 release. So they haven't been forgotten about, but also

Re: [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

On Fri, 12 Jul 2019 at 07:52, Alessandro wrote: > Neil explained that the NOTICE file in the zip is generated by an Ant task > that takes nbbuild/notice-stub.txt as a header, the NOTICE file in the root > of the repo is not going to be distributed. > Maybe it would be better to delete it? No, it

Re: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

Hi, Copied from PR ... On Thu, 11 Jul 2019 at 22:35, Josh Juneau wrote: > Thanks Neil! I’ll submit the PR tonight. I appreciate it. Unfortunately this PR is broken. I've tried manually creating a patch based on your last commit and it also fails to build with the same error as in Travis

[CANCELLED] [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

Hi, So, unfortunately a critical issue was picked up in NB 11.1-vc1, and voting on that has had to be cancelled. See https://issues.apache.org/jira/browse/NETBEANS-2824 Despite downgrading to Critical because there is a (horrible) workaround, there's no way we should release NB 11.1 with it in.

Re: [CANCELLED] [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

On Fri, 12 Jul 2019 at 11:32, Geertjan Wielenga wrote: > > I think the following should go in to beta-4: > > - Gaurav's fix for the Payara Micro issue that triggered the need for beta-4 > - Laszlo's license fixes > - Josh's PR, if he can get to it in time, > - Toni's PR about the DukeScript

Re: [URGENT] Java EE 8 support fixes / beta4?

On Fri, 12 Jul 2019 at 16:31, Geertjan Wielenga wrote: > > Thanks for your resilience and calm control of everything. :-) There is a famous phrase about a swan! ;-) After a couple more failed attempts, we got all green lights, and it's merged to master. Assuming the PR to release branch also

[URGENT] Java EE 8 support fixes / beta4?

Hi, Josh and I could do with someone having a quick look at why the Travis test on https://github.com/apache/netbeans/pull/1375 is failing? It's been retriggered a couple of times so it's not a one-off glitch. It says it's failing on ant verify-libs-and-licenses. Neither of us can replicate

Re: Where do "Third Party Libraries" point to?

On Fri, 12 Jul 2019 at 13:38, Emilian Bold wrote: > The URLs for the other update centers are normal URLs that an user can > download and look what the XML contains. > > The "Third Party Libraries" update center seems more special as it has > the URL >

  1   2   3   4   5   6   7   8   9   10   >