identify the cause
> of the problem here.
>
> And here is the project I use in NetBeans, considerably more than 900
> files, etc: https://github.com/apache/incubator-netbeans
>
> Gj
>
>
> On Fri, Apr 12, 2019 at 5:07 PM Scott Palmer wrote:
>
>> I’m not the onl
p.
> (a few years ago, some people were having problems with NB on networked file
> systems. Is your project on a shared/networked drive? Just stabbing in the
> dark.)
>
>
> On Fri, Apr 12, 2019 at 10:33 AM Scott Palmer <mailto:swpal...@gmail.com>> wrote:
> What is th
What is the best course of action for reporting slowness? I can’t share my
project.
I’m not certain how to give step-by-step instructions when the problem is
basically one step in most cases. E.g. invoke auto-complete - nothing happens
for several seconds. Invoke rename - dialog doesn’t
Instantly I see the the colours are messed on on macOS. I’m using macOS 10.14
in Dark Mode. The status bar at the bottom of the NetBeans window is using
black text on a dark grey background. The project/file names in tree view of
the Project/Files/Services tab are white on a very light
t 2:15 PM, Scott Palmer wrote:
>
> Instantly I see the the colours are messed on on macOS. I’m using macOS
> 10.14 in Dark Mode. The status bar at the bottom of the NetBeans window is
> using black text on a dark grey background. The project/file names in tree
> view of the Proj
Some Gradle subprojects are missing ...
"gradle projects" from the command-line shows me:
Root project 'KayakPluginsRepo'
+--- Project ':Installer'
+--- Project ':KayakPluginsRepoClient'
+--- Project ':KayakPluginsRepoClientGui'
+--- Project ':KayakPluginsRepoClientGuiDistribution'
+--- Project
Haven't done anything yet, other than launch with JDK 13.0.2 and let it
import settings and open projects that I had open in NB 11.2.. Note NB 11.2
was running on JDK 8. For 11.3-beta3 I confogred it to use JDK 13
After various scanning and such happens, I get this (though it doesn't seem
to be
1, 2020, at 3:23 PM, Geertjan Wielenga wrote:
>
> Agree completely. Make it so. :-)
>
> Gj
>
> On Tue, 11 Feb 2020 at 21:18, Scott Palmer wrote:
>
>> I can help some. I see someone (you?) marked several of the JavaFX test
>> specs as being Ant-based and they sh
an went through the existing ones and recommended that most of
>> them be considered obsolete.
>>
>> On the Synergy home page, we see a new spec "JavaFX - JDK 13 / 8
>> Projects and Deployments", updated by Scott Palmer. Is this ready for
>> testing, or does it need more updat
moved, but new tasks referring to deploying via
jpackage should be created.
Scott
> On Feb 11, 2020, at 12:40 PM, Geertjan Wielenga wrote:
>
>
> Gradle is included yes. Will you help write the test spec?
>
> Gj
>
> On Tue, 11 Feb 2020 at 18:20, Scott Palmer <mailto:swp
> On Feb 12, 2020, at 9:34 AM, Geertjan Wielenga wrote:
>
> Click the Clone button and then choose 12.0.
>
> Gj
>
> On Wed, Feb 12, 2020 at 3:24 PM Scott Palmer <mailto:swpal...@gmail.com>> wrote:
> I don’t know how :-(
>
> I can log in to Synergy.. (It’s been
the
> test spec. other than one to send a request to transfer ownership.
>
>
> Scott
>
>> On Feb 12, 2020, at 9:34 AM, Geertjan Wielenga wrote:
>>
>> Click the Clone button and then choose 12.0.
>>
>> Gj
>>
>> On Wed, Feb 12, 2020 at 3:24
> On Apr 2, 2020, at 10:09 AM, Ernie Rael wrote:
>
> On 4/2/2020 6:31 AM, Geertjan Wielenga wrote:
>> Hi all,
>>
>> I propose we keep things short and sweet for JavaFX in NetCAT 12.0:
>>
>> https://netbeans-vm.apache.org/synergy/client/app/#/specification/452
>>
>> What do we think about
Does the NB installer try to find the JDK folder by calling
/usr/libexec/java_home ? If so, the java_home tool is completely broken
under Big Sur and will not return a JDK folder unless a JAVA_HOME
environment variable is *already* set to a valid JDK, in which case the
java_home tool always
+1 Launched for me on Big Sur.
I have several JDKs installed, it launched using 1.8 (the oldest JDK I have),
That appears to be because I had the JAVA_HOME environment variable set to that.
I unset JAVA_HOME with “launchctl unsetenv JAVA_HOME” and launched NB again -
this time it used JDK
E
> +fi
> # read Java Preferences
> if [ -x "/usr/libexec/java_home" ]; then
> -jdkhome=`/usr/libexec/java_home --version 1.8.0+ --failfast`
> -
> +jdkhome=`/usr/libexec/java_home --version 1.8+`
>
> On Jun 7, 2021, at 7:50 PM, Glenn Holmer wrote:
>
> On 6/7/21 9:26 AM, Neil C Smith wrote:
>> On Mon, 7 Jun 2021 at 14:24, Jiří Kovalský wrote:
>>> From that point of view it makes more sense to concentrate the testing
>>> effort around LTS version with known NetCAT start/end dates, form
17 matches
Mail list logo
