You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Neil C Smith <ne...@apache.org> on 2020/05/12 11:02:16 UTC
Potential blocker in 12.0 (and 11.3!)
Hi,
As discussed off-list with Geertjan and Eric, I was just testing the
Jenkins build of 12.0-beta4 before it was announced, and noticed a
potential blocker issue. Interestingly, it's also in 11.3, but not in
11.2.
When importing settings from a previous install (which happens not to
have nb-javac or JavaFX installed), a dialog appears to install them
that gets stuck in a loop if you try to cancel it. I think this
behaviour gets triggered in other ways too, that effectively make
those modules non-optional in some workflows.
It seems this was reported against 11.3 in
https://issues.apache.org/jira/browse/NETBEANS-3810. I remember it at
the time, but it was marked minor and the emphasis was on the
certificate problem rather than the more serious issue that something
regressed between 11.2 and 11.3 that makes it (almost) impossible to
get out of the dialog loop without installing the supposedly optional
modules.
As of yet I haven't looked into what changed in the code that is
triggering this, but I don't think we should release 12.0 with this
issue. I also haven't checked whether this forces the install on Java
14 yet, which would be even more problematic.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Wed, 20 May 2020 at 18:12, Geertjan Wielenga <ge...@apache.org> wrote:
> What is your opinion on this, since you're one of very few who understands
> the scope of this problem: what would you recommend?
I've got a handle on the problems now, but not necessarily the causes!
And delving around JIRA can be a dirty business. :-)
IMO, the simpler the better. I've updated the initial PR with a
couple more slightly ugly changes that reserve the required flag for
the UI, but still let everything proceed on cancellation or failure.
JavaFX is now ticked by default in the wizards again.
https://github.com/apache/netbeans/pull/2135
https://github.com/apache/netbeans/pull/2135/files
Seems to also fix the issue with opening projects mentioned yesterday
in https://lists.apache.org/thread.html/r7ce0738e6bcdfa37c7500ca4b4dc7c82104732d57c8c5cb6cb08bc02%40%3Cusers.netbeans.apache.org%3E
Be good to test if that's enough and we're happy with it for now. It
doesn't stop the dialog with JavaFX and nb-javac showing up together -
that would be a bigger change - but at least it's cancellable. 12.1
could do with some major rethinking around this area.
As mentioned in the comment in the PR, I'd also like to know how to
launch with the debugger and exclude the extras cluster - am I missing
something obvious there? Makes stepping through this rather difficult
as it bypasses the problem!
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
I don't see anyone arguing at this stage that this is not a blocker -- or
at least no one is saying it should not be fixed for 12.0.
What is your opinion on this, since you're one of very few who understands
the scope of this problem: what would you recommend?
Gj
On Wed, May 20, 2020 at 10:09 AM Neil C Smith <ne...@apache.org> wrote:
> On Tue, 12 May 2020 at 12:02, Neil C Smith <ne...@apache.org> wrote:
> >.. I was just testing ... 12.0-beta4 ... and noticed a
> > potential blocker issue.
> > ..
> > When importing settings from a previous install a dialog appears to
> install [JavaFX and nb-javac]
> > that gets stuck in a loop if you try to cancel it.
>
> OK, following up on this here, as requested by Geertjan.
>
> We have multiple possible blocking issues in play triggered by a
> change that has made the JavaFX download required by Java support
> (actually added in 11.3)
>
> The most critical in my opinion is an effective lockup of the IDE on
> first run when the user is unable to establish a network connection to
> download JavaFX (or nb-javac) support from osuosl. We have multiple
> JIRA issues already reported against 11.3 for this (where the problem
> was introduced).
>
> Do we need to somehow move JavaFX back to being recommended, not
> required? The features-on-demand support doesn't handle problems with
> external required dependencies gracefully at all.
>
> There are other issues triggered by this too, including another
> potential blocker with ASF policy on handling of optional Cat X
> dependencies - above also makes it appear impossible to cancel
> acceptance of JavaFX license.
>
> We have neither consensus on a way forward, nor consensus that this is
> actually a blocker. It would be good to try and reach both!
>
> Further info on JIRA issue and linked in issues -
> https://issues.apache.org/jira/browse/NETBEANS-4328
>
> A quote from NETBEANS-3810 I agree with, where downloading failed due
> to network problems - "missing JavaFX and nb-javac should not be a
> blocker for project importing or creation ... If they are, they should
> be bundled with NB. Developers are not lawyers"
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by John Mc <mc...@gmail.com>.
Hi,
I'm still awaiting the INFRA ticket to be actioned, so I can get an Apple
certificate, but I tried building an installer for beta-4 locally (with a
random text file, in place of the certificate file):
./installermac.sh /Users/john/Downloads/netbeans-12.0-beta4-bin.zip
12.0-beta4 200523 "/Users/john/Apache/testCert.txt"
I got the following error:
+ ERROR_CODE=0
+ '[' 0 '!=' 0 ']'
+ ERROR_CODE=0
+ '[' 0 '!=' 0 ']'
+ '[' '!' -z ']'
+ mv
/Users/john/Apache/WIP/12.0-beta4/distpreparation/netbeans/installer/dist/installers/bundles
/Users/john/Apache/WIP/12.0-beta4/distpreparation/netbeans/installer/dist
+ rmdir
/Users/john/Apache/WIP/12.0-beta4/distpreparation/netbeans/installer/dist/installers
+ '[' '!' -z ']'
+ '[' '!' -z 1 ']'
+ rsync -avz
'/Users/john/Apache/WIP/12.0-beta4/distpreparation/netbeans/installer/nbbuild/installer/mac/newbuild/dist_en/*.dmg'
/Users/john/Apache/WIP/12.0-beta4/distpreparation/netbeans/installer/dist/bundles
building file list ... rsync: link_stat
"/Users/john/Apache/WIP/12.0-beta4/distpreparation/netbeans/installer/nbbuild/installer/mac/newbuild/dist_en/*.dmg"
failed: No such file or directory (2)
done
sent 29 bytes received 20 bytes 98.00 bytes/sec
total size is 0 speedup is 0.00
rsync error: some files could not be transferred (code 23) at
/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54/rsync/main.c(996)
[sender=2.6.9]
+ ERROR_CODE=23
+ '[' 23 '!=' 0 ']'
+ exit 23
I'll investigate this tomorrow after work (might be that the test
certification file I'm using is the reason why its not working)...
We have at least a beta-5 and around another week or so of testing this,
correct? Just want to make sure I have this resolved in time to avoid any
delays...
Regards
John
On Sat, 23 May 2020 at 06:20, Geertjan Wielenga <ge...@apache.org> wrote:
> Very nice, thank you!
>
> Gj
>
> On Sat, 23 May 2020 at 01:38, John Mc <mc...@gmail.com> wrote:
>
> > Hi,
> >
> > I've found the information I need, and have made the appropriate request
> to
> > the Infrastructure Team. I should be able to take on the Mac OSX
> installer
> > aspect for 12.0
> >
> > Regards
> >
> > John
> >
> > On Fri, 22 May 2020 at 22:22, John Mc <mc...@gmail.com> wrote:
> >
> > > Hi Eric/Geertjan,
> > >
> > > I was looking at whats involved here and I believe, we need someone
> with
> > > an Apple Developer Account which requires a yearly subscription fee of
> > €99.
> > >
> > > Is there an "Apache", or "Apache NetBeans" Apple Developer Account,
> that
> > > was used previously? With this account, you gain access to a
> "Developer
> > ID
> > > Installer" certificate which I'm guessing is the same as an "Apple
> > > Developer Installer Certificate" as that is mentioned in [1], and I
> have
> > > found no record of this listed anywhere...
> > >
> > > Whose certificate was used for the 11.X releases? Was this a personal
> > one
> > > or an Apache/NetBeans certificate?
> > >
> > > [1]:
> > >
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps
> > >
> > > Regards
> > >
> > > John
> > >
> > > On Fri, 22 May 2020 at 19:26, Geertjan Wielenga <ge...@apache.org>
> > > wrote:
> > >
> > >> I use a Mac, if you can point me in the right direction, I can do the
> > >> installer build and sign, unless someone else volunteers.
> > >>
> > >> Gj
> > >>
> > >> On Fri, 22 May 2020 at 11:59, Eric Barboni <sk...@apache.org> wrote:
> > >>
> > >> > Hi,
> > >> > Sorry for the delay. We are a bit late but what can we do against.
> > >> >
> > >> > The blocker was detected by Neil but Jaroslav first vetoed the
> > changes
> > >> > (maybe I overinterpret that but -1 on PR looks like a veto). By the
> > way
> > >> > Jaroslav change his mind. This fix is only a first step as far I
> know.
> > >> >
> > >> > It's better to have maybe until Wednesday or Friday the beta running
> > to
> > >> > avoid having to generate fix day one.
> > >> >
> > >> > If we can merge Neil PR, the beta can be at the end of the day.
> > >> >
> > >> > Best Regards
> > >> > Eric
> > >> >
> > >> > !!! help !!!
> > >> > And still important I have no volunteer to 12.0 macos installer
> build
> > >> and
> > >> > sign. (need to be a PMC, and I have no mac to do that :/ )
> > >> >
> > >> >
> > >> > -----Message d'origine-----
> > >> > De : Geertjan Wielenga <ge...@apache.org>
> > >> > Envoyé : jeudi 21 mai 2020 21:13
> > >> > À : dev@netbeans.apache.org
> > >> > Objet : Re: Potential blocker in 12.0 (and 11.3!)
> > >> >
> > >> > Thanks, great. Let’s see Eric’s response to this indeed.
> > >> >
> > >> > Gj
> > >> >
> > >> > On Thu, 21 May 2020 at 10:47, Neil C Smith <ne...@apache.org>
> > >> wrote:
> > >> >
> > >> > > On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <
> > geertjan@apache.org>
> > >> > > wrote:
> > >> > > > I must add that a sign of a big breakthrough in NetBeans
> progress
> > is
> > >> > > > historically always right at the point of my greatest despair —
> > >> > > > which is good because that point is now: we’ve missed our
> release
> > >> > > > date, might not make it at all this month, which will have knock
> > on
> > >> > effects.
> > >> > >
> > >> > > There's plenty else of concern in the world right now to be
> > despairing
> > >> > > on this. And the release window is May 15-31 anyway - we haven't
> > >> > > missed it yet, although probably be tight.
> > >> > >
> > >> > > > I propose we accept Neil’s minimal solution that at least solves
> > the
> > >> > > > problem, that Eric includes it in a beta 5 to be released by
> > Monday,
> > >> > > > and that we use that to start voting immediately, aiming in a
> very
> > >> > > > best case scenario to release end of next week.
> > >> > >
> > >> > > Final call on this is up to Eric, but -1 from me. We can't vote
> on
> > >> > > the beta build anyway, and I'm in favour of having a week of beta5
> > >> > > before voting - there are a range of other fixes to test in there
> > too,
> > >> > > and let's make sure this isn't still causing problems. We tried
> > >> > > rushing changes directly into a vote with 11.1, and it was a false
> > >> > > economy - it ended up taking almost a fortnight longer.
> > >> > >
> > >> > > We could all take the time that beta is being tested to ensure
> we've
> > >> > > checked all the "paperwork" though - we can all build it from
> > source,
> > >> > > do notice, binary checks, etc. and make sure there's nothing there
> > >> > > that might cause issues in the vote.
> > >> > >
> > >> > > All being well vc1 will then just be a retagged beta5, and we
> might
> > >> > > still just scrape May 31st if we can get beta build done this
> week.
> > >> > >
> > >> > > Best wishes,
> > >> > >
> > >> > > Neil
> > >> > >
> > >> > >
> > ---------------------------------------------------------------------
> > >> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > >> > > For additional commands, e-mail: dev-help@netbeans.apache.org
> > >> > >
> > >> > > For further information about the NetBeans mailing lists, visit:
> > >> > >
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >> > >
> > >> > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > >> > For additional commands, e-mail: dev-help@netbeans.apache.org
> > >> >
> > >> > For further information about the NetBeans mailing lists, visit:
> > >> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >> >
> > >> >
> > >> >
> > >> >
> > >>
> > >
> >
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
Very nice, thank you!
Gj
On Sat, 23 May 2020 at 01:38, John Mc <mc...@gmail.com> wrote:
> Hi,
>
> I've found the information I need, and have made the appropriate request to
> the Infrastructure Team. I should be able to take on the Mac OSX installer
> aspect for 12.0
>
> Regards
>
> John
>
> On Fri, 22 May 2020 at 22:22, John Mc <mc...@gmail.com> wrote:
>
> > Hi Eric/Geertjan,
> >
> > I was looking at whats involved here and I believe, we need someone with
> > an Apple Developer Account which requires a yearly subscription fee of
> €99.
> >
> > Is there an "Apache", or "Apache NetBeans" Apple Developer Account, that
> > was used previously? With this account, you gain access to a "Developer
> ID
> > Installer" certificate which I'm guessing is the same as an "Apple
> > Developer Installer Certificate" as that is mentioned in [1], and I have
> > found no record of this listed anywhere...
> >
> > Whose certificate was used for the 11.X releases? Was this a personal
> one
> > or an Apache/NetBeans certificate?
> >
> > [1]:
> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps
> >
> > Regards
> >
> > John
> >
> > On Fri, 22 May 2020 at 19:26, Geertjan Wielenga <ge...@apache.org>
> > wrote:
> >
> >> I use a Mac, if you can point me in the right direction, I can do the
> >> installer build and sign, unless someone else volunteers.
> >>
> >> Gj
> >>
> >> On Fri, 22 May 2020 at 11:59, Eric Barboni <sk...@apache.org> wrote:
> >>
> >> > Hi,
> >> > Sorry for the delay. We are a bit late but what can we do against.
> >> >
> >> > The blocker was detected by Neil but Jaroslav first vetoed the
> changes
> >> > (maybe I overinterpret that but -1 on PR looks like a veto). By the
> way
> >> > Jaroslav change his mind. This fix is only a first step as far I know.
> >> >
> >> > It's better to have maybe until Wednesday or Friday the beta running
> to
> >> > avoid having to generate fix day one.
> >> >
> >> > If we can merge Neil PR, the beta can be at the end of the day.
> >> >
> >> > Best Regards
> >> > Eric
> >> >
> >> > !!! help !!!
> >> > And still important I have no volunteer to 12.0 macos installer build
> >> and
> >> > sign. (need to be a PMC, and I have no mac to do that :/ )
> >> >
> >> >
> >> > -----Message d'origine-----
> >> > De : Geertjan Wielenga <ge...@apache.org>
> >> > Envoyé : jeudi 21 mai 2020 21:13
> >> > À : dev@netbeans.apache.org
> >> > Objet : Re: Potential blocker in 12.0 (and 11.3!)
> >> >
> >> > Thanks, great. Let’s see Eric’s response to this indeed.
> >> >
> >> > Gj
> >> >
> >> > On Thu, 21 May 2020 at 10:47, Neil C Smith <ne...@apache.org>
> >> wrote:
> >> >
> >> > > On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <
> geertjan@apache.org>
> >> > > wrote:
> >> > > > I must add that a sign of a big breakthrough in NetBeans progress
> is
> >> > > > historically always right at the point of my greatest despair —
> >> > > > which is good because that point is now: we’ve missed our release
> >> > > > date, might not make it at all this month, which will have knock
> on
> >> > effects.
> >> > >
> >> > > There's plenty else of concern in the world right now to be
> despairing
> >> > > on this. And the release window is May 15-31 anyway - we haven't
> >> > > missed it yet, although probably be tight.
> >> > >
> >> > > > I propose we accept Neil’s minimal solution that at least solves
> the
> >> > > > problem, that Eric includes it in a beta 5 to be released by
> Monday,
> >> > > > and that we use that to start voting immediately, aiming in a very
> >> > > > best case scenario to release end of next week.
> >> > >
> >> > > Final call on this is up to Eric, but -1 from me. We can't vote on
> >> > > the beta build anyway, and I'm in favour of having a week of beta5
> >> > > before voting - there are a range of other fixes to test in there
> too,
> >> > > and let's make sure this isn't still causing problems. We tried
> >> > > rushing changes directly into a vote with 11.1, and it was a false
> >> > > economy - it ended up taking almost a fortnight longer.
> >> > >
> >> > > We could all take the time that beta is being tested to ensure we've
> >> > > checked all the "paperwork" though - we can all build it from
> source,
> >> > > do notice, binary checks, etc. and make sure there's nothing there
> >> > > that might cause issues in the vote.
> >> > >
> >> > > All being well vc1 will then just be a retagged beta5, and we might
> >> > > still just scrape May 31st if we can get beta build done this week.
> >> > >
> >> > > Best wishes,
> >> > >
> >> > > Neil
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> > > For additional commands, e-mail: dev-help@netbeans.apache.org
> >> > >
> >> > > For further information about the NetBeans mailing lists, visit:
> >> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >> > >
> >> > >
> >> > >
> >> > >
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >> >
> >> > For further information about the NetBeans mailing lists, visit:
> >> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >> >
> >> >
> >> >
> >> >
> >>
> >
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by John Mc <mc...@gmail.com>.
Hi,
I've found the information I need, and have made the appropriate request to
the Infrastructure Team. I should be able to take on the Mac OSX installer
aspect for 12.0
Regards
John
On Fri, 22 May 2020 at 22:22, John Mc <mc...@gmail.com> wrote:
> Hi Eric/Geertjan,
>
> I was looking at whats involved here and I believe, we need someone with
> an Apple Developer Account which requires a yearly subscription fee of €99.
>
> Is there an "Apache", or "Apache NetBeans" Apple Developer Account, that
> was used previously? With this account, you gain access to a "Developer ID
> Installer" certificate which I'm guessing is the same as an "Apple
> Developer Installer Certificate" as that is mentioned in [1], and I have
> found no record of this listed anywhere...
>
> Whose certificate was used for the 11.X releases? Was this a personal one
> or an Apache/NetBeans certificate?
>
> [1]:
> https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps
>
> Regards
>
> John
>
> On Fri, 22 May 2020 at 19:26, Geertjan Wielenga <ge...@apache.org>
> wrote:
>
>> I use a Mac, if you can point me in the right direction, I can do the
>> installer build and sign, unless someone else volunteers.
>>
>> Gj
>>
>> On Fri, 22 May 2020 at 11:59, Eric Barboni <sk...@apache.org> wrote:
>>
>> > Hi,
>> > Sorry for the delay. We are a bit late but what can we do against.
>> >
>> > The blocker was detected by Neil but Jaroslav first vetoed the changes
>> > (maybe I overinterpret that but -1 on PR looks like a veto). By the way
>> > Jaroslav change his mind. This fix is only a first step as far I know.
>> >
>> > It's better to have maybe until Wednesday or Friday the beta running to
>> > avoid having to generate fix day one.
>> >
>> > If we can merge Neil PR, the beta can be at the end of the day.
>> >
>> > Best Regards
>> > Eric
>> >
>> > !!! help !!!
>> > And still important I have no volunteer to 12.0 macos installer build
>> and
>> > sign. (need to be a PMC, and I have no mac to do that :/ )
>> >
>> >
>> > -----Message d'origine-----
>> > De : Geertjan Wielenga <ge...@apache.org>
>> > Envoyé : jeudi 21 mai 2020 21:13
>> > À : dev@netbeans.apache.org
>> > Objet : Re: Potential blocker in 12.0 (and 11.3!)
>> >
>> > Thanks, great. Let’s see Eric’s response to this indeed.
>> >
>> > Gj
>> >
>> > On Thu, 21 May 2020 at 10:47, Neil C Smith <ne...@apache.org>
>> wrote:
>> >
>> > > On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <ge...@apache.org>
>> > > wrote:
>> > > > I must add that a sign of a big breakthrough in NetBeans progress is
>> > > > historically always right at the point of my greatest despair —
>> > > > which is good because that point is now: we’ve missed our release
>> > > > date, might not make it at all this month, which will have knock on
>> > effects.
>> > >
>> > > There's plenty else of concern in the world right now to be despairing
>> > > on this. And the release window is May 15-31 anyway - we haven't
>> > > missed it yet, although probably be tight.
>> > >
>> > > > I propose we accept Neil’s minimal solution that at least solves the
>> > > > problem, that Eric includes it in a beta 5 to be released by Monday,
>> > > > and that we use that to start voting immediately, aiming in a very
>> > > > best case scenario to release end of next week.
>> > >
>> > > Final call on this is up to Eric, but -1 from me. We can't vote on
>> > > the beta build anyway, and I'm in favour of having a week of beta5
>> > > before voting - there are a range of other fixes to test in there too,
>> > > and let's make sure this isn't still causing problems. We tried
>> > > rushing changes directly into a vote with 11.1, and it was a false
>> > > economy - it ended up taking almost a fortnight longer.
>> > >
>> > > We could all take the time that beta is being tested to ensure we've
>> > > checked all the "paperwork" though - we can all build it from source,
>> > > do notice, binary checks, etc. and make sure there's nothing there
>> > > that might cause issues in the vote.
>> > >
>> > > All being well vc1 will then just be a retagged beta5, and we might
>> > > still just scrape May 31st if we can get beta build done this week.
>> > >
>> > > Best wishes,
>> > >
>> > > Neil
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> > > For additional commands, e-mail: dev-help@netbeans.apache.org
>> > >
>> > > For further information about the NetBeans mailing lists, visit:
>> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> > >
>> > >
>> > >
>> > >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> > For additional commands, e-mail: dev-help@netbeans.apache.org
>> >
>> > For further information about the NetBeans mailing lists, visit:
>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> >
>> >
>> >
>> >
>>
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by John Mc <mc...@gmail.com>.
Hi Eric/Geertjan,
I was looking at whats involved here and I believe, we need someone with an
Apple Developer Account which requires a yearly subscription fee of €99.
Is there an "Apache", or "Apache NetBeans" Apple Developer Account, that
was used previously? With this account, you gain access to a "Developer ID
Installer" certificate which I'm guessing is the same as an "Apple
Developer Installer Certificate" as that is mentioned in [1], and I have
found no record of this listed anywhere...
Whose certificate was used for the 11.X releases? Was this a personal one
or an Apache/NetBeans certificate?
[1]:
https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps
Regards
John
On Fri, 22 May 2020 at 19:26, Geertjan Wielenga <ge...@apache.org> wrote:
> I use a Mac, if you can point me in the right direction, I can do the
> installer build and sign, unless someone else volunteers.
>
> Gj
>
> On Fri, 22 May 2020 at 11:59, Eric Barboni <sk...@apache.org> wrote:
>
> > Hi,
> > Sorry for the delay. We are a bit late but what can we do against.
> >
> > The blocker was detected by Neil but Jaroslav first vetoed the changes
> > (maybe I overinterpret that but -1 on PR looks like a veto). By the way
> > Jaroslav change his mind. This fix is only a first step as far I know.
> >
> > It's better to have maybe until Wednesday or Friday the beta running to
> > avoid having to generate fix day one.
> >
> > If we can merge Neil PR, the beta can be at the end of the day.
> >
> > Best Regards
> > Eric
> >
> > !!! help !!!
> > And still important I have no volunteer to 12.0 macos installer build and
> > sign. (need to be a PMC, and I have no mac to do that :/ )
> >
> >
> > -----Message d'origine-----
> > De : Geertjan Wielenga <ge...@apache.org>
> > Envoyé : jeudi 21 mai 2020 21:13
> > À : dev@netbeans.apache.org
> > Objet : Re: Potential blocker in 12.0 (and 11.3!)
> >
> > Thanks, great. Let’s see Eric’s response to this indeed.
> >
> > Gj
> >
> > On Thu, 21 May 2020 at 10:47, Neil C Smith <ne...@apache.org>
> wrote:
> >
> > > On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <ge...@apache.org>
> > > wrote:
> > > > I must add that a sign of a big breakthrough in NetBeans progress is
> > > > historically always right at the point of my greatest despair —
> > > > which is good because that point is now: we’ve missed our release
> > > > date, might not make it at all this month, which will have knock on
> > effects.
> > >
> > > There's plenty else of concern in the world right now to be despairing
> > > on this. And the release window is May 15-31 anyway - we haven't
> > > missed it yet, although probably be tight.
> > >
> > > > I propose we accept Neil’s minimal solution that at least solves the
> > > > problem, that Eric includes it in a beta 5 to be released by Monday,
> > > > and that we use that to start voting immediately, aiming in a very
> > > > best case scenario to release end of next week.
> > >
> > > Final call on this is up to Eric, but -1 from me. We can't vote on
> > > the beta build anyway, and I'm in favour of having a week of beta5
> > > before voting - there are a range of other fixes to test in there too,
> > > and let's make sure this isn't still causing problems. We tried
> > > rushing changes directly into a vote with 11.1, and it was a false
> > > economy - it ended up taking almost a fortnight longer.
> > >
> > > We could all take the time that beta is being tested to ensure we've
> > > checked all the "paperwork" though - we can all build it from source,
> > > do notice, binary checks, etc. and make sure there's nothing there
> > > that might cause issues in the vote.
> > >
> > > All being well vc1 will then just be a retagged beta5, and we might
> > > still just scrape May 31st if we can get beta build done this week.
> > >
> > > Best wishes,
> > >
> > > Neil
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > > For additional commands, e-mail: dev-help@netbeans.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
I use a Mac, if you can point me in the right direction, I can do the
installer build and sign, unless someone else volunteers.
Gj
On Fri, 22 May 2020 at 11:59, Eric Barboni <sk...@apache.org> wrote:
> Hi,
> Sorry for the delay. We are a bit late but what can we do against.
>
> The blocker was detected by Neil but Jaroslav first vetoed the changes
> (maybe I overinterpret that but -1 on PR looks like a veto). By the way
> Jaroslav change his mind. This fix is only a first step as far I know.
>
> It's better to have maybe until Wednesday or Friday the beta running to
> avoid having to generate fix day one.
>
> If we can merge Neil PR, the beta can be at the end of the day.
>
> Best Regards
> Eric
>
> !!! help !!!
> And still important I have no volunteer to 12.0 macos installer build and
> sign. (need to be a PMC, and I have no mac to do that :/ )
>
>
> -----Message d'origine-----
> De : Geertjan Wielenga <ge...@apache.org>
> Envoyé : jeudi 21 mai 2020 21:13
> À : dev@netbeans.apache.org
> Objet : Re: Potential blocker in 12.0 (and 11.3!)
>
> Thanks, great. Let’s see Eric’s response to this indeed.
>
> Gj
>
> On Thu, 21 May 2020 at 10:47, Neil C Smith <ne...@apache.org> wrote:
>
> > On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <ge...@apache.org>
> > wrote:
> > > I must add that a sign of a big breakthrough in NetBeans progress is
> > > historically always right at the point of my greatest despair —
> > > which is good because that point is now: we’ve missed our release
> > > date, might not make it at all this month, which will have knock on
> effects.
> >
> > There's plenty else of concern in the world right now to be despairing
> > on this. And the release window is May 15-31 anyway - we haven't
> > missed it yet, although probably be tight.
> >
> > > I propose we accept Neil’s minimal solution that at least solves the
> > > problem, that Eric includes it in a beta 5 to be released by Monday,
> > > and that we use that to start voting immediately, aiming in a very
> > > best case scenario to release end of next week.
> >
> > Final call on this is up to Eric, but -1 from me. We can't vote on
> > the beta build anyway, and I'm in favour of having a week of beta5
> > before voting - there are a range of other fixes to test in there too,
> > and let's make sure this isn't still causing problems. We tried
> > rushing changes directly into a vote with 11.1, and it was a false
> > economy - it ended up taking almost a fortnight longer.
> >
> > We could all take the time that beta is being tested to ensure we've
> > checked all the "paperwork" though - we can all build it from source,
> > do notice, binary checks, etc. and make sure there's nothing there
> > that might cause issues in the vote.
> >
> > All being well vc1 will then just be a retagged beta5, and we might
> > still just scrape May 31st if we can get beta build done this week.
> >
> > Best wishes,
> >
> > Neil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
RE: Potential blocker in 12.0 (and 11.3!)
Posted by Eric Barboni <sk...@apache.org>.
Hi,
Sorry for the delay. We are a bit late but what can we do against.
The blocker was detected by Neil but Jaroslav first vetoed the changes (maybe I overinterpret that but -1 on PR looks like a veto). By the way Jaroslav change his mind. This fix is only a first step as far I know.
It's better to have maybe until Wednesday or Friday the beta running to avoid having to generate fix day one.
If we can merge Neil PR, the beta can be at the end of the day.
Best Regards
Eric
!!! help !!!
And still important I have no volunteer to 12.0 macos installer build and sign. (need to be a PMC, and I have no mac to do that :/ )
-----Message d'origine-----
De : Geertjan Wielenga <ge...@apache.org>
Envoyé : jeudi 21 mai 2020 21:13
À : dev@netbeans.apache.org
Objet : Re: Potential blocker in 12.0 (and 11.3!)
Thanks, great. Let’s see Eric’s response to this indeed.
Gj
On Thu, 21 May 2020 at 10:47, Neil C Smith <ne...@apache.org> wrote:
> On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <ge...@apache.org>
> wrote:
> > I must add that a sign of a big breakthrough in NetBeans progress is
> > historically always right at the point of my greatest despair —
> > which is good because that point is now: we’ve missed our release
> > date, might not make it at all this month, which will have knock on effects.
>
> There's plenty else of concern in the world right now to be despairing
> on this. And the release window is May 15-31 anyway - we haven't
> missed it yet, although probably be tight.
>
> > I propose we accept Neil’s minimal solution that at least solves the
> > problem, that Eric includes it in a beta 5 to be released by Monday,
> > and that we use that to start voting immediately, aiming in a very
> > best case scenario to release end of next week.
>
> Final call on this is up to Eric, but -1 from me. We can't vote on
> the beta build anyway, and I'm in favour of having a week of beta5
> before voting - there are a range of other fixes to test in there too,
> and let's make sure this isn't still causing problems. We tried
> rushing changes directly into a vote with 11.1, and it was a false
> economy - it ended up taking almost a fortnight longer.
>
> We could all take the time that beta is being tested to ensure we've
> checked all the "paperwork" though - we can all build it from source,
> do notice, binary checks, etc. and make sure there's nothing there
> that might cause issues in the vote.
>
> All being well vc1 will then just be a retagged beta5, and we might
> still just scrape May 31st if we can get beta build done this week.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
Thanks, great. Let’s see Eric’s response to this indeed.
Gj
On Thu, 21 May 2020 at 10:47, Neil C Smith <ne...@apache.org> wrote:
> On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <ge...@apache.org>
> wrote:
> > I must add that a sign of a big breakthrough in NetBeans progress is
> > historically always right at the point of my greatest despair — which is
> > good because that point is now: we’ve missed our release date, might not
> > make it at all this month, which will have knock on effects.
>
> There's plenty else of concern in the world right now to be despairing
> on this. And the release window is May 15-31 anyway - we haven't
> missed it yet, although probably be tight.
>
> > I propose we accept Neil’s minimal solution that at least solves the
> > problem, that Eric includes it in a beta 5 to be released by Monday, and
> > that we use that to start voting immediately, aiming in a very best case
> > scenario to release end of next week.
>
> Final call on this is up to Eric, but -1 from me. We can't vote on
> the beta build anyway, and I'm in favour of having a week of beta5
> before voting - there are a range of other fixes to test in there too,
> and let's make sure this isn't still causing problems. We tried
> rushing changes directly into a vote with 11.1, and it was a false
> economy - it ended up taking almost a fortnight longer.
>
> We could all take the time that beta is being tested to ensure we've
> checked all the "paperwork" though - we can all build it from source,
> do notice, binary checks, etc. and make sure there's nothing there
> that might cause issues in the vote.
>
> All being well vc1 will then just be a retagged beta5, and we might
> still just scrape May 31st if we can get beta build done this week.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 21 May 2020 at 06:08, Geertjan Wielenga <ge...@apache.org> wrote:
> I must add that a sign of a big breakthrough in NetBeans progress is
> historically always right at the point of my greatest despair — which is
> good because that point is now: we’ve missed our release date, might not
> make it at all this month, which will have knock on effects.
There's plenty else of concern in the world right now to be despairing
on this. And the release window is May 15-31 anyway - we haven't
missed it yet, although probably be tight.
> I propose we accept Neil’s minimal solution that at least solves the
> problem, that Eric includes it in a beta 5 to be released by Monday, and
> that we use that to start voting immediately, aiming in a very best case
> scenario to release end of next week.
Final call on this is up to Eric, but -1 from me. We can't vote on
the beta build anyway, and I'm in favour of having a week of beta5
before voting - there are a range of other fixes to test in there too,
and let's make sure this isn't still causing problems. We tried
rushing changes directly into a vote with 11.1, and it was a false
economy - it ended up taking almost a fortnight longer.
We could all take the time that beta is being tested to ensure we've
checked all the "paperwork" though - we can all build it from source,
do notice, binary checks, etc. and make sure there's nothing there
that might cause issues in the vote.
All being well vc1 will then just be a retagged beta5, and we might
still just scrape May 31st if we can get beta build done this week.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
I must add that a sign of a big breakthrough in NetBeans progress is
historically always right at the point of my greatest despair — which is
good because that point is now: we’ve missed our release date, might not
make it at all this month, which will have knock on effects.
I propose we accept Neil’s minimal solution that at least solves the
problem, that Eric includes it in a beta 5 to be released by Monday, and
that we use that to start voting immediately, aiming in a very best case
scenario to release end of next week.
Gj
On Wed, 20 May 2020 at 23:41, Geertjan Wielenga <ge...@apache.org> wrote:
> Yeah, I don't think we should discuss anymore if but how this should be
> fixed, especially given this is an LTS release.
>
> Gj
>
> On Wed, May 20, 2020 at 11:24 PM Neil C Smith <ne...@apache.org>
> wrote:
>
>> On Wed, 20 May 2020, 20:09 Matthias Bläsing, <mb...@doppel-helix.eu>
>> wrote:
>>
>> > this is not true. The problem exist since the first release of Apache
>> > NetBeans. nbjavac was required on all JDKs and is now required on JDK
>> > 8.
>>
>>
>> It is true if we're talking about the same thing - nb-javac has never been
>> required *via ergonomics* on any JDK but 8. See
>> https://github.com/apache/netbeans/pull/715
>>
>> Yes, the same bug potentially affects JDK 8 with nb-javac too. Although my
>> proposed change would stop it erroring there too.
>>
>>
>> > With the addition of JavaFX the situation got a bit worse, but only
>> > gradually. If we could just bundle our dependencies ...
>> >
>>
>> We are in agreement here, but right now that's not an option ...
>>
>>
>> > The download for JavaFX comes from maven central (yes I know, that even
>> > maven central is down at times).
>> >
>>
>> True! But network problems don't just apply to the server end. Because
>> this
>> effectively brings nb-javac along for the required ride too, I think
>> failures to download that also come into play, judging from some reports.
>>
>>
>> > From my perspective NetBeans works as well as for example a maven build
>> > works, that has dependencies not yet present in a local repository.
>> >
>>
>> Good! I'm sure the people who have reported issues or been confused by
>> this
>> are happy about that. ;-) It's not a problem for me either because I know
>> how to work around it. But comparing Maven to a GUI that effectively locks
>> up isn't a fair one.
>>
>> I noticed this issue when trying to test JDK 14 and it surprised me, so I
>> went looking for reports, and found a few. Given it has only been a
>> problem
>> since 11.3, I'd expect more if we release with 12.0. It's been the problem
>> behind two threads on users@ in the last 24 hours.
>>
>> Best wishes,
>>
>> Neil
>>
>> >
>>
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
Yeah, I don't think we should discuss anymore if but how this should be
fixed, especially given this is an LTS release.
Gj
On Wed, May 20, 2020 at 11:24 PM Neil C Smith <ne...@apache.org> wrote:
> On Wed, 20 May 2020, 20:09 Matthias Bläsing, <mb...@doppel-helix.eu>
> wrote:
>
> > this is not true. The problem exist since the first release of Apache
> > NetBeans. nbjavac was required on all JDKs and is now required on JDK
> > 8.
>
>
> It is true if we're talking about the same thing - nb-javac has never been
> required *via ergonomics* on any JDK but 8. See
> https://github.com/apache/netbeans/pull/715
>
> Yes, the same bug potentially affects JDK 8 with nb-javac too. Although my
> proposed change would stop it erroring there too.
>
>
> > With the addition of JavaFX the situation got a bit worse, but only
> > gradually. If we could just bundle our dependencies ...
> >
>
> We are in agreement here, but right now that's not an option ...
>
>
> > The download for JavaFX comes from maven central (yes I know, that even
> > maven central is down at times).
> >
>
> True! But network problems don't just apply to the server end. Because this
> effectively brings nb-javac along for the required ride too, I think
> failures to download that also come into play, judging from some reports.
>
>
> > From my perspective NetBeans works as well as for example a maven build
> > works, that has dependencies not yet present in a local repository.
> >
>
> Good! I'm sure the people who have reported issues or been confused by this
> are happy about that. ;-) It's not a problem for me either because I know
> how to work around it. But comparing Maven to a GUI that effectively locks
> up isn't a fair one.
>
> I noticed this issue when trying to test JDK 14 and it surprised me, so I
> went looking for reports, and found a few. Given it has only been a problem
> since 11.3, I'd expect more if we release with 12.0. It's been the problem
> behind two threads on users@ in the last 24 hours.
>
> Best wishes,
>
> Neil
>
> >
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Wed, 20 May 2020, 20:09 Matthias Bläsing, <mb...@doppel-helix.eu>
wrote:
> this is not true. The problem exist since the first release of Apache
> NetBeans. nbjavac was required on all JDKs and is now required on JDK
> 8.
It is true if we're talking about the same thing - nb-javac has never been
required *via ergonomics* on any JDK but 8. See
https://github.com/apache/netbeans/pull/715
Yes, the same bug potentially affects JDK 8 with nb-javac too. Although my
proposed change would stop it erroring there too.
> With the addition of JavaFX the situation got a bit worse, but only
> gradually. If we could just bundle our dependencies ...
>
We are in agreement here, but right now that's not an option ...
> The download for JavaFX comes from maven central (yes I know, that even
> maven central is down at times).
>
True! But network problems don't just apply to the server end. Because this
effectively brings nb-javac along for the required ride too, I think
failures to download that also come into play, judging from some reports.
> From my perspective NetBeans works as well as for example a maven build
> works, that has dependencies not yet present in a local repository.
>
Good! I'm sure the people who have reported issues or been confused by this
are happy about that. ;-) It's not a problem for me either because I know
how to work around it. But comparing Maven to a GUI that effectively locks
up isn't a fair one.
I noticed this issue when trying to test JDK 14 and it surprised me, so I
went looking for reports, and found a few. Given it has only been a problem
since 11.3, I'd expect more if we release with 12.0. It's been the problem
behind two threads on users@ in the last 24 hours.
Best wishes,
Neil
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi,
Am Mittwoch, den 20.05.2020, 09:08 +0100 schrieb Neil C Smith:
> On Tue, 12 May 2020 at 12:02, Neil C Smith <ne...@apache.org>
> wrote:
> > .. I was just testing ... 12.0-beta4 ... and noticed a
> > potential blocker issue.
> > ..
> > When importing settings from a previous install a dialog appears to
> > install [JavaFX and nb-javac]
> > that gets stuck in a loop if you try to cancel it.
>
> OK, following up on this here, as requested by Geertjan.
>
> We have multiple possible blocking issues in play triggered by a
> change that has made the JavaFX download required by Java support
> (actually added in 11.3)
>
> The most critical in my opinion is an effective lockup of the IDE on
> first run when the user is unable to establish a network connection to
> download JavaFX (or nb-javac) support from osuosl. We have multiple
> JIRA issues already reported against 11.3 for this (where the problem
> was introduced).
>
this is not true. The problem exist since the first release of Apache
NetBeans. nbjavac was required on all JDKs and is now required on JDK
8. It is by far "recommend", but required. So if nbjavac did not
magically reach the system of the user, it was downloaded. If I'm not
mistaken the same was true for the js parser, not sure when that was
replaced by the UPL licensed version.
With the addition of JavaFX the situation got a bit worse, but only
gradually. If we could just bundle our dependencies ...
The download for JavaFX comes from maven central (yes I know, that even
maven central is down at times).
From my perspective NetBeans works as well as for example a maven build
works, that has dependencies not yet present in a local repository.
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 12 May 2020 at 12:02, Neil C Smith <ne...@apache.org> wrote:
>.. I was just testing ... 12.0-beta4 ... and noticed a
> potential blocker issue.
> ..
> When importing settings from a previous install a dialog appears to install [JavaFX and nb-javac]
> that gets stuck in a loop if you try to cancel it.
OK, following up on this here, as requested by Geertjan.
We have multiple possible blocking issues in play triggered by a
change that has made the JavaFX download required by Java support
(actually added in 11.3)
The most critical in my opinion is an effective lockup of the IDE on
first run when the user is unable to establish a network connection to
download JavaFX (or nb-javac) support from osuosl. We have multiple
JIRA issues already reported against 11.3 for this (where the problem
was introduced).
Do we need to somehow move JavaFX back to being recommended, not
required? The features-on-demand support doesn't handle problems with
external required dependencies gracefully at all.
There are other issues triggered by this too, including another
potential blocker with ASF policy on handling of optional Cat X
dependencies - above also makes it appear impossible to cancel
acceptance of JavaFX license.
We have neither consensus on a way forward, nor consensus that this is
actually a blocker. It would be good to try and reach both!
Further info on JIRA issue and linked in issues -
https://issues.apache.org/jira/browse/NETBEANS-4328
A quote from NETBEANS-3810 I agree with, where downloading failed due
to network problems - "missing JavaFX and nb-javac should not be a
blocker for project importing or creation ... If they are, they should
be bundled with NB. Developers are not lawyers"
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
Hi,
On Tue, 12 May 2020 at 14:17, Geertjan Wielenga <ge...@apache.org> wrote:
>
> It sounds like this nb-javac/javafx dialog is showing up in undesired
> places.
>
> I started 11.3 with a fresh userdir, did not enable anything, opened the
> Favorites window, double-clicked a JAR, and there that dialog was as well.
Yes, and some predate 11.3 - interesting one if you click on Java in
Tools / Options (first task, clean userdir, no settings import). Wait
for ergonomics to kick in and reopen the dialog, then click on Maven
tab.
I understand why we have ergonomics, but given the number of headaches
it's caused, it's also my least favourite feature!
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Wed, 13 May 2020 at 12:05, Neil C Smith <ne...@apache.org> wrote:
> On Tue, 12 May 2020 at 14:17, Geertjan Wielenga <ge...@apache.org> wrote:
> > It sounds like this nb-javac/javafx dialog is showing up in undesired
> > places.
>
> I made a minimal PR at https://github.com/apache/netbeans/pull/2135
> This would stop the immediate issue of the dialog not being
> cancellable,
Just to clarify, for anyone not following the discussion on the PR,
why I think the cancellability of the dialog is the most serious
aspect of this, note we have multiple issue reports on JIRA around
network issues (proxies, firewalls, outage, etc.) with downloading
these components.
So, try this -
- Switch off your network connection
- Make sure you have lots of Java projects open in 11.3 (fairly normal)
- Open 12.0-beta4 with a clean userdir and click Yes to import settings.
- Figure out how to get out of it! :-)
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 12 May 2020 at 14:17, Geertjan Wielenga <ge...@apache.org> wrote:
> It sounds like this nb-javac/javafx dialog is showing up in undesired
> places.
I made a minimal PR at https://github.com/apache/netbeans/pull/2135
This would stop the immediate issue of the dialog not being
cancellable, but still isn't ideal, causes regressions elsewhere and
is not uncontroversial! :-) Any thoughts on the right approach for
12.0 this late in?!
IMO, we should never have allowed JavaFX to become required rather
than recommended for Java enablement in 11.3. Seems borderline
against ASF rules to me.
The addition in 11.3 for the above has the unfortunate side effect of
forcing nb-javac installation in a lot of scenarios, and given that
won't support Java 14 and other things have gone in to stop it being
recommended when running on Java 14, this negates all of that.
I don't know if others agree this is a blocker, and it's up to Eric in
the end, but I would personally certainly -1 the release with this
behaviour as is.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
It sounds like this nb-javac/javafx dialog is showing up in undesired
places.
I started 11.3 with a fresh userdir, did not enable anything, opened the
Favorites window, double-clicked a JAR, and there that dialog was as well.
Gj
On Tue, 12 May 2020 at 15:13, Neil C Smith <ne...@apache.org> wrote:
> On Tue, 12 May 2020 at 13:52, Neil C Smith <ne...@apache.org> wrote:
> >
> > On Tue, 12 May 2020 at 12:56, Geertjan Wielenga <ge...@apache.org>
> wrote:
> > > I'm trying to reproduce this in 11.3 but am failing to do so, could you
> > > provide some quick steps from scratch, assuming I have just installed
> 11.3
> > > and am starting with a clean userdir?
> >
> > Click yes on the dialog to import settings from 11.2 (assuming you had
> > Java enabled, and possibly open projects, in 11.2). That's all that
> > seems to be required to trigger it here. Running on Java 11.
>
> Also, without importing settings, open an existing Java project, and
> click cancel on the dialog - no loop (which seems to be once for every
> project as the issue reporter suggested) but the project is marked
> broken. That's running on Java 14 by the way, so the last thing we
> want is to force installation of nb-javac.
>
> I wonder if it's this PR -
> https://github.com/apache/netbeans/pull/1612/files Has that made
> JavaFX required on JDK 11+? Which in turn triggers nb-javac as well
> (no opt out).
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 12 May 2020 at 13:52, Neil C Smith <ne...@apache.org> wrote:
>
> On Tue, 12 May 2020 at 12:56, Geertjan Wielenga <ge...@apache.org> wrote:
> > I'm trying to reproduce this in 11.3 but am failing to do so, could you
> > provide some quick steps from scratch, assuming I have just installed 11.3
> > and am starting with a clean userdir?
>
> Click yes on the dialog to import settings from 11.2 (assuming you had
> Java enabled, and possibly open projects, in 11.2). That's all that
> seems to be required to trigger it here. Running on Java 11.
Also, without importing settings, open an existing Java project, and
click cancel on the dialog - no loop (which seems to be once for every
project as the issue reporter suggested) but the project is marked
broken. That's running on Java 14 by the way, so the last thing we
want is to force installation of nb-javac.
I wonder if it's this PR -
https://github.com/apache/netbeans/pull/1612/files Has that made
JavaFX required on JDK 11+? Which in turn triggers nb-javac as well
(no opt out).
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
Well, maybe its a bit weasly as a solution, but we could make the argument
that since 12.0 is an LTS, we could say that we don’t support this kind of
scenaio. I.e., an LTS implies a new major release — a fresh blank page. And
in the meantime we’d work on fixing this for 12.1 and later, maybe
backported to 12.0.
Gj
On Tue, 12 May 2020 at 14:52, Neil C Smith <ne...@apache.org> wrote:
> On Tue, 12 May 2020 at 12:56, Geertjan Wielenga <ge...@apache.org>
> wrote:
> > I'm trying to reproduce this in 11.3 but am failing to do so, could you
> > provide some quick steps from scratch, assuming I have just installed
> 11.3
> > and am starting with a clean userdir?
>
> Click yes on the dialog to import settings from 11.2 (assuming you had
> Java enabled, and possibly open projects, in 11.2). That's all that
> seems to be required to trigger it here. Running on Java 11.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 12 May 2020 at 12:56, Geertjan Wielenga <ge...@apache.org> wrote:
> I'm trying to reproduce this in 11.3 but am failing to do so, could you
> provide some quick steps from scratch, assuming I have just installed 11.3
> and am starting with a clean userdir?
Click yes on the dialog to import settings from 11.2 (assuming you had
Java enabled, and possibly open projects, in 11.2). That's all that
seems to be required to trigger it here. Running on Java 11.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Potential blocker in 12.0 (and 11.3!)
Posted by Geertjan Wielenga <ge...@apache.org>.
I'm trying to reproduce this in 11.3 but am failing to do so, could you
provide some quick steps from scratch, assuming I have just installed 11.3
and am starting with a clean userdir?
Gj
On Tue, May 12, 2020 at 1:02 PM Neil C Smith <ne...@apache.org> wrote:
> Hi,
>
> As discussed off-list with Geertjan and Eric, I was just testing the
> Jenkins build of 12.0-beta4 before it was announced, and noticed a
> potential blocker issue. Interestingly, it's also in 11.3, but not in
> 11.2.
>
> When importing settings from a previous install (which happens not to
> have nb-javac or JavaFX installed), a dialog appears to install them
> that gets stuck in a loop if you try to cancel it. I think this
> behaviour gets triggered in other ways too, that effectively make
> those modules non-optional in some workflows.
>
> It seems this was reported against 11.3 in
> https://issues.apache.org/jira/browse/NETBEANS-3810. I remember it at
> the time, but it was marked minor and the emphasis was on the
> certificate problem rather than the more serious issue that something
> regressed between 11.2 and 11.3 that makes it (almost) impossible to
> get out of the dialog loop without installing the supposedly optional
> modules.
>
> As of yet I haven't looked into what changed in the code that is
> triggering this, but I don't think we should release 12.0 with this
> issue. I also haven't checked whether this forces the install on Java
> 14 yet, which would be even more problematic.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>