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

[Neil C Smith]

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 opinion/interpretation in the issue and help
> resolving it.

It is the following two paragraphs that are relevant, and they are
adopted (verbatim as far as I can tell) from the Classpath Exception,
as in https://www.gnu.org/software/classpath/license.html  This
exception has a lot of other uses, particularly in the Java ecosystem
- using it myself for a few things.

> If the ASF can do it alone, I'm all for it, but the issue stands
> unresolved.

Well, I found an interesting comparison point recently -
https://www.eclipse.org/org/documents/GPL_CE_Policy.php

> So Oracle and the ASF both had to be
> aware, that bundling the only freely distributable JDK (OpenJDK) will
> be a major PITA.

Because of ASF policies though.  The point of the CPE is to allow this
sort of bundling.

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] Draft release schedule

[Neil C Smith]

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 between now and then to reconsider.


> I recommend you send a mail with LAZY CONSENSUS in the subject, outline the
> release plan, specify 72 hours for objections, or otherwise you’ll then go
> ahead with it.
>

Ah, sounds much better, will do. Didn't want to consider this thread lazy
consensus.

Thanks and best wishes,

Neil

>

Re: [DISCUSS] Draft release schedule

[Neil C Smith]

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.  Basically anything that affects how we do the next release
and whether we archive 11.0 or not.

If we are freezing master for a month in mid-June, it would also be
good to decide and advertise that by end of next week or so?

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] Draft release schedule

[Neil C Smith]

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 instead?!

Only reason I suggested vote is that it maybe gets more people to buy
in or raise a -1 than a discussion thread?  I've curated things
various people have said in the past into what feels like a viable
plan.  But I'm wary of setting a precedent in how I think we should do
11.1 that causes unforeseen issues down the line that are difficult to
unwind.

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: Users banned from apache.org due to downloading updates.xml.gz

[Neil C Smith]

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).
>

Sounds like a plan, although also like it will complicate the VM
configuration quite a bit? Given current release process do we really need
to track individual nbm downloads?

We do still have an issue with n.a.o to VM redirect as far as I can tell.
Any chance you or someone else can try a platform download using the Ant
harness and the UC? Maybe it's an issue at this end, but don't think it is.

Best wishes,

Neil

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

[Neil C Smith]

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 mirror,
bypassing closer.lua

updates.xml.gz can be on netbeans-vm.a.o

> That's the question! How well are we doing with statistics? Would it be
> possible/better for the IDE to send periodic reports (including
> OS/modules/etc.) to netbeans-vm.a.o for later statistics analysis? Or is
> this banned by the ASF?

No idea, but we could still track catalog access.  But given people
can currently only download a full IDE, and we're not making much use
of updates, at least on the IDE side there doesn't seem much to track
via NBMs?

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: Users banned from apache.org due to downloading updates.xml.gz

[Neil C Smith]

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 intended to be
downloaded from the VM, not through closer.lua, but still with statistics?

Best wishes,

Neil

>

Re: [DISCUSS] Draft release schedule

[Neil C Smith]

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 be closed for extensive periods of time, it
> feels there should be a place where work could happen (rather than managing
> private branches that are effectively done, but cannot be pushed/merged
> anywhere, as the master is closed).

Well, one question would be, what did you have in mind when you
originally suggested it?! :-)

I wondered about this myself, but left it out for now.  How useful /
necessary does it feel in practice?  What are the downsides?  eg. is
it simplifying the release merging process just to end up complicating
it elsewhere?  What work cannot happen in the context of pull
requests?  Could we set up various feature branches on a case by case
basis where there's a need to merge interdependent private branches
together to work on?

I guess my thought was not closing master completely for all of that
time - just concentrating on stabilisation merging only.  We could
rethink it completely?  Or still do a release branch when we're closer
to the release date?  Just trying to get cherry-picking out of the
process as much as feasible, and make sure release and master fixes
tie up.

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: 11.1 info publicly available

[Neil C Smith]

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 there, but I changed the description last week.

Perhaps we should also have an NB 11.2 one for things that are mostly
complete but we think we should hold back on until the merge window
reopens post NB 11.1?

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: 11.1 info publicly available

[Neil C Smith]

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. Maybe that could be clarified?

Best wishes,

Neil

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

[Neil C Smith]

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, everything that goes into master is intended for NB11.1 until the
NB11.1 release happens.  So anything intended for NB11.2+ should not
be merged to master until after the release and the merge window opens
again.

We may need to adapt that process if it proves problematic - see
earlier discussion with Jan.

> What are the steps to include PRs into the 11.1 release (before
> the branch is created as well as after it is created)? How shall I mark an
> issue that (I believe) has to be fixed in 11.1 release?

Anything merged to master will be merged to 11.1.  There is a GitHub
label for PRs for 11.1 already.  I'll check if there's also one for
11.2.  I also need to check exactly where we're at with Jira labels
(just back from a week at a conference and getting up to speed again!)

> Is there a list of
> such issues?

I also need to check in respect of Jira - as far as I know, yes.

> Thanks for any enlightenment. I feel a bit confused and lost so far.

Sorry!  This cover everything?

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: Schedule of 11.1 release was: 11.1 info publicly available

[Neil C Smith]

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 even if we'd like to.

I've tried to pull the various suggestions that have been made into one
plan. But if this approach causes any problems with development during
release then we review, and either way we definitely review post NB11.1
release.

Best wishes,

Neil

Re: Installers -- making them official for 11.1?

[Neil C Smith]

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 correctly,
the last time this came up we talked about people distributing a build from
unmodified sources being allowed?! And fairly sure it was up to us to
define acceptable uses of the name?

Having reproducible builds might be good for this in future.

Best wishes,

Neil

>

Re: Installers -- making them official for 11.1?

[Neil C Smith]

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 we might want to clarify the distinction between that and
derivative though. Eg. Removing modules / clusters, etc.

Best wishes,

Neil

>

Re: Installers -- making them official for 11.1?

[Neil C Smith]

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 -
https://lists.apache.org/thread.html/072862707d0c75ec72f474d696a1addd994055b0c5b7617d3c7403ca@%3Cdev.netbeans.apache.org%3E

Best wishes,

Neil

>

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

[Neil C Smith]

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 or the Nashorn parser in your own built NetBeans, you can't do
> it either from the NetBeans that is pre-built for you?

This isn't correct - I see exactly the same issue - the update center
link building from master that Ken links to doesn't exist.

Adding back the old Plugin Portal link from NB11.0 does get everything
to work again.

http://plugins.netbeans.org/nbpluginportal/updates/11.0/catalog.xml.gz

Looks like https://github.com/apache/netbeans/pull/1293 is broken?

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: JIRA permissions / releases?

[Neil C Smith]

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: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NB11.1 spec version increment?

[Neil C Smith]

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 your testing release emails - for some
reason were difficult to find - think my filtering went funny because
they were also going to netcat.

> > Out of interest, did you PR all required changes into the release
> > branch or push directly to the repo?  I'm inclined to the former as a
> > sanity check on whether I've picked up everything that needs doing
> > anyway.
> I usually announce the release workflow usually around the time when I
> cut the release branch. Basically for cherry-picks, as they were
> reviewed for master once, I committed them directly to the release
> branch unless it would result a non-trivial merge. In the later case I
> asked for a PR from the author(s) specific to the release branch.

Thanks.  Well, that should be easier as we're merging everything from
master now!

However, I was thinking more about how you handled commits you made
*only* on the release branch (release specific stuff like version
number, launcher settings, etc.).  Of course, some of those may not be
required now - sooner we can get them all configurable as build
parameters the better!

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: JIRA permissions / releases?

[Neil C Smith]

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 now.  It's always good to know I'm not being
an idiot when I can't find something! :-)

I also hadn't realised that the JIRA UI could get even more convoluted
than it was before.

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

JIRA permissions / releases?

[Neil C Smith]

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 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

NB11.1 inbound - what is NetCAT lite?

[Neil C Smith]

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 thing I'm still unsure about is what we mean by NetCAT lite?
I guess we should actually have an email about the release schedule,
LTS, etc. on netcat@?  My bad, I should have thought about that
earlier.  But what do we actually say?  Invite people to just try the
beta?  Highlight specific new  / tribes that we might want to look at
anything new?

Thoughts?

* I won't be doing the release branch until Monday, just in case
anything needs to sneak in.  Before and *after* Monday, everything
that goes into master should be intended for NB11.1 - in an ideal
world every PR merged from Monday will have a corresponding issue in
JIRA tagged with 11.1.

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: JIRA permissions / releases?

[Neil C Smith]

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

-
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

AutoUpdate and Installer hard-coded versions?!

[Neil C Smith]

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 and Installer classes?!

eg. from https://issues.apache.org/jira/browse/NETBEANS-2677

nb/o.n.upgrader/src/org/netbeans/upgrade/AutoUpgrade.java
nb/autoupdate.pluginimporter/src/org/netbeans/modules/autoupdate/pluginimporter/Installer.java

Given we probably don't need to support import from versions prior to
7.2 any more, can we not list and sort available directories and pick
the first one less than our current version automatically now?  What
would be the pros and cons of that change?

Incidentally, I'm planning on treading lightly for NB11.1 so would
probably make that a PR early for NB11.2.

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: Updating the website for the new release

[Neil C Smith]

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 
https://github.com/apache/netbeans/pulls?utf8=%E2%9C%93=is%3Apr+merged%3A%3E%3D2019-03-01+sort%3Aupdated-asc+

Filtered as is:pr merged:>=2019-03-01 sort:updated-asc

The date might not be quite right, and some things will have been cherry picked.

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: AutoUpdate and Installer hard-coded versions?!

[Neil C Smith]

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 right this change
goes in master rather than just in the release branch, right?

In future I would have thought this change should happen when we open
the merge window for the next release?

I wonder if the reason is about not listing files or not having access
to the version number?  If the former, it would also be easy to
generate the list to search.  If the latter, then something to look at
fixing.  Either way, in NB11.2 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: Apache NetBeans 11.1-beta1 Is Available for Testing!

[Neil C Smith]

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:
...
> /Users/sven/tools/netbeans-11.1beta1/java/modules/org-netbeans-libs-javacapi.jar
> was enabled before, will not accept fragment
> StandardModule:org.netbeans.modules.nbjavac.api jarFile:

That looks like something I've read today - see
https://issues.apache.org/jira/projects/NETBEANS/issues/NETBEANS-2637
and the tail of the log?  Think that's against 11.0 too.  Be good to
get exact steps that consistently trigger this, if there are any.

I may have seen this while updating the release branch too, but put it
down to the redirects for the UC bedding in - not seen it since - been
through a few userdirs since then!

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: Installers for 11.1 release

[Neil C Smith]

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.
> > Can you confirm the reasons and requirements for the local Mac build?
> Apache infra doesn't support Mac build hosts, we need to provide a
> remote host.
> https://issues.apache.org/jira/browse/INFRA-17961

So the requirement is macOS!  :-)  I wasn't sure if the build could
work cross-platform.

> Updated job to build from netbeans-release artifact, build #20 has
> installers for Beta. I still have to build for Mac, will share by tomorrow.
> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/20/

Thanks.  The commit history got me as it's for master.  I assume
that's not a problem - should the repo link be to release111 branch
not master?  Or is it used at all?

Guess we could use wildcards for the artefact?

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: NB11.1 Feature Freeze - master branch closed except for fixes!

[Neil C Smith]

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.  If a PR is
fairly standalone, then we tag it with NB11.2 and merge when the
window reopens after the release, after the spec version update and on
top of any bug fixes.

OTOH, as Jan, I and others discussed here, there might be a need to
consider a short-lived "next" branch (or in my opinion various feature
grouped branches) to allow for collaboration while master is closed.
We agreed to review after NB 11.1 release, and during if it poses a
problem earlier.

In respect of PR 1301 need to consider whether to revert the commit
and reapply later, or whether the code is OK to remain in place.
Either way, it won't be in first beta now.

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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Neil C Smith]

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 and 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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Neil C Smith]

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?

The only current way I think is the IDE log itself, where the modules
have the release number and build date?

Ideally the version in the UI would have a -beta suffix, which I don't
think we had with NB 11.0 either.  I could (should) have added this in
all the different places it's mentioned for each beta release.  I'm
putting some thoughts together for NB 11.2 so that the remaining
changes required in the release branch (eg.
https://github.com/apache/netbeans/pull/1304 ) can be set from one
place in the build so that we can more easily update each time.

Hopefully anyone outside of this community will only be using the
voted on releases anyway! :-)

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: Request for Cherry-picking for NB-11.1(https://github.com/apache/netbeans/pull/1323)

[Neil C Smith]

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 go in. If not, I'll take a look at everything labelled
NB11.1 first anyway.

Best wishes,

Neil

>

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

[Neil C Smith]

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 (everything will be merged across) and ideally
with a JIRA ticket and taking into consideration NetBeans bug priority
guidelines 
https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines

Please tag any PR intended to be merged with NB 11.1 - I'll keep an
eye out for them!

This email is prompted partly by
https://github.com/apache/netbeans/pull/1301 :-)

Thanks and 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: Apache NetBeans 11.1-beta1 Is Available for Testing!

[Neil C Smith]

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, does the Java with Maven / Java Frontend Application
work for you after those steps?  This wizard just hangs for me after
activation as above.

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

Merging of PRs for 11.1 and 11.2

[Neil C Smith]

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 the release.

PRs to be included in next release (eg. NB 11.1)

* PRs should be made/reviewed in accordance with the Bug Priority Guidelines
* (almost) all PRs should have a related JIRA ticket with 11.1 as the
fix version - add the ticket reference in the PR title (and ideally a
full link to the issue in the description)
* Tag the PR with the release label (eg. NB 11.1)
* Add the release manager as a reviewer (in this case me) to help
tracking / scheduling

PRs ready to be merged in the following cycle (eg. NB 11.2)

* If the PR is ready for merging, add the following release label (eg. NB 11.2)
* A few days after the release (NB 11.1) necessary commits to master
such as spec increments will be made.
* Following that, the merge window reopening will be announced.
* Priority will be given to merging all pending PRs labelled as above.

Any thoughts, issues, comments?

Thanks and 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

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

[Neil C Smith]

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 Java EE and Payara PRs to be merged to
master for the NB 11.1 release -

* Incorporating new files and code modifications for adding Java EE 8
support. https://github.com/apache/netbeans/pull/1298
* NP-20 Payara Server tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1290
* NP-20 Payara Micro tools integration in Apache NetBeans IDE.
https://github.com/apache/netbeans/pull/1297

One of the reasons we discussed having quarterly and non-LTS releases
was to get things testing in the wild earlier.  These partly missed
the feature freeze because of Travis issues, seem ready to merge, and
(hopefully!) have minimal impact on existing features.

This is a lazy consensus thread that will be open for 72hrs.  You do
not need to +1 (although you're welcome to), but do raise concerns or
-1 if need be.  Assuming this goes ahead, we can merge in time to sync
up and include in beta2 next Wednesday.

My own lazy consent as release manager is also based on -

* All tests are passing before merging (appears now to be the case)
* Merging is done before second beta (possibly a good criteria for
feature freeze bypass in general?)
* The respective contributors can commit to timely fixes in case of
issues so that this doesn't cause delay in the NB 11.1 release
schedule.

Thanks and 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: Files to License List

[Neil C Smith]

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.
>
> Excellent, another step towards NetBeans World Domination!

Well, they were NetBeans platform based before AFAIK.  However,
another step towards Apache NetBeans World Domination perhaps! :-)

And on a more serious note, a move I find a reassuring sign
post-Apache donation.

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: [Lazy Consensus] Feature freeze pass for Java EE and Payara PRs for NB 11.1

[Neil C Smith]

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 be good, Gaurav, if
you can have a quick check over.

Thanks and 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

NB11.1 spec version increment?

[Neil C Smith]

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 the spec version in master was incremented immediately for the
next release.  That correct?

Now, given we're feature freezing and merging everything from master
to release branch, should we instead increment the spec version in
master as the first step in opening the merge window for NB11.2
*after* the NB11.1 release?

I assume we still need the branch spec increment on the release
branch?  If so, when?  Immediately for a beta build?  Or, as a last
step before tagging a voting candidate for final release?

Thanks and 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

Apache NetBeans 11.1-beta1 Is Available for Testing!

[Neil C Smith]

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 tagged beta not vc!).

As per the recently agreed release schedule, NB 11.1 is a non-LTS
release, and will not have a full NetCAT process.  However, feedback
and testing from those on the dev@ and netcat@ lists would still be
appreciated, particularly around new features.  Please file issues in
JIRA as necessary, with the affects and fix versions set to 11.1.

Further betas will be released, as required, on June ~26th and/or July
~3rd.  The final NB 11.1 release is scheduled for July ~15th.

The next full NetCAT is scheduled for NB 12.0 in early 2020, which
will be the next LTS release.

Release schedule :
https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
NB 11.1 major changes :
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1


See the artefacts here:

https://builds.apache.org/job/netbeans-release/413/artifact/dist/

The binary you most likely need is:

https://builds.apache.org/job/netbeans-release/413/artifact/dist/netbeans-11.1-beta1-bin.zip

Installers, as mentioned in the major changes link, are in progress.

The SHA512 sums if you would like to check them are provided there as
well as here:

8d401c2e2b16fca5b236da24a379416f315fc8ac83177cc740319a3c3fdd31154af683b624cf31968d6bd4288de96de4d651a7b2990f1da4d5c456f3849bdb59
 ./netbeans-11.1-beta1-bin.zip
78061ea3dde1741b50dc0aa3a994274d688285b58b6ec0ac48426ae15bbb2cddec348d85d36ddaf5a6a4b459f5cdfb7d11bbab59ed1bb5b072f245cbfbd02f06
 ./netbeans-11.1-beta1-source.zip
a3d1b839a859ad3b916e7ae54e6335aa071a7530c17ab7749f1267eb38f7666823862af886aae53c9ccc379e131d28f5ab8de2498b97e3433c2fbb59c1217d2e
 ./netbeans-platform-11.1-beta1-bin.zip
91b494fa43925f4c8a73a9be5a57fe24f7b0d496a37a79678fd7d0fbb91d8a0f73a68cf35dfb6ea4d82f5594b29f958716f31ebe9a85f317d4404c9da995d8bb
 ./netbeans-platform-11.1-beta1-source.zip


Thanks and best wishes,

Neil

Voluntary Release Manager for Apache NetBeans 11.1

-
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: Installers for 11.1 release

[Neil C Smith]

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 daily build job.
> But for release build, it should pick up release artifact from release
> job [2]. This artifact is generated by Release Manager as per Release
> README wiki, wiki has link to old job I think.

So, the first beta release build has been done.  What's required to
update and trigger your build job?  Note that the artefacts from the
release build no longer have incubating in their names.

Quite a few wiki links have broken now our build jobs have moved out
of incubation.  I'll fix any I notice.

> Neil or I can build the installers once release artifact is built.
> Please let me know. Signing installers will require code signing
> account, as per the steps I followed.

Perhaps better if you can do at least the first beta one?

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: PR-1245 Splash Screens and About Dialogs

[Neil C Smith]

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 TrueType font that we use at build
> time (Montserrat-medium.ttf) but it seems there're problems with
> synchronization that I'm currently tracking.
>
> Feel free to discuss & improve.
>

Looks great!  And will definitely improve the release process.

One query would be about using OSUOSL for the font file.  Wasn't there
a general principle to move away from there in favour of Maven hosted
artefacts where possible?  This font is available.  Could be a follow
up?

Haven't looked carefully, but is there any impact to follow up on RCP branding?

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

[DISCUSS] Draft release schedule

[Neil C Smith]

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 to decide what goes in it, whether it was 11.1
or 12, and what branch to build it off! :-)

So, I've had a re-read of various threads we've had about this in the
past, and tried to come up with something that combines things that
have been suggested, what feels deliverable, reservations people had,
and where NetCAT fits in to all this.

Full version is here.  It's a draft!  (It did have draft in the title
until I got annoyed with Confluence's approach to linking).

https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule

Some key things.

* Fixed quarterly releases based off master.
* Fixed merge windows and feature freeze dates.
* Annual LTS releases that go through full NetCAT process and remain
downloadable for the year. Minimal backporting of critical bugs - you
want features, jump on the fast train and help test them.
* LTS has shorter merge window to allow time for NetCAT, and should
have less new features anyway!
* Next releases are then NB 11.1 (Jul), NB 11.2 (Oct), NB 11.3 (Jan
2020), NB 12.0 LTS (Apr 2020)  - perhaps counter-intuitively major
version increases when least new features.
* NB 11.0 remains available until next April.
* All commits to master go in the next release and release branch
merges everything - so no feature merges to master outside of the
merge window, and all merges during those periods take into account
the bug priority guidelines.
* Feature freeze for NB 11.1 would be ~15th June. (if everyone's on
board with this be good to publicise that fact soon!)

Please feel free to take it apart .. gently! ;-)  Suggestions that
this is all about making my job easier over the next couple of months
are .. entirely correct.

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] Draft release schedule

[Neil C Smith]

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 way we want it to? Is there a better way to test?

i took the NetCAT parts of the LTS schedule from a suggestion put
forward on the initial quarterly release thread, which had a week for
test specs.  That was based on doing NetCAT on each quarterly release
though, which to me seems impractical.  And from my recollection a
week is a little short?!

So if it's brought forward, how far?  Still post-freeze?  Or tied to
PR's that affect them?

I'm guessing I personally see the non-LTS releases also about testing
in the wild to a degree?  And defining what NetCAT-lite actually means
in practice.

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: Users banned from apache.org due to downloading updates.xml.gz

[Neil C Smith]

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 went to the VM it will eventually just
> crash out on sheer number of connections.

Except that everything is going via the VM first anyway as far as I
can tell?!  Check the log I posted, or #7 at
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README

It seems my problem actually isn't quite the same, but something being
limited in the netbeans.apache.org -> netbeans-vm.apache.org redirect
process.  It might be the solution is the same though?

What about -

* rethinking where the catalog.xml is hosted, ideally somewhere
without redirects, or at least without a query in the URL?  (assume
this might be a caching issue?)

* use absolute rather than relative URLs in the catalog.xml and point
directly to closer.lua?  That way hosting of catalog and NBMs can be
separated?  And we can update the catalog.xml itself rather than the
redirect when archiving releases?

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: NBM Signing...

[Neil C Smith]

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 NBM builds! :-)

Hash would definitely be good for validating third-party plugins too
if they're hosted elsewhere from the plugin manager catalog.

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] Draft release schedule

[Neil C Smith]

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 calendar year from January to December, I might replace
> version prefixes 11. and 12. 13. with something as  in order
> not to get the feeling that we are developing two versions in parallel,
> one LTS and one non-lts (I'm sorry that was how I read the table first,
> then I looked into the details.)

Thanks!  Definitely not your bad! :-)  Sorry for the delayed response
on this comment.  I've updated the table a bit, not exactly as you
suggested but close I think.  Does it make more sense now?

i do think the dates should go from now to April, to emphasise that
the releases build towards the next LTS?  Or just April to April?

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: Request for Help : Java Hint to enable Preview feature in gradle project

[Neil C Smith]

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 wanted it as a global property (not sure!), maybe
somewhere in build.properties as a key related to the chosen Java
platform?  eg. platforms.JDK_12.enable-preview=true

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

Release process - update center configuration problem?

[Neil C Smith]

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 lines for the update center configuration -

curl 
https://dist.apache.org/repos/dist/release/incubator/netbeans/incubating-netbeans/incubating-11.0/nbms/updates.xml.gz
-o updates.xml.gz
echo ' RedirectMatch ^/uc/11.0/(.*)(\?.*)?$
http://www.apache.org/dyn/closer.lua?action=download=incubator/netbeans/incubating-netbeans/incubating-11.0/nbms/$1'
> .htaccess

Unless I'm missing something here, either the first line is
superfluous or the second line is wrong?!  What is the intention here?
 To serve updates.xml.gz from the VM or the distribution mirrors?
Should the redirect just be on *.nbm?

This obviously relates to recent thread on users being banned too.

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: Still Plugging Away on Java EE Support

[Neil C Smith]

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 new license for ASF! ;-) The CPE might be
tweakable but it's a standardized wording, so I can't see that
happening either.

Anyway, this is OT.  I stand by the opinion that this is one that ASF
needs to resolve itself, as the idea of Java being a "platform"
dependency gets overtaken by real world events.

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] Draft release schedule

[Neil C Smith]

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, wouldn't they?

That's an interesting question!  My inclination would be they should
still have UCs.  I wonder how many RCP people are using the Ant
scripts and the ability to set up autoupdate.catalog.url to download
the harness for example?  Or is that just me now?!  We would need to
be careful of all other uses of UCs, and may still want the ability to
push critical / security-related updates to non-LTS?

Incidentally, there is already a page for what is currently done in
the release branch but not in master at
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Branding
 Need to check if it's complete, and what given potential splash PR
still would need looking at in order to release from master if that
was desirable.

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: Users banned from apache.org due to downloading updates.xml.gz

[Neil C Smith]

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 done another verbose ant build to get a log, and
the issue I have isn't quite the same.  The main catalog redirects to
the VM, which then redirects via closer.lua  But it's the first
redirect that seems to fail after a while, so it's another issue in
how we're handling updates redirects i think?!

eg.

[get:org.netbeans.modules.editor.guards]
http://netbeans.apache.org/nb/updates/11.0/ide/org-netbeans-modules-editor-guards.nbm
moved to 
http://netbeans-vm.apache.org/uc/11.0/ide/org-netbeans-modules-editor-guards.nbm
[get:org.netbeans.modules.editor.guards]
http://netbeans-vm.apache.org/uc/11.0/ide/org-netbeans-modules-editor-guards.nbm
moved to 
http://www.apache.org/dyn/closer.lua?action=download=incubator/netbeans/incubating-netbeans/incubating-11.0/nbms/ide/org-netbeans-modules-editor-guards.nbm

and later

[get:org.netbeans.modules.xml.xam] Getting:
http://netbeans.apache.org/nb/updates/11.0/ide/org-netbeans-modules-xml-xam.nbm
[get:org.netbeans.modules.xml.xam] To:
/tmp/org-netbeans-modules-xml-xam9083219336849970974.nbm
[get:org.netbeans.modules.xml.xam] Error getting
http://netbeans.apache.org/nb/updates/11.0/ide/org-netbeans-modules-xml-xam.nbm
to /tmp/org-netbeans-modules-xml-xam9083219336849970974.nbm

Fails at a different point each time.

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: Users banned from apache.org due to downloading updates.xml.gz

[Neil C Smith]

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 raised something similar here in a thread on redirects a few weeks
ago.  It also affects downloading a harness for RCP applications using
autoupdate.catalog.url  I've had to switch from the URL in the IDE
directly to the VM to get this process to complete without an error
(eg. 
https://github.com/praxis-live/praxis-live/blob/nb11/nbproject/platform.properties#L337
)

The nb-javac catalog uses full URLs rather than relative paths.  I
wonder whether that change needs to be made in the main UC catalog
too?  Otherwise not just the catalog itself, but every download, hits
that redirect IIRC.

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

Ant build of NetBeans RCP with --release

[Neil C Smith]

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 useful PR for those of us stuck using Ant?  But
...

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".  Same Ant, and as far as I can tell same compiler
arguments.  Any idea if there's something obvious I'm missing here?

Thanks and 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: Ant build of NetBeans RCP with --release

[Neil C Smith]

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
attribute fails inside the IDE unless the task is set to fork a
separate VM.  Replicated with a minimal Ant project.  Any idea whether
this is expected or a bug?

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: git repo - NB10?

[Neil C Smith]

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 branch, or the relevant tag in it.

The incorrect splash in master is a known issue AFAIK.

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: Volunteer Release Manager(s) Needed for Apache NetBeans 11.1

[Neil C Smith]

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 with a release snapshot of master, and with the
intention of trying to tidy up the various visions (or not!) of
time-based releases into a process everyone is on board with, so that
we're not trying to re-imagine the release process each time.

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] import Bugzilla to Jira or Plan to Drop Bugzilla

[Neil C Smith]

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 infrastructure was a possibility?!

Best wishes,

Neil

>

Re: [DISCUSS} Apache NetBeans Gradle Patch 1 Release

[Neil C Smith]

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 cherry-picking,
> release. Repeat X months later.
>
> That way we know:
>
> - when a release is due
> - what will be in the release (the state of master)
>

+1 to this. At some point in the initial thread on time-based releases Jan
also suggested merge windows for master to keep cherry picking minimal. I
think being stricter about what gets merged to master and when might be
required?

I was looking around the NB11 release process a while ago, and wondered
about feasibility of making some of those release branch commits be
configurable in the master build instead? That way branching could happen
more easily later in the schedule, after testing for final beta maybe?

Still think next should be NB 12.0 to do time-based releasing properly! As
Matthias said, you don't know for sure what's in it until you freeze
master, so how do you know it's major or minor?

11.1, 12.1 etc. could be reserved for patch updates where a new full binary
download might be warranted? There using release branch possibly makes more
sense.

Best wishes,

Neil

>

Re: What will be in 11.1/12?

[Neil C Smith]

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 whatever is there as NB12.  And fixing
that date as soon as possible so there's an advertised time to fix up
any desired PR's for that release.  Cherry-picking things to include,
or deciding now whether it counts as "major" or "minor", seems counter
to doing time-based releases.

And I still think it would be good to freeze master at branch point
for anything other than fixes intended for the next release, and run
merge windows for new features after the releases are done.

I'd be happy to consider being release manager this time around, as
discussed last time, if we do something along these lines.  I'm not so
keen to release manage with further cherry picking on to the
release110 branch.  If it's purely about bug fixes / improvements on
select modules, can't they be done separately via the update centre?

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: 11.1 beta-3 status

[Neil C Smith]

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 tried to keep them to a minimum though.

No problem!  We're all still finding our way on this new release
process.  I'd suggested all PRs for a release during release window
add the release manager as reviewer, and add JIRA reference in title /
link in description.  Seems to be an easier way for the release
manager to track and/or request changes in case of release problems
before things hit master now we're doing full merge across.

We should review that post-release, and add to / change in release
guidelines on the wiki as necessary.

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: 11.1 -- separate convenience binary for frontend development?

[Neil C Smith]

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 to run on weren't we looking at
someone like AdoptOpenJDK doing this?

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: 11.1 -- separate convenience binary for frontend development?

[Neil C Smith]

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 I'm a little wary of making changes to the build job for the
voting candidate after all betas have been done.

And, without a JDK, I'm not sure how useful they are in practice to justify it?!

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: 11.1 beta-3 status

[Neil C Smith]

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 still waiting on a review on requested changes from Jan.
I think all the requested changes are made, so can merge, or someone
else want to check all is ready?

The second is marked as failing Travis, but I assume just because of
earlier Travis issues - have retriggered the pending test and waiting
for completion.

Geertjan, you might want to take a look at the stale branches at
https://github.com/apache/netbeans/branches/all  I didn't delete any
of yours while merging the PRs, but we might want to remove some of
those temporary branches?

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: 11.1 beta-3 status

[Neil C Smith]

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 did.  Looks like we're back on track with Travis testing for
now, so would rather keep it that way.  Would still like to know what
caused all the issues with Travis in the first place 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: 11.1 beta-3 status

[Neil C Smith]

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 release though!

Having the release manager as one of the reviewers, but not
necessarily have to handle all merging, is probably the right way to
go in future.

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: Apache NetBeans 11.1-beta3 Is Available for Testing!

[Neil C Smith]

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 doesn't seem to have affected usage. Not great user
experience though.  eg.
https://issues.apache.org/jira/browse/NETBEANS-2558?jql=project%20%3D%20NETBEANS%20AND%20resolution%20%3D%20Unresolved%20AND%20text%20~%20%22accept%20fragment%20StandardModule%22%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC

At some point we need to make some better sense of JIRA.

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: 11.1 beta-3 status

[Neil C Smith]

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 for a break, and to let Travis run on this, then I'll merge and
fire up the build task.

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: 11.1 beta-3 status

[Neil C Smith]

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 label was missing, but
think you'd asked me to look earlier - sorry.

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: 11.1 beta-3 status

[Neil C Smith]

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 ?
> >
> > https://github.com/apache/netbeans/pull/1324
>
> OK, looking now.  Missed it because the NB11.1 label was missing, but
> think you'd asked me to look earlier - sorry.

Have retriggered the two tests that failed -
https://travis-ci.org/apache/netbeans/builds/550323219

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: 11.1 beta-3 status

[Neil C Smith]

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

-
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: Apache NetBeans 11.1-beta3 Is Available for Testing!

[Neil C Smith]

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 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: Beta 3 installers : Re: Apache NetBeans 11.1-beta3 Is Available for Testing!

[Neil C Smith]

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: 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: Maven repo for Apache NetBeans

[Neil C Smith]

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 picked up same way as any other Maven dependency?

Linking in for reference - https://issues.apache.org/jira/browse/NETBEANS-2730

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

Travis failures?

[Neil C Smith]

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 second beta plans unless I ignore them!

Any thoughts?

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: nb-javac and Oracle JS Parser on Maven Central

[Neil C Smith]

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 it's built from and how.  I've
raised this issue on the list before - this might be a good way to solve it?

Also agree with Eric that I don't see any way this could go under
org.apache namespace.

Best wishes,

Neil

Re: Travis failures?

[Neil C Smith]

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 master back in.

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: Travis failures?

[Neil C Smith]

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 is out, and if
so get it fixed before the final release.

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: Beta 2 Installers - Re: Apache NetBeans 11.1-beta2 Is Available for Testing!

[Neil C Smith]

Are these with a clean userdir or one from beta1?  I had somewhat similar
issues (on Linux) with a userdir from beta1.

Thanks,

Neil

On Fri, 28 Jun 2019 at 10:43, Geertjan Wielenga  wrote:

> Yes, I get this during the Mac install, Payara related:
>
> Warning - could not install some modules:
> Payara Common - The module Java DB Database Support was requested in
> implementation version "incubator-netbeans-release-404-on-20190319" but
> only "netbeans-release-417-on-20190626" was found.
> Payara Common - The module Java SE Platforms and Libraries was requested
> in implementation version "incubator-netbeans-release-404-on-20190319" but
> only "netbeans-release-417-on-20190626" was found.
> Payara EE Common - The module J2EE Support Utilities was requested in
> implementation version "incubator-netbeans-release-404-on-20190319" but
> only "netbeans-release-417-on-20190626" was found.
> Another module could not be installed due to the above problems.
>
> Gj
>
> On Fri, Jun 28, 2019 at 11:39 AM James Ostrowick 
> wrote:
>
>> Just downloaded the Mac OSX DMG - I get module warnings after
>> installation is complete as well as after startup:
>> I do know that this was mentioned as an issue before, but still - here
>> for reference in the thread.
>>
>> Warning - could not install some modules:
>> Nashorn Integration - No module providing the capability
>> com.oracle.js.parser.implementation could be found.
>> Payara Common - The module Java DB Database Support was requested in
>> implementation version "incubator-netbeans-release-404-on-20190319" but
>> only "netbeans-release-417-on-20190626" was found.
>> Payara Common - The module Java SE Platforms and Libraries was requested
>> in implementation version "incubator-netbeans-release-404-on-20190319" but
>> only "netbeans-release-417-on-20190626" was found.
>> Payara EE Common - The module J2EE Support Utilities was requested in
>> implementation version "incubator-netbeans-release-404-on-20190319" but
>> only "netbeans-release-417-on-20190626" was found.
>> 28 further modules could not be installed due to the above problems.
>>
>> Clicking disable the modules allows startup to continue.
>>
>> Immediately on startup I get an update :
>> Eclipse Jobs Mechanism [3.5.100 -> 3.5.101]
>>
>> This requires a restart.
>>
>> When I open a project and I now need to “resolve missing server
>> problems”, upon clicking add server I get the following:
>> (Duplicate glass fish servers being shown) - not sure why.
>> However, if I manually go to the tools -> servers menu I don’t get the
>> duplicate glass fish options.
>> This is also fine if you go to the “services” tab, right click on
>> “servers” and “add server…” it also correctly only shows one glass fish
>> offering.
>>
>> Other than that, no significant issues.
>>
>>
>> Now just waiting for JBoss / Wildly integration… Unfortunately this is a
>> deal breaker for me.
>>
>>
>>
>> On 28 Jun 2019, at 11:14, Geertjan Wielenga  wrote:
>>
>> Excellent!
>>
>> Anyone reading this — please try out one or more of the installers below
>> and provide feedback (success, failure, problems) here in this thread.
>>
>> Thanks,
>>
>> Gj
>>
>>
>> On Fri, 28 Jun 2019 at 09:19,  wrote:
>>
>> Hi,
>>
>> Apache NetBeans 11.1 beta 2 Installers are temporarily hosted for
>> testing on a branch in my github fork here:
>>
>>
>>
>> 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-NetBeans-11.1-bin-linux-x64.sh
>>
>>
>>
>> https://github.com/rtaneja1/netbeans/blob/installer-bin-11-1/nbbuild/installer/binaries/Apache-NetBeans-11.1-bin-macosx.dmg
>>
>> You can use download button on respective pages.
>>
>>
>> Windows installer(unsigned) and Linux installer are also available from
>> Jenkins build job:
>>
>> https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/
>>
>>
>> Thanks,
>>
>> Reema
>>
>>
>>
>> On 26/06/19 11:56 PM, Neil C Smith wrote:
>>
>> Dear Community,
>>
>> I'd like to announce that the second beta build for Apache NetBeans
>> 11.1 from the release111 branch is available for download.
>

Re: Final preparation for NB 11.1 voting

[Neil C Smith]

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.  Ideally all the Maven stuff would too, or we
switch everything over to the new pipeline.

But, an email literally 5min before I was triggering the voting
candidate build, and without us having used that pipeline for any of
the betas or tested with any of the depending tasks, doesn't feel
right.  So, unless we intend to push the schedule back by at least a
week to fit in another beta, my intention is to go ahead with a vc off
of netbeans-release today.

Then we can figure out what's missing and how to get it in place ...

> AFAIK, we vote also the nbm files as conveniences libraries, so maven 
> artefact are part of this concept.

We don't vote on the nbms or the binaries of the IDE or platform.  We
vote on the sources.  See eg.
http://www.apache.org/legal/release-policy.html#compiled-packages  The
important thing is that all the source required to build the binary
artefacts is in the source releases we vote on.  I'm assuming this is
the case, even if we might be missing some instructions?

The PMC also has responsibility to ensure any convenience binaries are
correctly made, signed, etc.  But AFAIK we can have a sanity check
thread about them after the release vote if necessary.

Thanks and 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: Final preparation for NB 11.1 voting

[Neil C Smith]

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 immediately when we try out those newest new features. We may not
> need a vc2, but if we do, we shouldn't be very surprised.

Well, I'm at least hopeful we won't!  Bear in mind, we've had three
betas, which in NB 11.0 were also called vc.  So by NB 11.0 standards
this is vc4. :-)

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: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

[Neil C Smith]

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.  This is similar to the last PR I submitted that showed 12
> commits...I believe you probably remember this.  Should I just go ahead and
> proceed to submit the PR, or is there something I need to do with my fork
> before submitting?
>

It's because your commits were squashed and merged in the original PR so
don't exist in the upstream history. Ideally keep your fork's master branch
in sync with upstream and create a separate branch off it for each PR.

I should be able to squash and merge the new PR to get it to work though,
as I did with your last fixes, if you can't do above in time.

Thanks and best wishes,

Neil

>

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

[Neil C Smith]

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 like you might be in luck! :-\  The Payara Micro bug seems like
it's going to force a second VC.

Is there a PR for this fix yet?  If not, could you create one?

Given time pressures, I might not be able to roll another VC until
early next week.  But, if we can get relevant fixes in tomorrow I
might use that to our advantage and look at a beta4 to test with for a
few days before then.

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: Final preparation for NB 11.1 voting

[Neil C Smith]

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 - so much for this being an easy day! :-)

> But yes source vote only,  but I'm not sure convenience that use apache infra 
> can be populated without control.

Totally agree.  The PMC has a responsibility to ensure that things
under our dist control are OK.  Hence my comment earlier about a
sanity check thread.

ie.  something like committer uploads to dist/dev, opens a mailing
list thread, and as soon as three +1 checks from other PMC members,
convenience binaries get moved over to dist/release?  Obviously
somewhat different for Maven artefacts in terms of where they end up,
but same principle?

I wonder how other projects handle this aspect?

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

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

[Neil C Smith]

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 the Java SE, Java EE, PHP, JavaScript and Groovy features of
Apache NetBeans.

Build artefacts are available here:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc1/
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/11.1-vc1/

Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and
NOTICE files, as well as a README file with build instructions, which
are the same as these:
https://github.com/apache/netbeans/blob/release111/README.md

We are voting on:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.1-vc1/netbeans-11.1-vc1-source.zip

SHA512:
7f49cfca8d27f2e08d0e5d9b4f61d70baddfdfa013f4a783feb2a1e203d7a1c7208321cdb0be7aa49d469c027e221999c8c0e4b9d911eec35a7d2e3cf8859466
 ./netbeans-11.1-vc1-source.zip

KEYS file:
https://dist.apache.org/repos/dist/release/netbeans/KEYS

Apache NetBeans Git Repo tag: 11.1-vc1 :
https://github.com/apache/netbeans/tree/11.1-vc1

Note: NetBeans license violation checks are managed via the
rat-exclusions.txt file:
https://github.com/apache/netbeans/blob/release111/nbbuild/rat-exclusions.txt

Rat report shows no unknown licenses, except for license files:
https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-release/423/artifact/rat-release-temp/nbbuild/build/rat-report.txt

Release specific wiki page:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.1


How (and what) to try out with the release:

1. Download the artefact to be voted on and unzip it.
2. Check that the artefact does not contain any jar files, except for:
- 
platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar
- enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
- enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
- enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
- enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
which are only jars by their name
3. Verify the cryptographic signatures, the NOTICE and LICENSE file
4. Build it using the README provided by the artefact.
5. Look in nbbuild/netbeans for the NetBeans installation created by
the build process.

This vote is going to be open at least 72 hours, vote with +1, 0, and
-1 as usual.  Please mark your vote with (binding) if you're a
NetBeans PMC member to help with voting admin.  NetBeans 11.1 will be
released if and when this vote passes.

Convenience binaries, not relevant for voting purposes, are staged at
the build artefacts links above.


Thank you for all the hard work!
And fingers X'd my first release voting thread is all correct - speak
up if there are any issues.

Best wishes,

Neil
Volunteer Release Manager for Apache NetBeans 11.1

-
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: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

[Neil C Smith]

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 this (JIRA down)? Specifically, according to our bug
guidelines, is this critical or a blocker? What if any workarounds are
there?

I'm not averse to rolling another vc for this if there's agreement even if
it's not a blocker, but realistically it'll probably be beginning of next
week before I can find time to now, so it'll knock the release back up to a
week.

Best wishes,

Neil

>

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

[Neil C Smith]

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 JIRA and see mention of the
workaround.  It's also not been marked with 11.1(!). and only classed
as major (which seems accurate per
https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines
)

Creating the voting candidates (affectively the releases) is
significantly more time consuming than the betas.  More so when you're
still learning and have to rewrite half the docs because we're out of
incubation. :-)

Of course, if I've screwed something up in that process and we need a
second VC anyway then we should consider this.

But, in general, we're going to have a month of betas (two for LTS)
before releases, and that's the time we should be picking up
functionality issues.  And a voting candidate for release won't be
made if there are blocker or critical issues assigned to the release.
Ideally we'll only need one actual voting thread per release, unless a
critical or blocker crops up during the vote (particularly around
checking Apache release requirements).

None of this precludes your right to -1 but given also Geertjan's
point above my intention is to keep the vote thread live for the full
72hrs unless a blocking or critical is found in the meantime.

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: [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

[Neil C Smith]

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).

This is confusing but correct - the source and binary NOTICE files are
generated based on what is actually included.  We might have clusters
in the repository that are not in a particular source release.

The copyright year is annoying, and incorrect in 11.0 too - the fix
there missed a file - opened a JIRA ticket for 11.2.

Thanks and 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: Website changes for NB 11.1

[Neil C Smith]

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 information.  It should be on a sub-page though, because
the majority of visitors should not be downloading them.

I'll put together a website PR for this as and when the voting thread passes.

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: Is this design weird

[Neil C Smith]

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 harder. Seems like a low priority bug.

Not Mac specific either, same here.  I assume running the logic to see
if there's a valid target is cheaper on click than every mouse move?!

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: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

[Neil C Smith]

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 (preview) on the website against new
features we know have a few issues?

eg.

JavaEE 8 (preview)
Inline editor hints (preview)

non-LTS releases of Apache NetBeans may include preview features that
while mostly complete might have minor usability issues or require
occasional workarounds (see notes)

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: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

[Neil C Smith]

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
quarterly releases / NetCAT.  I just think that highlighting which new
features are considered to be in that state and not is also useful for
end users though.  Everything else should *hopefully* be just as
stable as NB 11.0! :-)

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: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

[Neil C Smith]

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 will just accumulate from one release to the next. We should see
> this as the first step in the direction of Java EE 8 and use 11.1 to kick
> the tires for 11.2 etc so that when we get to 12, we'll have a really solid
> product around Java EE 8. I haven't yet managed to get the large code
> generation wizards, e.g., from database to REST endpoints, etc, to work in
> Java EE 8, and these kinds of things should be the focus next -- as well as
> getting more people on board to work with Josh, and Gaurav from Payara, on
> these kinds of enhancements.
>

Agreed!  Given particularly these things came in after feature freeze,
we should expect there might be a few rough edges still.  That's not
only fine, IMO, it's also the main reason for having non-LTS.  The key
thing is to tidy up the rough edges by NB 12.0.  And obviously
presenting that clearly to end users via the website.

And we have an AUC.  If we can find a better way to use it, we can
cherry pick and push select updates via the release branch if we
really want/need to.

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: a couple of fixes..

[Neil C Smith]

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 won't
be looked at for merging until the release is out and other master
branch tasks completed.

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: [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

[Neil C Smith]

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 has a different purpose - we should still have something in the
repository itself.  There is an argument for it being the same as in
the source bundle for every cluster though, so it covers the state of
the repository as a whole.

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: Java EE 8 Support Repairs - Enhancements to repair [NETBEANS-2800]

[Neil C Smith]

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

```
... netbeans/enterprise/j2ee.dd/build.xml:341: Replace: source file
...netbeans/enterprise/j2ee.dd/src/org/netbeans/modules/j2ee/dd/impl/web/model_4_0_frag/WebFragment.java
doesn't exist
```

It looks like the .gitignore file at
https://github.com/apache/netbeans/blob/master/enterprise/j2ee.dd/.gitignore
needs updating for the newly generated files too.

I think you're going to have to reset your fork (or delete and create
a new fork), keep master clean and in sync, apply these changes in a
PR-specific branch, check it builds, and resubmit the PR.

Let me know if that's feasible today and I'll hold off beta4 build.  Thanks!

-
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

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

[Neil C Smith]

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.

I'm now going to merge the fix for this issue, and a few other major
issue fixes that are now available, and do a beta4 build for testing.
Once that's ready, please test it to the max and report back (both all
OK or any other issues).  Assuming no further problems, I'll look to
do a second voting candidate and vote early next week.  All being
well, we should be in a position to release towards end of next week.

If you're wondering why beta4 and the difference between beta and vc -
I changed the naming, but not the process, from NB 11.0 so that only
builds that can be voted on for release are suffixed with -vc.  The
betas are much quicker to create because they are not signed and are
linked directly off of the build server rather than committed via svn
to Apache dist - but we can't vote on or release them in that state.

In an ideal world, we will only have one vote and -vc per release to
sanity check Apache release requirements, and all critical/blocking
functionality or policy issues will be picked up in a beta.  All being
well, NB 11.1 will be released off of the same git commit as beta4.

Thanks everyone for all your work on testing and fixing!

Best wishes,

Neil
Volunteer Release Manager for Apache NetBeans 11.1

-
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: [CANCELLED] [VOTE] Release Apache NetBeans 11.1 [vote candidate 1]

[Neil C Smith]

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 suppoprt and JDK 11
>
> That's all, I think.

Plus fix to NOTICES date.  Thanks.  Yes, all in there except for Josh's, so far.

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: [URGENT] Java EE 8 support fixes / beta4?

[Neil C Smith]

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 goes green
I'll merge and do beta4 at some point tomorrow now.

Thanks and 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

[URGENT] Java EE 8 support fixes / beta4?

[Neil C Smith]

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 that locally.

So, we either do beta4 (and therefore release) without this fix, or
delay the beta, get a fresh pair of eyes on this, and hopefully
include it.  I'm going with the latter for now, which means beta4
won't be today.

Full Travis message below.

Thanks, Neil

travis_time:start:204f886a
 [0K$ if [ "x$LICENSE" == "xtrue" ]; then ant -quiet
verify-libs-and-licenses
-Dverify-libs-and-licenses.haltonfailure=true; fi
 [echo] Bootstrapping NetBeans-specific Ant extensions...
 [echo] Downloading external binaries (*/external/ directories)
for cluster.config=release...

BUILD FAILED
/home/travis/build/apache/netbeans/nbbuild/build.xml:1584: Failed
VerifyLibsAndLicenses test(s):
Some binaries were found outside of /external/ directories
(edit nbbuild/antsrc/org/netbeans/nbbuild/extlibs/ignored-binaries as
needed)
scratch/nb/ide.launcher/external/launchers-10.0.zip
scratch/nbbuild/installer/jnlp/external/jnlp-definitions-7.0.jar
scratch/nbbuild/installer/jnlp/external/webstart-jnlp-servlet-1.0-beta-7.jar

-
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: Where do "Third Party Libraries" point to?

[Neil C Smith]

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 
> nbresloc:/org/netbeans/modules/updatecenters/resources/3rdparty-catalog.xml
> . Clicking it does nothing and obviously it doesn't work outside
> NetBeans. Seems very opaque.

Check out -

https://github.com/apache/netbeans/pull/917
https://github.com/apache/netbeans/pull/1159

for a bit of background.

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