Possible NB 11.2 blocker?

[Neil C Smith <ne...@apache.org>]

Hi,

Saw an issue report today which might be the sign of a blocking issue
in NB 11.2.  I won't be able to look further until Monday.  It appears
we're getting a NPE in OptionsChooserPanel related to reading the
netbeans.buildnumber system property.  But I think this is still being
set correctly?

Haven't had a chance to dig too deeply yet, but I believe it's set at -

https://github.com/apache/netbeans/blob/master/platform/o.n.bootstrap/src/org/netbeans/MainImpl.java#L265

Yet the code here seems from the stacktrace to be getting null? -

https://github.com/apache/netbeans/blob/master/platform/options.api/src/org/netbeans/modules/options/export/OptionsChooserPanel.java#L413

Is there something else that would affect that value?  There have been
changes between beta1 and beta2 in the build on how buildnumber is
set, but it looks like the manifest values are correct?!

Issue at https://issues.apache.org/jira/browse/NETBEANS-3198

Thanks and 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: Possible NB 11.2 blocker?

[Neil C Smith <ne...@apache.org>]

On Fri, 11 Oct 2019, 19:36 Neil C Smith, <ne...@apache.org> wrote:

> It appears
> we're getting a NPE in OptionsChooserPanel related to reading the
> netbeans.buildnumber system property.  But I think this is still being
> set correctly?
>

Thanks Apache hive mind of Matthias and Christian! Debugging via GitHub UI
on a phone is difficult. :-)

So, it appears this is due to a regex in the options import/export assuming
a date is in the build number (I'd missed the call through to that).
However, this is no longer going to be true as the date has been replaced
by git hash.

So, not the blocker I feared it might be, but probably still something we
should fix for release? I guess we might need a quick fix now, and a better
fix for 11.3. Any thoughts on that?

Best wishes,

Neil

>