BTW, my macOS non-blocking error is caused by nbexec using the root folder (/)
for the cache (Cache directory: /var/cache).
I believe this also explains the Windows error Chris is mentioning where a lock
file is written top-level:
..\Downloads\netbeans\platform\lib\nbexec64.exe
java.io.FileNotFoundException: \lock (Zugriff verweigert)
at java.io.RandomAccessFile.open0(Native Method)
at java.io.RandomAccessFile.open(RandomAccessFile.java:316)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243)
at org.netbeans.CLIHandler.initialize(CLIHandler.java:555)
at org.netbeans.CLIHandler.initialize(CLIHandler.java:359)
at org.netbeans.MainImpl.execute(MainImpl.java:168)
at org.netbeans.MainImpl.main(MainImpl.java:60)
at org.netbeans.Main.main(Main.java:58)
Exception in thread "main" java.lang.NullPointerException
at org.netbeans.CLIHandler.initialize(CLIHandler.java:684)
at org.netbeans.CLIHandler.initialize(CLIHandler.java:359)
at org.netbeans.MainImpl.execute(MainImpl.java:168)
at org.netbeans.MainImpl.main(MainImpl.java:60)
at org.netbeans.Main.main(Main.java:58)
--emi
>-------- Original Message --------
>Subject: Re: [VOTE] Release Apache NetBeans 9.0 Alpha (incubating) -- 2nd
>attempt
>Local Time: November 15, 2017 3:45 PM
>UTC Time: November 15, 2017 1:45 PM
>From: [email protected]
>To: [email protected] <[email protected]>
>
>FWIW, ./platform/lib/nbexec runs just fine on macOS:
>
> Product Version: NetBeans Platform Dev (Build
> incubator-netbeans-release-79-on-20171113)
> Java: 1.8.0_66; Java HotSpot(TM) 64-Bit Server VM 25.66-b17
> Runtime: Java(TM) SE Runtime Environment 1.8.0_66-b17
> System: Mac OS X version 10.12.6 running on x86_64; UTF-8; en_US
> User directory: /Users/apache/Downloads/netbeans/platform/lib
> Cache directory: /var/cache
>
> Still, I don't believe nbexec is supposed to be called manually. That's why
> we have ./bin/netbeans which calls nbexec
>
> On macOS I'm also getting this non-blocking error:
>
> java.io.FileNotFoundException: /var/cache/lastModified/all-checksum.txt (No
> such file or directory)
>
> which means the paths nbexec is using are not entirely right.
>
> So, overall, I believe this is good enough to get an Alpha out!
>
> --emi
>
>>-------- Original Message --------
>> Subject: Re: [VOTE] Release Apache NetBeans 9.0 Alpha (incubating) -- 2nd
>> attempt
>> Local Time: November 15, 2017 3:38 PM
>> UTC Time: November 15, 2017 1:38 PM
>> From: [email protected]
>> To: [email protected]
>>OK, makes sense.
>>Still, we need to figure out what the problem is that Chris describes in
>> this thread.
>>Gj
>>On Wed, 15 Nov 2017 at 13:17, Jaroslav Tulach [email protected]
>> wrote:
>>>>On Wednesday, November 15, 2017, Geertjan Wielenga <
>>>>[email protected]> wrote:
>>>>>Well, the question would be why it is useful.
>>>>> And what does it prove -- and is it a requirement for release.
>>>>> What does it show if the launcher isn't working? That you cannot start
>>>>> platform!
>>>>> When I wrote the installation proposal
>>>>>https://platform.netbeans.org/articles/installation.html I described that
>>>>> nbexec shall be there and shall be used to launch the platform. I don't
>>>>> think much changed since then.
>>>>> Releasing something without a way to start it doesn't make it very useful,
>>>>> in my opinion. My 2 Kč
>>>>> -jt
>>>>> On Wed, Nov 15, 2017 at 9:49 AM, Jaroslav Tulach <
>>>>>>>[email protected]
>>>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote:
>>>>>> 2017-11-14 20:32 GMT+01:00 Geertjan Wielenga <
>>>>>>[email protected]
>>>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>>:
>>>>>>>Calling the exe doesn’t really make sense. Who/why would one do
>>>>>>> this.
>>>>>>>>
>>>>>>>>Why it doesn't make sense? Calling platform/lib/nbexec.exe shall start
>>>>>>> the
>>>>>>> platform. Calling platform/lib/nbexec does so on Unix.
>>>>>>> -jt
>
