Re: Using Netbeans with SE 22

[Owen Thomas]

Thanks Michael. Although I don't distribute my own bytecode, I do hope
people may find it valuable one day.

I currently use private static methods if I need to do anything before
calling super and this new feature does promise me some release from this
ugly way of doing things. I think perhaps I can wait until this feature is
made generally available.

On Sun, 2 Jun 2024 at 20:33, Michael Bien  wrote:

> Hi Owen,
>
> regarding NetBeans:
> you will need NetBeans 22 or later for Java 22 features (NB 22 should be
> officially released soon). Also keep in mind that JEP 447 (Statements
> before super) is a preview feature and preview features create
> non-portable bytecode which lock the bytecode to one JDK version.
>
> regarding Gradle:
> I believe latest gradle (8.8) has now full support for JDK 22.
>
> -mbien
>
>
> On 02.06.24 08:05, Owen Thomas wrote:
> > Hello Netbeans Users.
> >
> > I have heard that Java SE 22 allows code before a call to super so
> > long as it doesn't refer to "this". Being that I think this feature
> > will help me a lot, I was wondering if Netbeans supports this Java
> > release.
> >
> > My projects are currently using JSE 17 and Gradle 7.3 (I think) as per
> > the lauded compatibility matrix
> > <https://docs.gradle.org/current/userguide/compatibility.html>.
> >
> > What advice might others be able to provide me before I decide to make
> > the move? I take it I will have to upgrade to the later gradle
> > recommended in the matrix which makes me hesitant; is there any advice
> > anyone can give me about doing this?
> >
> > Thanks,
> >
> >   Owen.
> >
> > Clique Space(TM). Anima ex machina. Find out more on cliquespace.net
> > <http://cliquespace.net>.
>
>
>

Using Netbeans with SE 22

[Owen Thomas]

Hello Netbeans Users.

I have heard that Java SE 22 allows code before a call to super so long as
it doesn't refer to "this". Being that I think this feature will help me a
lot, I was wondering if Netbeans supports this Java release.

My projects are currently using JSE 17 and Gradle 7.3 (I think) as per the
lauded compatibility matrix
.

What advice might others be able to provide me before I decide to make the
move? I take it I will have to upgrade to the later gradle recommended in
the matrix which makes me hesitant; is there any advice anyone can give me
about doing this?

Thanks,

  Owen.

Clique Space(TM). Anima ex machina. Find out more on cliquespace.net.

Re: How to stop output "wobbling"?

[Owen Thomas]

Correction in bold...

On Fri, 8 Mar 2024 at 13:26, Owen Thomas  wrote:

> So, I call invokeAnWait for both cases, and although the mechanism works
> slower by a factor of about 100 (cf. the attached - ~4ms versus *[~40μs]*),
> the wobble appears to have gone.
>

Re: How to stop output "wobbling"?

[Owen Thomas]

Thanks Thomas for the tip. I think I have made an appropriate correction.

I was calling invokeLater on a method that adds a character to the output
for anything that wasn't a newline. For newlines I would call invokeAndWait
when I was displaying the output in the window. It seems that using
different calls was producing the wobble; an effect that wasn't evident
when I was running my program over a slower machine.

So, I call invokeAnWait for both cases, and although the mechanism works
slower by a factor of about 100 (cf. the attached - ~4ms versus ~40ns), the
wobble appears to have gone.

On Fri, 8 Mar 2024 at 00:36, Thomas Wolf  wrote:

> You’re making all the Swing calls in the EDT (vs directly in the threads
> you mentioned), right?
>
> Tom
>
> On Mar 7, 2024, at 6:40 AM, Owen Thomas 
> wrote:
>
> 
> The numbers running down the left are milliseconds, all others are nanos.
> As you can see, all this happens within the same millisecond, and perhaps
> I'm thinking that Swing wasn't built with rendering output at this rate in
> mind.
>
> Anyway, I'd love to know what people have to say. :)
>
> On Thu, 7 Mar 2024 at 22:04, Owen Thomas 
> wrote:
>
>> Hello Netbeans people. This is not a question for Netbeans itself, but I
>> know there are a lot of clever people here who may be able to give me a
>> pointer or two, so please look away if this question might offend. I hope
>> it doesn't. :)
>>
>> My program uses Swing. It outputs text to a window. The output is
>> attached. At a particular point (the line is highlighted in the attached
>> screenshot) the output begins to wobble; that is, the line spacing becomes
>> uneven and (perhaps) even characters appear to be squashed.
>>
>> Now, I thought this might be something to do with how quickly the output
>> is produced (it is produced very quickly - those numbers are time
>> measurements in nanoseconds) and how competing threads might cause the
>> Swing GUI innards to lose their grip somehow, but when I tried wrapping
>> some of my code within synchronised blocks, I didn't see any improvement.
>>
>> Surely I think to myself things like this have been done before. Does
>> anyone know how I might be able to stop this wobbling?
>>
>> Thanks,
>>
>>   Owen.
>>
>>

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: How to stop output "wobbling"?

[Owen Thomas]

The numbers running down the left are milliseconds, all others are nanos.
As you can see, all this happens within the same millisecond, and perhaps
I'm thinking that Swing wasn't built with rendering output at this rate in
mind.

Anyway, I'd love to know what people have to say. :)

On Thu, 7 Mar 2024 at 22:04, Owen Thomas  wrote:

> Hello Netbeans people. This is not a question for Netbeans itself, but I
> know there are a lot of clever people here who may be able to give me a
> pointer or two, so please look away if this question might offend. I hope
> it doesn't. :)
>
> My program uses Swing. It outputs text to a window. The output is
> attached. At a particular point (the line is highlighted in the attached
> screenshot) the output begins to wobble; that is, the line spacing becomes
> uneven and (perhaps) even characters appear to be squashed.
>
> Now, I thought this might be something to do with how quickly the output
> is produced (it is produced very quickly - those numbers are time
> measurements in nanoseconds) and how competing threads might cause the
> Swing GUI innards to lose their grip somehow, but when I tried wrapping
> some of my code within synchronised blocks, I didn't see any improvement.
>
> Surely I think to myself things like this have been done before. Does
> anyone know how I might be able to stop this wobbling?
>
> Thanks,
>
>   Owen.
>
>

How to stop output "wobbling"?

[Owen Thomas]

Hello Netbeans people. This is not a question for Netbeans itself, but I
know there are a lot of clever people here who may be able to give me a
pointer or two, so please look away if this question might offend. I hope
it doesn't. :)

My program uses Swing. It outputs text to a window. The output is attached.
At a particular point (the line is highlighted in the attached screenshot)
the output begins to wobble; that is, the line spacing becomes uneven and
(perhaps) even characters appear to be squashed.

Now, I thought this might be something to do with how quickly the output is
produced (it is produced very quickly - those numbers are time measurements
in nanoseconds) and how competing threads might cause the Swing GUI innards
to lose their grip somehow, but when I tried wrapping some of my code
within synchronised blocks, I didn't see any improvement.

Surely I think to myself things like this have been done before. Does
anyone know how I might be able to stop this wobbling?

Thanks,

  Owen.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: Not all inline hints being displayed.

[Owen Thomas]

On Wed, 6 Mar 2024 at 11:33,  wrote:

> Owen,
>
> I've noticed that whenever you concatenate a string argument, NetBeans
> drops the inline hint for that argument, also. I am not sure if this is a
> bug, however, because I believe that this is what occurs simply to shortent
> the line, as the inline hints do not count against the character count of
> the line for ALT+SHIFT+F formatting.
>
> I've noticed that the inline hints are also dropped when using a ternary
> operator in an argument to a method. I believe that this is simply done for
> the sake of readability.
>

Thanks Sean for your suggestions. They make sense in terms of behaviour
that could have been intended even though the behaviour doesn't feel
intuitive to me.

Perhaps my intuition is off. :)

Not all inline hints being displayed.

[Owen Thomas]

Hello.

I like the inline hints feature, as it helps me to understand which
arguments receive which values in method calls. However, I have noticed
something strange with variable length arguments.

The attached screenshot is of a call to a method with variable arguments,
and the screenshot shows that the editor hasn't named one of them. Why is
this?

Thanks,

  Owen.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: JavaDoc latest documentation

[Owen Thomas]

GTK :)

On Fri, 23 Feb 2024 at 00:50, Arbol One  wrote:

> Yes! Very helpful.
> Thanks so much.
> On 2024-02-21 10:25 p.m., Owen Thomas wrote:
>
>
>
> On Thu, 22 Feb 2024 at 13:05, Arbol One  wrote:
>
>> Is there a webpage anyone can recommend to get information about JavaDoc
>> 17.0.10?
>>
>> TIA.
>>
>
>  Perhaps this
> <https://docs.oracle.com/en/java/javase/17/docs/specs/javadoc/doc-comment-spec.html>
> might be what you're after?
>
> --
> *ArbolOne.ca* Using Fire Fox and Thunderbird. ArbolOne is composed of
> students and volunteers dedicated to providing free services to charitable
> organizations. ArbolOne on Java Development is in progress [ í ]
>

Re: JavaDoc latest documentation

[Owen Thomas]

On Thu, 22 Feb 2024 at 13:05, Arbol One  wrote:

> Is there a webpage anyone can recommend to get information about JavaDoc
> 17.0.10?
>
> TIA.
>

 Perhaps this

might be what you're after?

Re: JSON Simple

[Owen Thomas]

I don't know the answer to this question because that will depend a little
on what build tool you are using. You could start by right-clicking on your
project from the projects pane and navigating to your dependent libraries
through the project's properties or something similar.

I hope that helps. :)

On Tue, 13 Feb 2024 at 01:25, Tom  wrote:

> Newbie question, how can I use external jars like json simple in a
> Netbeans project?
> I have added json-simple-1.1.1.jar to Tools / Library.
> But import org.json.simple.JSONArray; gives a package not found error.
> I have already googled.
> How can I fix that?
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Re: AI assistant for NetBeans

[Owen Thomas]

NetBeans appears to give me everything I need without harassment. I think
there are magic pixies at IntelliJ waving moral fingers at me to be more
like them, because they keep telling me that they walk in the garden of
Eden.

On Mon, 12 Feb 2024 at 09:47, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> Several people in this thread still, after all these years, seem under the
> mistaken impression that there are magic pixies creating things in NetBeans.
>
> There. Are. No. Pixies. There. Is. Only. You.
>
> You are NetBeans. Missing a feature? Then create that feature. You don't
> want to create that feature. That means you don't really need that feature
> after all.
>
> Gj
>
> On Sun, Feb 11, 2024 at 11:08 PM Owen Thomas 
> wrote:
>
>>
>>
>> On Mon, 12 Feb 2024 at 08:40, Benjamin Neuman 
>> wrote:
>>
>>> To the luddites, I believe you are going to be left behind.
>>>
>>
>> Better watch out then.
>>
>

Re: AI assistant for NetBeans

[Owen Thomas]

On Mon, 12 Feb 2024 at 08:40, Benjamin Neuman  wrote:

> To the luddites, I believe you are going to be left behind.
>

Better watch out then.

Re: Re: AI assistant for NetBeans

[Owen Thomas]

On Sun, 11 Feb 2024 at 11:42, Andreas Reichel <
andr...@manticore-projects.com> wrote:

> On Sun, 2024-02-11 at 09:50 +1100, Owen Thomas wrote:
>
> On Sat, 10 Feb 2024 at 13:46, Andreas Reichel <
> andr...@manticore-projects.com> wrote:
>
> Smart people will become smarter and faster using it. Others won't.
>
>
> What do you mean when you say this?
>
>
> What I meant was: it amplifies experience and skills. If you are
> experienced it will make you faster because you know when to trust and use
> it. If you are inexperienced it will harm you because it can pretend
> providing "solutions", which actually may be harmful or wrong.
>

Yes, I understand that perhaps it does help one who is already experienced
leverage off the experience of others to quickly come to an optimal
solution to a particular problem.

 Perhaps I would agree to using an AI that makes suggestions without
"learning" from the code it is being exposed to.


>
>
> I think I would surely benefit from some assistance too, but I am afraid
> that an AI algorithm may suggest what it found in my code to a wider
> developer community, thus leaking my own work to a wider world out of my
> control.
>
>
> That is a different and very valid and interesting angle to look at it:
> what guarantees are there when its integrated into your UI, which opens ALL
> your code? None and nothing! They just will say "sorry" when eventually
> caught and that's it.
>

I would recommend Netbeans think about this scenario. I believe that the
point I make in this reply above about preventing the AI from being trained
on the code it is exposed to in a particular user's IDE would be considered
valuable to many.


> I would say, when you believed in proprietary code then IDE AI integration
> was not for you even when it worked.
>

I'm not averse to publishing my code and being attributed for it - that's
why I do this. Hence, I would be flattered if I saw snippets of my
published code being suggested back to me by an AI, but I wouldn't be as
happy if I saw unpublished work appearing. I will steer clear of an AI
looking at the code in my IDE for now and wait a while perhaps until this
AI stuff matures; let others make the mistakes that I hopefully avoid. :)


> Although the same concern applies to GitHub already. So unless you host by
> yourself strictly (as we do, except for what we publish as OpenSource) this
> concern should not be new.
>

Just as well because I have no code in GitHub.

  Owen.

>
Clique Space(TM). Anima ex machina.
Find out more on cliquespace.net.

Re: Re: AI assistant for NetBeans

[Owen Thomas]

Hi Andreas.

On Sat, 10 Feb 2024 at 13:46, Andreas Reichel <
andr...@manticore-projects.com> wrote:

> Smart people will become smarter and faster using it. Others won't.
>

What do you mean when you say this?

I think I would surely benefit from some assistance too, but I am afraid
that an AI algorithm may suggest what it found in my code to a wider
developer community, thus leaking my own work to a wider world out of my
control.

Would I be one of the "others" as you define them above?

Re: Upgrade Gradle version.

[Owen Thomas]

Thanks all. I created a new Gradle 7.2 multiproject build and imported my
sources to it. That seems to have worked.

On Thu, 25 Jan 2024 at 20:51, Giles Winstanley  wrote:

> Aside from Laszlo's suggestion to use Java 17, since you seem to be in a
> position to choose your Gradle version, I suggest trying Gradle 8.5, which
> has better support for *running* on Java 21. Gradle 8.4 can build a Java 21
> project, but must itself run on Java <21. With Gradle 8.5 you can do both,
> which simplifies things (and it also supports Java 17, etc.).
>
> Regarding the migration from older Gradle, Eric's suggestion to look at
> the Gradle docs is a good one. Pay attention to the (sometimes a little
> cryptic) Gradle build warnings and you'll become informed. Recent versions
> of Gradle are keen to ensure strong task input/output declaration. Also I
> recommend using the newer task definition style (e.g.
> tasks.register('myCopyTask', Copy) {...}) and updating references for
> buildDirectory/libsDirectory/etc. which have been updated and will likely
> show warnings.
>
> Stan
>
> On 25/01/2024 02:13, Owen Thomas wrote:
>
> I've only got version 21 of Java, and I want to upgrade to gradle 8.?
> don't I?
>
>
>
> On Thu, 25 Jan 2024 at 13:11, Owen Thomas 
> wrote:
>
>> How do I do that?
>>
>> On Thu, 25 Jan 2024 at 13:07, Laszlo Kishalmi 
>> wrote:
>>
>>> Set the Java Runtime Version for Gradle to Java 17 in NetBeans.
>>>
>>> On 1/24/24 17:43, Owen Thomas wrote:
>>> > I'm thoroughly lost with Gradle.
>>> >
>>> > Can someone please tell me which version of Java I should use and
>>> > version of this build tool I should upgrade to with the current
>>> > release of Netbeans?
>>> >
>>> > This is all too frustrating.
>>> >
>>> >   Owen.
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>>> For additional commands, e-mail: users-h...@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: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, 
> visit:https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

Module with changes but without blue cylinder?

[Owen Thomas]

Hello again.

I think I'm almost there. One minor and possibly cosmetic problem that
seems not to go away when one clears ".cache/netbeans/20".

I have noticed that changes are being picked up by Netbeans for one
project, but there is no blue cylinder. Do I have to worry about it? How
might I make the blue cylinder appear?

See the attached screenshot of the projects pane.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: Upgrade Gradle version.

[Owen Thomas]

One other thing... How do I set dependencies among my projects from
Netbeans?

On Thu, 25 Jan 2024 at 13:20, Owen Thomas 
wrote:

> Okay... I suppose that advice was good. I've created some new projects and
> the yellow triangles have now disappeared after installing Zulu 17.0.10+7.
>
> Hmmm... not an upgrade to gradle 8.? but the yellow triangles have
> disappeared... I'll try and copy my source to them and see what happens...
>
> On Thu, 25 Jan 2024 at 13:13, Owen Thomas 
> wrote:
>
>> I've only got version 21 of Java, and I want to upgrade to gradle 8.?
>> don't I?
>>
>>
>>
>> On Thu, 25 Jan 2024 at 13:11, Owen Thomas 
>> wrote:
>>
>>> How do I do that?
>>>
>>> On Thu, 25 Jan 2024 at 13:07, Laszlo Kishalmi 
>>> wrote:
>>>
>>>> Set the Java Runtime Version for Gradle to Java 17 in NetBeans.
>>>>
>>>> On 1/24/24 17:43, Owen Thomas wrote:
>>>> > I'm thoroughly lost with Gradle.
>>>> >
>>>> > Can someone please tell me which version of Java I should use and
>>>> > version of this build tool I should upgrade to with the current
>>>> > release of Netbeans?
>>>> >
>>>> > This is all too frustrating.
>>>> >
>>>> >   Owen.
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>>>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>>>
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>
>>>>

Re: Upgrade Gradle version.

[Owen Thomas]

Okay... I suppose that advice was good. I've created some new projects and
the yellow triangles have now disappeared after installing Zulu 17.0.10+7.

Hmmm... not an upgrade to gradle 8.? but the yellow triangles have
disappeared... I'll try and copy my source to them and see what happens...

On Thu, 25 Jan 2024 at 13:13, Owen Thomas 
wrote:

> I've only got version 21 of Java, and I want to upgrade to gradle 8.?
> don't I?
>
>
>
> On Thu, 25 Jan 2024 at 13:11, Owen Thomas 
> wrote:
>
>> How do I do that?
>>
>> On Thu, 25 Jan 2024 at 13:07, Laszlo Kishalmi 
>> wrote:
>>
>>> Set the Java Runtime Version for Gradle to Java 17 in NetBeans.
>>>
>>> On 1/24/24 17:43, Owen Thomas wrote:
>>> > I'm thoroughly lost with Gradle.
>>> >
>>> > Can someone please tell me which version of Java I should use and
>>> > version of this build tool I should upgrade to with the current
>>> > release of Netbeans?
>>> >
>>> > This is all too frustrating.
>>> >
>>> >   Owen.
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>

Re: Upgrade Gradle version.

[Owen Thomas]

I've only got version 21 of Java, and I want to upgrade to gradle 8.? don't
I?



On Thu, 25 Jan 2024 at 13:11, Owen Thomas 
wrote:

> How do I do that?
>
> On Thu, 25 Jan 2024 at 13:07, Laszlo Kishalmi 
> wrote:
>
>> Set the Java Runtime Version for Gradle to Java 17 in NetBeans.
>>
>> On 1/24/24 17:43, Owen Thomas wrote:
>> > I'm thoroughly lost with Gradle.
>> >
>> > Can someone please tell me which version of Java I should use and
>> > version of this build tool I should upgrade to with the current
>> > release of Netbeans?
>> >
>> > This is all too frustrating.
>> >
>> >   Owen.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>> For additional commands, e-mail: users-h...@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: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: Upgrade Gradle version.

[Owen Thomas]

How do I do that?

On Thu, 25 Jan 2024 at 13:07, Laszlo Kishalmi 
wrote:

> Set the Java Runtime Version for Gradle to Java 17 in NetBeans.
>
> On 1/24/24 17:43, Owen Thomas wrote:
> > I'm thoroughly lost with Gradle.
> >
> > Can someone please tell me which version of Java I should use and
> > version of this build tool I should upgrade to with the current
> > release of Netbeans?
> >
> > This is all too frustrating.
> >
> >   Owen.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Re: Upgrade Gradle version.

[Owen Thomas]

I'm thoroughly lost with Gradle.

Can someone please tell me which version of Java I should use and version
of this build tool I should upgrade to with the current release of Netbeans?

This is all too frustrating.

  Owen.

Re: Upgrade Gradle version.

[Owen Thomas]

On Thu, 25 Jan 2024 at 10:33, Owen Thomas 
wrote:

> Hello.
>
> I needed to reinstall netbeans, so I installed the latest version. I was
> using Gradle 7.2 on a previous project but the current environment is
> complaining to me that I need Gradle 8.4 to run with Java 21.
>
> I am happy to move to version 8.4 of Gradle, especially since there
> appears to be a mismatch between Grable 7.2 and the Java 17 I was using
> previously. However, there isn't much information on how to upgrade Gradle
> to work with the current Java version from the Resolve Project Problems
> dialogue box that appears.
>
> So, my question is: how do I upgrade my existing project from Gradle 7.2
> to 8.4?
>
> Help appreciated. Thanks.
>

So, I've tried to follow instructions to the degree that doing so made
sense to me.

I installed version 21 of the JVM on my machine, and, from the
multi-project root  directory of my gradle build I tried to use the gradle
wrapper...

This is the output I received:

-- Start of output.

owen@owen-Q16-7A405-BM-55:~/Development/CliqueSpace/Current/Code/trunk/clique-space$
./gradlew wrapper --gradle-version=8.5 --distribution-type=bin
Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use
--status for details

FAILURE: Build failed with an exception.

* Where:
Settings file
'/home/owen/Development/CliqueSpace/Current/Code/trunk/clique-space/settings.gradle'

* What went wrong:
Could not compile settings file
'/home/owen/Development/CliqueSpace/Current/Code/trunk/clique-space/settings.gradle'.
> startup failed:
  General error during conversion: Unsupported class file major version 65

  java.lang.IllegalArgumentException: Unsupported class file major version
65
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:196)
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:177)
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:163)
at groovyjarjarasm.asm.ClassReader.(ClassReader.java:284)
at
org.codehaus.groovy.ast.decompiled.AsmDecompiler.parseClass(AsmDecompiler.java:81)
at
org.codehaus.groovy.control.ClassNodeResolver.findDecompiled(ClassNodeResolver.java:251)
at
org.codehaus.groovy.control.ClassNodeResolver.tryAsLoaderClassOrScript(ClassNodeResolver.java:189)
at
org.codehaus.groovy.control.ClassNodeResolver.findClassNode(ClassNodeResolver.java:169)
at
org.codehaus.groovy.control.ClassNodeResolver.resolveName(ClassNodeResolver.java:125)
at
org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveClassNullable(AsmReferenceResolver.java:57)
at
org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveClass(AsmReferenceResolver.java:44)
at
org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveNonArrayType(AsmReferenceResolver.java:79)
at
org.codehaus.groovy.ast.decompiled.AsmReferenceResolver.resolveType(AsmReferenceResolver.java:70)
at
org.codehaus.groovy.ast.decompiled.MemberSignatureParser.createMethodNode(MemberSignatureParser.java:57)
at
org.codehaus.groovy.ast.decompiled.DecompiledClassNode.lambda$createMethodNode$1(DecompiledClassNode.java:230)
at
org.codehaus.groovy.ast.decompiled.DecompiledClassNode.createMethodNode(DecompiledClassNode.java:236)
at
org.codehaus.groovy.ast.decompiled.DecompiledClassNode.lazyInitMembers(DecompiledClassNode.java:203)
at
org.codehaus.groovy.ast.decompiled.DecompiledClassNode.getDeclaredMethods(DecompiledClassNode.java:122)
at
org.codehaus.groovy.ast.ClassNode.tryFindPossibleMethod(ClassNode.java:1283)
at
org.codehaus.groovy.control.StaticImportVisitor.transformMethodCallExpression(StaticImportVisitor.java:251)
at
org.codehaus.groovy.control.StaticImportVisitor.transform(StaticImportVisitor.java:133)
at
org.codehaus.groovy.ast.ClassCodeExpressionTransformer.visitExpressionStatement(ClassCodeExpressionTransformer.java:108)
at
org.codehaus.groovy.ast.stmt.ExpressionStatement.visit(ExpressionStatement.java:40)
at
org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitClassCodeContainer(ClassCodeVisitorSupport.java:138)
at
org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitConstructorOrMethod(ClassCodeVisitorSupport.java:111)
at
org.codehaus.groovy.ast.ClassCodeExpressionTransformer.visitConstructorOrMethod(ClassCodeExpressionTransformer.java:66)
at
org.codehaus.groovy.control.StaticImportVisitor.visitConstructorOrMethod(StaticImportVisitor.java:108)
at
org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitConstructor(ClassCodeVisitorSupport.java:101)
at
org.codehaus.groovy.ast.ClassNode.visitContents(ClassNode.java:1089)
at
org.codehaus.groovy.ast.ClassCodeVisitorSupport.visitClass(ClassCodeVisitorSupport.java:52)
at
org.codehaus.groovy.control.CompilationUnit.lambda$addPhaseOperations$3(CompilationUnit.java:209)

Upgrade Gradle version.

[Owen Thomas]

Hello.

I needed to reinstall netbeans, so I installed the latest version. I was
using Gradle 7.2 on a previous project but the current environment is
complaining to me that I need Gradle 8.4 to run with Java 21.

I am happy to move to version 8.4 of Gradle, especially since there appears
to be a mismatch between Grable 7.2 and the Java 17 I was using previously.
However, there isn't much information on how to upgrade Gradle to work with
the current Java version from the Resolve Project Problems dialogue box
that appears.

So, my question is: how do I upgrade my existing project from Gradle 7.2 to
8.4?

Help appreciated. Thanks.

Re: Java version: 21 ... not supported by Gradle 8.5

[Owen Thomas]

On Wed, 6 Dec 2023 at 10:38, Andreas Reichel 
wrote:

> 1) dependency resolution (including the understanding, what Class format
> the artifact is providing)
> 2) compiling and packaging based on the built classpath
>
> For 2), any Gradle will do.
> But for 1) Gradle needs to understand the particular Class formats and
> thus depends on the JDK version strictly.
>

Hmm... thanks for this info Andreas.

I would think that the JVM version is given in a jar's environment setup.
It might have to be known to the build tool only to check that the
destination JVM for the build is able to run the built artefact and all its
dependencies.

Anyway, I think Gradle is trying to make me appropriate someone else's
problems. I might use Maven in the future, and I'll hang on to my gradle
build at the moment (I'm getting incompatibility errors in my build but
these don't seem to have a material influence on what is being built), but
I may yet turn back to Ant. Although in a future time I may, I currently
use no third party libraries.

I think Gradle is making things too complicated for Java users. Bad.

>

Re: Java version: 21 ... not supported by Gradle 8.5

[Owen Thomas]

Thanks for that; Maybe I'm not keeping enough attention to what is going on
here to really make a constructive comment, butI was looking more for
justification of the existence of this "compatibility matrix" and Gradle's
future intentions in supporting Java. This matrix is just doing my head in,
because all I can gather from the page disclosed is a mechanism - I don't
understand why the mechanism needs to exist in the first place.

I don't think the version of a build tool should need to be matched with a
version of the JVM - but this is indeed probably merey my ignorance of the
justification for this necessity speaking. Is there a page that informs my
ignorance?

On Wed, 6 Dec 2023 at 03:23, Bernd Michaely  wrote:

> https://docs.gradle.org/current/userguide/compatibility.html
>
> On 04.12.23 01:24, Owen Thomas wrote:
> >
> > Is there a page I can read that outlines how Gradle will work with
> > Java in the future? This stuff is giving me a headache.
> >
>

Re: Java version: 21 ... not supported by Gradle 8.5

[Owen Thomas]

What's going on with Java and Gradle? Would I be right in supposing that it
would be simpler just to go back to Ant?

Is there a page I can read that outlines how Gradle will work with Java in
the future? This stuff is giving me a headache.

On Mon, 4 Dec 2023 at 10:51, Laszlo Kishalmi 
wrote:

> Well, unfortunately gradle init only supports java version specification
> since Gradle 8.5
>
> NB20 is bundled with Gradle 8.4.
>
> There is a bit workaround needed to run Java 21 projects with Gradle.
>
> Set the Java Runtime version for Gradle in Tools > Options > Java >
> Gradle to Java 20 or below.
>
>  From there you can use any Java version in your Gradle projects,
> whatever that Gradle version support.
>
> Gradle 8.4 does support Java 21 using Java Toolchain, should work.
>
> java {
>  toolchain {
>  languageVersion = JavaLanguageVersion.of(21)
>  }
> }
>
> On 12/3/23 13:30, Ernie Rael wrote:
> > Running NB-20, jdk21.
> >
> > The goal is to play with some JDK-21 APIs...
> >
> > Creating a project using NB's "New Project > Java with Gradle".
> >
> > I can build and run the default "Library" and test. But there's the
> > warning icon and "Resolve Project Problems".
> >
> > Any way to get rid of the warning?
> >
> > -ernie
> >
> >
> > "Resolve Project Problems"
> >
> > The Java version: 21, that is selected for the project is not
> > supported by
> > Gradle 8.4.The IDE will attempt to use Gradle 8.4 to gather the project
> > information.
> > Possible solutions:
> > Upgrade your Gradle version on your project
> > Select Java Runtime 20 (or below), on Build > Gradle Execution
> > settings, to avoid this problem!
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: users-h...@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: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Netbeans and modules.

[Owen Thomas]

I have "modularised" my java project, and since then, I have noticed that
Netbeans 14 doesn't like to resolve all entries when I do "Find Usages". I
can of course sometimes see too much when I do a "Find In Projects".

Have later versions of NB tackled this seeming annoyance?

Ta.

  Owen.

Re: Refactoring

[Owen Thomas]

Hi Tom.

Refactoring is simply moving stuff around in your source code without
making any (major) change to the functionality of your program.

You may want to do this when for instance you are preparing to implement a
functional enhancement that makes use of a particular design pattern, and
your source code cannot implement the functional enhancement in its current
state.

HTH.

  Owen.

On Tue, 22 Aug 2023 at 07:28, Tom Rushworth  wrote:

> Newbie question.  I'm working on an HTML project.  When I change a file
> name, Netbeans wants to know if I want to "refactor" or not. What does
> it mean to refactor?
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Installer for Netbeans 15 on Ubuntu?

[Owen Thomas]

Is there an installer for Netbeans 15 on Ubuntu?

Re: Should I exclude ./gradle/nb-cache from commit?

[Owen Thomas]

Thanks Bernd for providing this important information. It is help like this
from you and others that helps me make sense of the complexity, and I feel
that I wouldn't be able to comprehend as quickly without it. I hope that I
might be able to provide others with the same from time to time.

On Sun, 7 Aug 2022 at 02:16, Bernd Michaely  wrote:

> The original Gradle (7.5) doc says:
>
> The project root directory contains all source files that are part of your
> project. In addition, it contains files and directories that are generated
> by Gradle such as .gradle and build. While the former are usually checked
> in to source control, the latter are transient files used by Gradle to
> support features like incremental builds.
>
> see:
> https://docs.gradle.org/current/userguide/directory_layout.html#dir:project_root
>
>
> regards,
>
> Bernd
>
>
> On 06.08.22 02:26, Owen Thomas wrote:
>
> I have my projects running. All is good in the world.
>
> I see the directory indicated in the title of this message sometimes
> contains files for projects with old names (I converted my project names
> from camel to kebab case when this was indicated to me as the standard in
> gradle/maven, so I did as I was told).
>
> Is it important to keep nb-cache under version control in Git? Are there
> any other NetBeans or Gradle directories that can be ignored? Do I ignore
> them or do I exclude them from the commit?
>
> Thanks,
>
>   Owen.
>
>

Re: Should I exclude ./.gradle/nb-cache from commit?

[Owen Thomas]

I've also ignored "./build" as keeping these files in version control is
silly.

Now that that's done, I can forget about it for another decade or so. :)

On Sat, 6 Aug 2022 at 11:36, Owen Thomas  wrote:

> Sorry, I have misquoted the folder in the title. The folder I intended to
> quote is "./.gradle/nb-cache", and I have corrected the title of this email
> accordingly.
>
> What I will do then is ignore ".gradle" from each project's base
> directory. Let me know if that is not correct or is incomplete.
>
> Thanks,
>
>   Owen.
>
> On Sat, 6 Aug 2022 at 10:55, Andreas Reichel <
> andr...@manticore-projects.com> wrote:
>
>>
>>
>> On Fri, 2022-08-05 at 17:52 -0700, Laszlo Kishalmi wrote:
>>
>> while gradle/ folders
>> shall be committed
>>
>>
>>
>> Laszlo,
>>
>> thank you for advise, please care to elaborate. Why should it be there
>> when it can be rebuild on demand? What is the advantage of tracking it and
>> the disadvantage of dismissing it?
>> Sorry to bother you, I just would like to learn.
>>
>> Cheers
>> Andreas
>>
>

Should I exclude ./.gradle/nb-cache from commit?

[Owen Thomas]

Sorry, I have misquoted the folder in the title. The folder I intended to
quote is "./.gradle/nb-cache", and I have corrected the title of this email
accordingly.

What I will do then is ignore ".gradle" from each project's base directory.
Let me know if that is not correct or is incomplete.

Thanks,

  Owen.

On Sat, 6 Aug 2022 at 10:55, Andreas Reichel 
wrote:

>
>
> On Fri, 2022-08-05 at 17:52 -0700, Laszlo Kishalmi wrote:
>
> while gradle/ folders
> shall be committed
>
>
>
> Laszlo,
>
> thank you for advise, please care to elaborate. Why should it be there
> when it can be rebuild on demand? What is the advantage of tracking it and
> the disadvantage of dismissing it?
> Sorry to bother you, I just would like to learn.
>
> Cheers
> Andreas
>

Should I exclude ./gradle/nb-cache from commit?

[Owen Thomas]

I have my projects running. All is good in the world.

I see the directory indicated in the title of this message sometimes
contains files for projects with old names (I converted my project names
from camel to kebab case when this was indicated to me as the standard in
gradle/maven, so I did as I was told).

Is it important to keep nb-cache under version control in Git? Are there
any other NetBeans or Gradle directories that can be ignored? Do I ignore
them or do I exclude them from the commit?

Thanks,

  Owen.

Re: Re: Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

On Thu, 4 Aug 2022 at 15:54, László Kishalmi 
wrote:

> Compile was discouraged at 3.4, marked for deprecation in  4.0 they
> removed it in 7.0. that's pretty long time. 4 years
>

No problem. I'll just have to be mindful of this when following advice from
people about Gradle.

Thanks all. Until next time. :)

Re: Re: Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

On Thu, 4 Aug 2022 at 12:37, Andreas Reichel 
wrote:

> Just be prepared. Its still very much worth it in my opinion.
>

Thanks Andreas. Yea, even though, if I were Gradle, I might have kept the
"compile" option for a while longer, I think backwards compatibility might
be a little overrated too. :)

Re: Re: Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

Indeed Eric. Thankfully, I found the answer and the remainder of the
conversion to Gradle went reasonably smoothly over source code which
currently calls nothing but Java SE currently. That might now change
without too much added complication.

I observe that Gradle isn't fussed about backwards compatibility as much as
Java.

On Thu, 4 Aug 2022 at 04:01, Eric Bresie  wrote:

> Think there have been some changes in Gradle around compile and
> implementation (1).  May depend on what version of Gradle is in use as well.
>
> Eric Bresie
> ebre...@gmail.com
>
> (1) https://tomgregory.com/gradle-implementation-vs-compile-dependencies/
>
> On August 2, 2022 at 1:46:54 AM CDT, Owen Thomas <
> owen.paul.tho...@gmail.com> wrote:
> And restarting NetBeans (after rebooting my laptop) seems to have cleared
> the PeerDevice project of its rash. Now to include the remainder of the
> projects...
>
> On Tue, 2 Aug 2022 at 16:23, Owen Thomas 
> wrote:
>
>> Hey Laszlo.
>>
>> Sorry for not doing as you have asked, but while you were probably
>> composing your message, my Gradle project built!
>>
>> I don't know if that means that I'm good - (it usually doesn't) I need to
>> add a lot more subprojects to the root project - but all I did was to
>> change CliqueSpace/PeerDevice/build.gradle from:
>>
>> description = 'PeerDevice'
>>
>> dependencies {
>> *compile* project(':Concept')
>> }
>>
>> to:
>> description = 'PeerDevice'
>>
>> dependencies {
>> *implementation* project(':Concept')
>> }
>>
>> NetBeans is still telling me that the source code within the PeerDevice
>> project is not compiling. Perhaps there is a caching problem. (?)
>>
>> I hope I'm on to something. If perhaps I'm not, then please let me know.
>> This might also give you more information about the problem I'm having and
>> equip you or others with more pointers.
>>
>>   Owen.
>>
>> On Tue, 2 Aug 2022 at 15:50, Laszlo Kishalmi 
>> wrote:
>>
>>> Well, I've done and see a few dozen of Gradle builds, though this sounds
>>> alien to me. If you could share your project structure (main folders and
>>> their build.gradle files, maybe we can help sort this thing out.
>>> On 8/1/22 22:39, Owen Thomas wrote:
>>>
>>> While I've been doing other things, I have come to the conclusion that I
>>> need something, possibly in my build.gradle file of the Concept project,
>>> that refers to the Groovy method "compile". Perhaps I will need to start
>>> here.
>>>
>>> On Tue, 2 Aug 2022 at 14:02, Jason Abreu  wrote:
>>>
>>>> When I converted about 30 projects from Any to Gradle, including
>>>> multiple multi-project builds, I noticed a few peculiar things.
>>>>
>>>> Firstly, NetBeans gets a background task hung up every now and then.
>>>> The only solution for this was to exit NetBeans then find the hung up task
>>>> and kill it.  Once NetBeans restarted, the project scanning worked as
>>>> expected once more.
>>>>
>>>> Secondly, I have noticed that the Gradle dependency cache can get stale
>>>> and not refresh from repositories.  For this I would execute the Gradle
>>>> build task with the "--refresh-dependencies" (or something like that)
>>>> option to force Gradle to pull a fresh copy of the dependencies from the
>>>> repositories.
>>>>
>>>> Hope this helps!  I still consider myself new-ish to Gradle.  I do find
>>>> most of the support I need there in the NetBeans IDE for it, though.
>>>> However, my complaints about NetBeans relate to their lack of Jakarta EE 9
>>>> support, so far - but that's not anything to do with Gradle.
>>>>
>>>> --Jason
>>>>
>>>> On Mon, Aug 1, 2022, 22:59 Owen Thomas 
>>>> wrote:
>>>>
>>>>> Hello again. I am perplexed at the following problem.
>>>>>
>>>>> I have a multi-project build in a directory named "CliqueSpace". It's
>>>>> build.gradle file has the following:
>>>>>
>>>>> subprojects {
>>>>> apply plugin: 'java'
>>>>>
>>>>> repositories {
>>>>> mavenCentral()
>>>>> }
>>>>> }
>>>>>
>>>>> The settings.gradle file or the same directory has the following:
>>>>>
>>>>> rootProject.name = 'CliqueSpace'
>>

Re: How to set compile dependencies for Gradle in Netbeans.

[Owen Thomas]

Furthermore, if you read this
<https://tomgregory.com/gradle-implementation-vs-compile-dependencies/>,
the "compile" dependency has been deprecated since version 7 of Gradle. I'm
using 7.2. Apparently there are three types of dependency: compileOnly,
implementation, and runtimeOnly. The link gives details.


On Mon, 1 Aug 2022 at 17:45, Owen Thomas  wrote:

> Thanks for your comments Laszlo. They've helped me.
>
> I have created a multi-build script, and I have created all my Ant
> projects as subprojects of this, although I still have to put the source
> code into them and fix the dependencies.
>
> Perhaps it isn't really a concern, but I've noticed that NetBeans creates
> Gradle build scripts in Groovy. Is there any switch to instruct NetBeans to
> create them in Kotlin Script? Might there be an easy way to translate
> Groovy to Kotlin Script?
>
> Thanks again,
>
>   Owen.
>

Re: Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

And restarting NetBeans (after rebooting my laptop) seems to have cleared
the PeerDevice project of its rash. Now to include the remainder of the
projects...

On Tue, 2 Aug 2022 at 16:23, Owen Thomas  wrote:

> Hey Laszlo.
>
> Sorry for not doing as you have asked, but while you were probably
> composing your message, my Gradle project built!
>
> I don't know if that means that I'm good - (it usually doesn't) I need to
> add a lot more subprojects to the root project - but all I did was to
> change CliqueSpace/PeerDevice/build.gradle from:
>
> description = 'PeerDevice'
>
> dependencies {
> *compile* project(':Concept')
> }
>
> to:
> description = 'PeerDevice'
>
> dependencies {
> *implementation* project(':Concept')
> }
>
> NetBeans is still telling me that the source code within the PeerDevice
> project is not compiling. Perhaps there is a caching problem. (?)
>
> I hope I'm on to something. If perhaps I'm not, then please let me know.
> This might also give you more information about the problem I'm having and
> equip you or others with more pointers.
>
>   Owen.
>
> On Tue, 2 Aug 2022 at 15:50, Laszlo Kishalmi 
> wrote:
>
>> Well, I've done and see a few dozen of Gradle builds, though this sounds
>> alien to me. If you could share your project structure (main folders and
>> their build.gradle files, maybe we can help sort this thing out.
>> On 8/1/22 22:39, Owen Thomas wrote:
>>
>> While I've been doing other things, I have come to the conclusion that I
>> need something, possibly in my build.gradle file of the Concept project,
>> that refers to the Groovy method "compile". Perhaps I will need to start
>> here.
>>
>> On Tue, 2 Aug 2022 at 14:02, Jason Abreu  wrote:
>>
>>> When I converted about 30 projects from Any to Gradle, including
>>> multiple multi-project builds, I noticed a few peculiar things.
>>>
>>> Firstly, NetBeans gets a background task hung up every now and then.
>>> The only solution for this was to exit NetBeans then find the hung up task
>>> and kill it.  Once NetBeans restarted, the project scanning worked as
>>> expected once more.
>>>
>>> Secondly, I have noticed that the Gradle dependency cache can get stale
>>> and not refresh from repositories.  For this I would execute the Gradle
>>> build task with the "--refresh-dependencies" (or something like that)
>>> option to force Gradle to pull a fresh copy of the dependencies from the
>>> repositories.
>>>
>>> Hope this helps!  I still consider myself new-ish to Gradle.  I do find
>>> most of the support I need there in the NetBeans IDE for it, though.
>>> However, my complaints about NetBeans relate to their lack of Jakarta EE 9
>>> support, so far - but that's not anything to do with Gradle.
>>>
>>> --Jason
>>>
>>> On Mon, Aug 1, 2022, 22:59 Owen Thomas 
>>> wrote:
>>>
>>>> Hello again. I am perplexed at the following problem.
>>>>
>>>> I have a multi-project build in a directory named "CliqueSpace". It's
>>>> build.gradle file has the following:
>>>>
>>>> subprojects {
>>>> apply plugin: 'java'
>>>>
>>>> repositories {
>>>> mavenCentral()
>>>> }
>>>> }
>>>>
>>>> The settings.gradle file or the same directory has the following:
>>>>
>>>> rootProject.name = 'CliqueSpace'
>>>>
>>>> include ':Concept'
>>>> include ':PeerDevice'
>>>>
>>>> There are other includes in the above file, but I don't think it is
>>>> necessary to quote them here.
>>>>
>>>> In the Concept directory (CliqueSpace/Concept), build.gradle contains
>>>> the following:
>>>>
>>>> description = 'Concept'
>>>>
>>>> In the PeerDevice directory (CliqueSpace/PeerDevice), build.gradle
>>>> contains the following:
>>>>
>>>> description = 'PeerDevice'
>>>>
>>>> dependencies {
>>>> compile project(':Concept')
>>>> }
>>>>
>>>> At the moment, I only feel confident using gradle from the CLI. So,
>>>> when I open a CLI window within the CliqueSpace directory, and run "gradle
>>>> project PeerDevice", I get the following:
>>>>
>>>> owen@owen-Latitude-5511:~/Development/CliqueSpace/Code/trunk/CliqueSpace$
>>>> gradle pro

Re: Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

Hey Laszlo.

Sorry for not doing as you have asked, but while you were probably
composing your message, my Gradle project built!

I don't know if that means that I'm good - (it usually doesn't) I need to
add a lot more subprojects to the root project - but all I did was to
change CliqueSpace/PeerDevice/build.gradle from:

description = 'PeerDevice'

dependencies {
*compile* project(':Concept')
}

to:
description = 'PeerDevice'

dependencies {
*implementation* project(':Concept')
}

NetBeans is still telling me that the source code within the PeerDevice
project is not compiling. Perhaps there is a caching problem. (?)

I hope I'm on to something. If perhaps I'm not, then please let me know.
This might also give you more information about the problem I'm having and
equip you or others with more pointers.

  Owen.

On Tue, 2 Aug 2022 at 15:50, Laszlo Kishalmi 
wrote:

> Well, I've done and see a few dozen of Gradle builds, though this sounds
> alien to me. If you could share your project structure (main folders and
> their build.gradle files, maybe we can help sort this thing out.
> On 8/1/22 22:39, Owen Thomas wrote:
>
> While I've been doing other things, I have come to the conclusion that I
> need something, possibly in my build.gradle file of the Concept project,
> that refers to the Groovy method "compile". Perhaps I will need to start
> here.
>
> On Tue, 2 Aug 2022 at 14:02, Jason Abreu  wrote:
>
>> When I converted about 30 projects from Any to Gradle, including multiple
>> multi-project builds, I noticed a few peculiar things.
>>
>> Firstly, NetBeans gets a background task hung up every now and then.  The
>> only solution for this was to exit NetBeans then find the hung up task and
>> kill it.  Once NetBeans restarted, the project scanning worked as expected
>> once more.
>>
>> Secondly, I have noticed that the Gradle dependency cache can get stale
>> and not refresh from repositories.  For this I would execute the Gradle
>> build task with the "--refresh-dependencies" (or something like that)
>> option to force Gradle to pull a fresh copy of the dependencies from the
>> repositories.
>>
>> Hope this helps!  I still consider myself new-ish to Gradle.  I do find
>> most of the support I need there in the NetBeans IDE for it, though.
>> However, my complaints about NetBeans relate to their lack of Jakarta EE 9
>> support, so far - but that's not anything to do with Gradle.
>>
>> --Jason
>>
>> On Mon, Aug 1, 2022, 22:59 Owen Thomas 
>> wrote:
>>
>>> Hello again. I am perplexed at the following problem.
>>>
>>> I have a multi-project build in a directory named "CliqueSpace". It's
>>> build.gradle file has the following:
>>>
>>> subprojects {
>>> apply plugin: 'java'
>>>
>>> repositories {
>>> mavenCentral()
>>> }
>>> }
>>>
>>> The settings.gradle file or the same directory has the following:
>>>
>>> rootProject.name = 'CliqueSpace'
>>>
>>> include ':Concept'
>>> include ':PeerDevice'
>>>
>>> There are other includes in the above file, but I don't think it is
>>> necessary to quote them here.
>>>
>>> In the Concept directory (CliqueSpace/Concept), build.gradle contains
>>> the following:
>>>
>>> description = 'Concept'
>>>
>>> In the PeerDevice directory (CliqueSpace/PeerDevice), build.gradle
>>> contains the following:
>>>
>>> description = 'PeerDevice'
>>>
>>> dependencies {
>>> compile project(':Concept')
>>> }
>>>
>>> At the moment, I only feel confident using gradle from the CLI. So, when
>>> I open a CLI window within the CliqueSpace directory, and run "gradle
>>> project PeerDevice", I get the following:
>>>
>>> owen@owen-Latitude-5511:~/Development/CliqueSpace/Code/trunk/CliqueSpace$
>>> gradle project PeerDevice
>>>
>>> FAILURE: Build failed with an exception.
>>>
>>> * Where:
>>> Build file
>>> '/home/owen/Development/CliqueSpace/Code/trunk/CliqueSpace/PeerDevice/build.gradle'
>>> line: 4
>>>
>>> * What went wrong:
>>> A problem occurred evaluating project ':PeerDevice'.
>>> > Could not find method compile() for arguments [project ':Concept'] on
>>> object of type
>>> org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
>>>
>>> * Try:
>>> Run with --stacktrace option to get the stack trace. Run with --info or
>>> --debug option to get more log output. Run with --scan to get full insights.
>>>
>>> * Get more help at https://help.gradle.org
>>>
>>> BUILD FAILED in 493ms
>>>
>>> In short, having followed the instructions from a few different sources
>>> now, I don't know what I'm doing wrong. It might be good for the reader to
>>> know that Concept/src/main/java has source code in it that compiles, but
>>> PeerDevice/src/main/java also has source code where almost every Java
>>> module has broken out in a rash of unresolved dependencies.
>>>
>>> Thanks for any help,
>>>
>>>   Owen.
>>>
>>

Re: Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

While I've been doing other things, I have come to the conclusion that I
need something, possibly in my build.gradle file of the Concept project,
that refers to the Groovy method "compile". Perhaps I will need to start
here.

On Tue, 2 Aug 2022 at 14:02, Jason Abreu  wrote:

> When I converted about 30 projects from Any to Gradle, including multiple
> multi-project builds, I noticed a few peculiar things.
>
> Firstly, NetBeans gets a background task hung up every now and then.  The
> only solution for this was to exit NetBeans then find the hung up task and
> kill it.  Once NetBeans restarted, the project scanning worked as expected
> once more.
>
> Secondly, I have noticed that the Gradle dependency cache can get stale
> and not refresh from repositories.  For this I would execute the Gradle
> build task with the "--refresh-dependencies" (or something like that)
> option to force Gradle to pull a fresh copy of the dependencies from the
> repositories.
>
> Hope this helps!  I still consider myself new-ish to Gradle.  I do find
> most of the support I need there in the NetBeans IDE for it, though.
> However, my complaints about NetBeans relate to their lack of Jakarta EE 9
> support, so far - but that's not anything to do with Gradle.
>
> --Jason
>
> On Mon, Aug 1, 2022, 22:59 Owen Thomas  wrote:
>
>> Hello again. I am perplexed at the following problem.
>>
>> I have a multi-project build in a directory named "CliqueSpace". It's
>> build.gradle file has the following:
>>
>> subprojects {
>> apply plugin: 'java'
>>
>> repositories {
>> mavenCentral()
>> }
>> }
>>
>> The settings.gradle file or the same directory has the following:
>>
>> rootProject.name = 'CliqueSpace'
>>
>> include ':Concept'
>> include ':PeerDevice'
>>
>> There are other includes in the above file, but I don't think it is
>> necessary to quote them here.
>>
>> In the Concept directory (CliqueSpace/Concept), build.gradle contains the
>> following:
>>
>> description = 'Concept'
>>
>> In the PeerDevice directory (CliqueSpace/PeerDevice), build.gradle
>> contains the following:
>>
>> description = 'PeerDevice'
>>
>> dependencies {
>> compile project(':Concept')
>> }
>>
>> At the moment, I only feel confident using gradle from the CLI. So, when
>> I open a CLI window within the CliqueSpace directory, and run "gradle
>> project PeerDevice", I get the following:
>>
>> owen@owen-Latitude-5511:~/Development/CliqueSpace/Code/trunk/CliqueSpace$
>> gradle project PeerDevice
>>
>> FAILURE: Build failed with an exception.
>>
>> * Where:
>> Build file
>> '/home/owen/Development/CliqueSpace/Code/trunk/CliqueSpace/PeerDevice/build.gradle'
>> line: 4
>>
>> * What went wrong:
>> A problem occurred evaluating project ':PeerDevice'.
>> > Could not find method compile() for arguments [project ':Concept'] on
>> object of type
>> org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or
>> --debug option to get more log output. Run with --scan to get full insights.
>>
>> * Get more help at https://help.gradle.org
>>
>> BUILD FAILED in 493ms
>>
>> In short, having followed the instructions from a few different sources
>> now, I don't know what I'm doing wrong. It might be good for the reader to
>> know that Concept/src/main/java has source code in it that compiles, but
>> PeerDevice/src/main/java also has source code where almost every Java
>> module has broken out in a rash of unresolved dependencies.
>>
>> Thanks for any help,
>>
>>   Owen.
>>
>

Re: Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

Hi Andreas.

In some way, I agree with you: NetBeans could make the conversion process
easier. Although I have only been trying to move my Ant projects to Gradle
now for probably little more than a day, I have also tried to use IntelliJ,
and their advice seems unable to solve the problem that I am having. The
solutions in IntelliJ I have read so far involve fiddling in an obscure
corner of the projects' settings, and they have not resolved my problem
either.

As I demonstrated, the problem appears to be with my Gradle project. I'm
using the CLI to issue commands to Gradle. The build is failing there, and
the solution to fix it seems to reside with telling Gradle what it wants to
hear.

Thanks again Andreas; I hope someone can tell me what Gradle wants to hear.
If perhaps you can help me show me how to get my projects to work in
IntelliJ, then I would indeed be most thankful.

  Owen.

On Tue, 2 Aug 2022 at 13:04, Andreas Reichel 
wrote:

> Owen, I have had the same problem and found only IntelliJ supporting
> Gradle Multi Projects properly. It made me switch.
>
> @Netbeans: I am really sorry to write that. I have used and loved Netbeans
> for my entire life. But not liking Maven (not at all!) and unable to stick
> with Ant, this is what it came to.
>
> On Tue, 2022-08-02 at 12:59 +1000, Owen Thomas wrote:
>
> Hello again. I am perplexed at the following problem.
>
> I have a multi-project build in a directory named "CliqueSpace". It's
> build.gradle file has the following:
>
> subprojects {
> apply plugin: 'java'
>
> repositories {
> mavenCentral()
> }
> }
>
> The settings.gradle file or the same directory has the following:
>
> rootProject.name = 'CliqueSpace'
>
> include ':Concept'
> include ':PeerDevice'
>
> There are other includes in the above file, but I don't think it is
> necessary to quote them here.
>
> In the Concept directory (CliqueSpace/Concept), build.gradle contains the
> following:
>
> description = 'Concept'
>
> In the PeerDevice directory (CliqueSpace/PeerDevice), build.gradle
> contains the following:
>
> description = 'PeerDevice'
>
> dependencies {
> compile project(':Concept')
> }
>
> At the moment, I only feel confident using gradle from the CLI. So, when I
> open a CLI window within the CliqueSpace directory, and run "gradle project
> PeerDevice", I get the following:
>
> owen@owen-Latitude-5511:~/Development/CliqueSpace/Code/trunk/CliqueSpace$
> gradle project PeerDevice
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file
> '/home/owen/Development/CliqueSpace/Code/trunk/CliqueSpace/PeerDevice/build.gradle'
> line: 4
>
> * What went wrong:
> A problem occurred evaluating project ':PeerDevice'.
> > Could not find method compile() for arguments [project ':Concept'] on
> object of type
> org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> BUILD FAILED in 493ms
>
> In short, having followed the instructions from a few different sources
> now, I don't know what I'm doing wrong. It might be good for the reader to
> know that Concept/src/main/java has source code in it that compiles, but
> PeerDevice/src/main/java also has source code where almost every Java
> module has broken out in a rash of unresolved dependencies.
>
> Thanks for any help,
>
>   Owen.
>
>
>

Gradle won't resolve dependency: what's wrong here?

[Owen Thomas]

Hello again. I am perplexed at the following problem.

I have a multi-project build in a directory named "CliqueSpace". It's
build.gradle file has the following:

subprojects {
apply plugin: 'java'

repositories {
mavenCentral()
}
}

The settings.gradle file or the same directory has the following:

rootProject.name = 'CliqueSpace'

include ':Concept'
include ':PeerDevice'

There are other includes in the above file, but I don't think it is
necessary to quote them here.

In the Concept directory (CliqueSpace/Concept), build.gradle contains the
following:

description = 'Concept'

In the PeerDevice directory (CliqueSpace/PeerDevice), build.gradle contains
the following:

description = 'PeerDevice'

dependencies {
compile project(':Concept')
}

At the moment, I only feel confident using gradle from the CLI. So, when I
open a CLI window within the CliqueSpace directory, and run "gradle project
PeerDevice", I get the following:

owen@owen-Latitude-5511:~/Development/CliqueSpace/Code/trunk/CliqueSpace$
gradle project PeerDevice

FAILURE: Build failed with an exception.

* Where:
Build file
'/home/owen/Development/CliqueSpace/Code/trunk/CliqueSpace/PeerDevice/build.gradle'
line: 4

* What went wrong:
A problem occurred evaluating project ':PeerDevice'.
> Could not find method compile() for arguments [project ':Concept'] on
object of type
org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 493ms

In short, having followed the instructions from a few different sources
now, I don't know what I'm doing wrong. It might be good for the reader to
know that Concept/src/main/java has source code in it that compiles, but
PeerDevice/src/main/java also has source code where almost every Java
module has broken out in a rash of unresolved dependencies.

Thanks for any help,

  Owen.

Re: How to set compile dependencies for Gradle in Netbeans.

[Owen Thomas]

Thanks for your comments Laszlo. They've helped me.

I have created a multi-build script, and I have created all my Ant projects
as subprojects of this, although I still have to put the source code into
them and fix the dependencies.

Perhaps it isn't really a concern, but I've noticed that NetBeans creates
Gradle build scripts in Groovy. Is there any switch to instruct NetBeans to
create them in Kotlin Script? Might there be an easy way to translate
Groovy to Kotlin Script?

Thanks again,

  Owen.

How to set compile dependencies for Gradle in Netbeans.

[Owen Thomas]

Hello NetBeans people.

I have just started migrating my projects from Ant to Gradle in NetBeans.
Some of them have compile dependencies on others, and I'm currently
wondering how I set them up in NetBeans.

I'm very new to Gradle, but I can no longer ignore the light being cast by
wise people, and I concede that my work needs exposure to all the goodies
available through a build tool like Gradle. Any help would be greatly
appreciated at this early and tentative stage of my journey.

Thanks,

  Owen.

Re: Where is my post?

[Owen Thomas]

Haha, thanks!

On Sat, 5 Feb 2022 at 23:16, Amn  wrote:

> Sorry, I ment to type 'file.java'. Darn spell checker [image: :-)]
> On Sat, 2022-02-05 at 23:14 +1100, Owen Thomas wrote:
>
> On Sat, 5 Feb 2022 at 22:44, Amn  wrote:
>
> I recently posted the following question :
> 
> How can I add external source code (flecks) to my project?
> All the information I found is related to adding libraries (flecks)
> to the project, which I have already done (thanks folks).
>
>
>
> Here you are.
>
> IHNI what a fleck is though, so I can't help you there.
>
>
>
>

Re: Where is my post?

[Owen Thomas]

On Sat, 5 Feb 2022 at 22:44, Amn  wrote:

> I recently posted the following question :
> 
> How can I add external source code (flecks) to my project?
> All the information I found is related to adding libraries (flecks)
> to the project, which I have already done (thanks folks).
>
>
Here you are.

IHNI what a fleck is though, so I can't help you there.

Re: Happy holidays all

[Owen Thomas]

I have used IntelliJ and Eclipse, and after not much of that, I went back
to NetBeans for my Java projects because I still think NetBeans is the best
IDE for Java Developers. Have a great year ahead.

On Sat, 25 Dec 2021 at 04:23, Geertjan Wielenga  wrote:

> Hi all,
>
> Happy holidays all. :-)
>
> It’s been another great year of quarterly Apache NetBeans releases. In the
> coming year, we’re looking forward to and can expect:
>
> 1. Better start up experience via direct integration of nb-javac into
> Apache NetBeans.
>
> 2. Whole number releases, i.e., the next release will be 13, then 14, then
> 15, etc.
>
> 3. Better start up experience via bundling of OpenJDK with Apache
> NetBeans, which can’t be done as part of Apache because of the licensing of
> the OpenJDK, and will be hosted below, at least:
>
> https://www.codelerity.com/netbeans/
>
> The above developments, all of which have been discussed at length or at
> least mentioned on the dev mailing list several times (please join that
> list if you’re not on it yet), together will put Apache NetBeans in a
> strong position to offer a more complete and coherent basis for further
> contributions and usage in developer communities.
>
> Thanks all for your involvement and support for this project, for some of
> you over many years indeed. :-)
>
> Kind regards,
>
> Gj
>
> PMC Chair
>

Re: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

On Fri, 29 Oct 2021 at 11:48, Owen Thomas 
wrote:

> I say the following. Have an abstract checked exception class in the Java
> SE API. Call it, say, Checked*Managed*Exception. Descendents of this
> class behave like any other checked exception, with perhaps a few caveats
> [covered in the conversation we are having]...
>

Re: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

On Tue, 2 Nov 2021 at 06:35, Emilian Bold  wrote:

> It looks to me that the JVM doesn't have the concept of checked
> exceptions, only Java has. So, it may be valid bytecode to just rip out
> checked exception from the method signatures. New compilations, targeting a
> modified JAR, will not complain about the checked exception. At runtime
> they will be handled by the normal try-catch chain.
>
> Which is to say, bytecode processing may be sufficient. No need for
> language-wide changes.
>
> --emi
>

I think I understand that checked exceptions are only relevant to the Java
compiler; the "checking" is only performed by the compiler and the JVM
doesn't care about whether a calling method throws or catches checked
exceptions. This is, as I understand, why a language like Kotlin can omit
the feature from its compiler and call Java methods that throw checked
exceptions without problems. So, I think some small and contained changes
to the runtime might be appropriate, but the changes would not be too
invasive. The changes would be relevant only in the circumstance where a
Java module descriptor specifies which managed exceptions are thrown,
caught or ignored and so these changes would be backwards compatible.

I now think I prefer this "managed" term in place of "checked" because the
runtime environment doesn't care about checked exceptions, and I don't
think it a good idea to change this behaviour. Maybe the feature I am
describing would also be deemed fit to be appropriated by others like
Kotlin.

If a feature like this can garner broader support, I might even make it
official and look at how to apply through the JCP.

  Owen.


> On Mon, Nov 1, 2021 at 9:23 PM Alonso Del Arte 
> wrote:
>
>> > Might it be good to have a way to indicate to others that your module
>> can guarantee that checked exceptions have not been buried inside unchecked
>> ones?
>>
>> Okay, that might be good to know. We can certainly write that in the
>> Javadoc, but without a system like what you're proposing we would be on the
>> honor system.
>>
>> As you might know, Scala inventor Martin Odersky wrote the Java 1.3
>> compiler. Java was not evolving as fast as he wanted it to. He put a lot of
>> things into Scala that Java eventually adopted later, and some that will be
>> added to future versions of Java.
>>
>> But his approach was to make all exceptions unchecked, though you can add
>> an @throws annotation for the sake of interoperability with Java.
>> Clearly that's something Java will never adopt.Your idea of managed
>> exceptions seems likelier to be added.
>>
>> Suppose that Java 19 adds managed exceptions. What changes would an IDE
>> like NetBeans have to make in response to that?
>>
>> Al
>>
>> On Sun, Oct 31, 2021 at 11:22 PM Owen Thomas 
>> wrote:
>>
>>>
>>>
>>> On Mon, 1 Nov 2021 at 09:51, Alonso Del Arte 
>>> wrote:
>>>
>>>> >  Although I do it often enough, I'm not a fan of wrapping a checked
>>>> exception in a RuntimeException or even another checked exception like
>>>> IOException.
>>>>
>>>> I'm not either. Nor do I like how AssertionError has a constructor
>>>> that takes an Object rather than specifically a Throwable. But usually
>>>> (though not always), a better way occurs to me during refactoring. I'm not
>>>> sure I see the benefit of managed exceptions.
>>>>
>>>
>>> Might it be good to have a way to indicate to others that your module
>>> can guarantee that checked exceptions have not been buried inside unchecked
>>> ones?
>>>
>>> I'm wondering if perhaps it might be good to generate a compile error in
>>> code that threw anything other than the type of managed exception that was
>>> indicated to be thrown in an associated module descriptor?
>>>
>>>   Owen.
>>>
>>
>>
>> --
>> Alonso del Arte
>> Author at SmashWords.com
>> <https://www.smashwords.com/profile/view/AlonsoDelarte>
>> Musician at ReverbNation.com <http://www.reverbnation.com/alonsodelarte>
>>
>

Re: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

On Mon, 1 Nov 2021 at 09:51, Alonso Del Arte 
wrote:

> >  Although I do it often enough, I'm not a fan of wrapping a checked
> exception in a RuntimeException or even another checked exception like
> IOException.
>
> I'm not either. Nor do I like how AssertionError has a constructor that
> takes an Object rather than specifically a Throwable. But usually (though
> not always), a better way occurs to me during refactoring. I'm not sure I
> see the benefit of managed exceptions.
>

Might it be good to have a way to indicate to others that your module can
guarantee that checked exceptions have not been buried inside unchecked
ones?

I'm wondering if perhaps it might be good to generate a compile error in
code that threw anything other than the type of managed exception that was
indicated to be thrown in an associated module descriptor?

  Owen.

Re: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

Perhaps these type of exceptions can be called "managed" exceptions. Two
syllables instead of the monosyllabic "checked" might draw interest to the
possibility that a slightly more complicated mechanism can make things
easier for the developer. I don't know.

On Sun, 31 Oct 2021 at 23:07, Owen Thomas 
wrote:

> On Sun, 31 Oct 2021 at 18:24, Emilian Bold  wrote:
>
>> I don't understand your proposal. You are trying to explain it in an
>> almost formal way but I don't know what it means...
>>
>
> Thank you for trying Emilian. Sometimes I find it hard to speak directly.
> Hopefully you'll find some sense in what I'm trying to talk about in this
> reply. :)
>
> Please also note that I speak from a position of ignorance about Java
> modules. I hope you can fill in the blanks with your own understanding of
> Java modules which I assume is better than mine.
>
>
>> For eg. not sure what "ignored" means. Does it behave like a Runtime
>> Exception? Or is it just not thrown?
>>
>
> I think it fair that javac should not compile your code if you attempt to
> catch or if you declare that any method throws an exception that is
> "ignored". Perhaps you may think that is too harsh, but I'm less than eager
> to accept anything more accommodating at this point in time until I hear a
> compelling reason for why this might be better.
>
>
>> Same with the other 2 options.
>>
>
> Okay. 
>
> Imagine this scenario. Hopefully, this use case describes what happens
> when an exception that extends this CheckedException class is "ignored". If
> you get the use-case I am describing here, you can probably imagine what
> might happen in other scenarios.
>
> So, you are developing a library that depends on another library. This
> other library declares in a module descriptor that a particular exception
> is "thrown". It has to do this because this exception extends
> CheckedException, and at least one method in this module declares that it
> throws this exception.
>
> You're in charge of the module descriptors in your library. In your
> library, you have a module governed by a descriptor which says that the
> exception thrown from the module defined above is "ignored". You have to
> care about this because at least one of the methods defined in your module
> calls at least one of the methods defined in the module above. When you
> call any method declared within the above defined module from your module,
> your calling method cannot either catch this ignored exception in your
> code, nor declare that it throws this exception.
>
> Importantly, I think that the checked behaviour of such an exception has
> been preserved. Modules defined by others that call one or more methods
> defined in yours would likewise have to do something with this ignored
> exception just as you have done. A developer using your library would have
> to declare in their module descriptor what they are going to do with the
> exception that you have ignored if they are going to call any methods of
> your module: either to declare that they are "ignored" or "caught"...
> another use case.
>
> So, you have "ignored" the fact that a method you call throws a particular
> extension of the class CheckedException. Your methods cannot catch, or
> declare that they throw this exception because you said in your module's
> descriptor that you wanted this concern abstracted away for you. You have,
> however, passed this concern onto anyone who might use your module. Others
> are free to do with their module as you have done with yours, but they
> still have to do something to address the fact that this checked exception
> you have elected to ignore has been passed through your module to theirs.
>
>   Owen.
>
> PS:
> *A small, and I think favourable twist in the behaviour of checked
> exceptions expressed through this mechanism is that one might be able to,
> say, have Object.equals() throw these type of checked exceptions. This
> would perhaps slightly and temporarily modify the signature for
> Object.equals() which has been overridden in some module where a particular
> checked exception was "thrown" until the exception was handled somewhere in
> another dependent module where the exception was "caught". I can't at this
> moment see why this would be a problem; I see it as something I would like.*
>
> PPS: Perhaps, if another developer's library implements a mechanism called
> directly from Thread.run(), any "ignored" exception will just behave like
> an unchecked exception. Perhaps however, it would be more in-keeping with
> the original intentions of the checked exception 

Re: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

On Sun, 31 Oct 2021 at 18:24, Emilian Bold  wrote:

> I don't understand your proposal. You are trying to explain it in an
> almost formal way but I don't know what it means...
>

Thank you for trying Emilian. Sometimes I find it hard to speak directly.
Hopefully you'll find some sense in what I'm trying to talk about in this
reply. :)

Please also note that I speak from a position of ignorance about Java
modules. I hope you can fill in the blanks with your own understanding of
Java modules which I assume is better than mine.


> For eg. not sure what "ignored" means. Does it behave like a Runtime
> Exception? Or is it just not thrown?
>

I think it fair that javac should not compile your code if you attempt to
catch or if you declare that any method throws an exception that is
"ignored". Perhaps you may think that is too harsh, but I'm less than eager
to accept anything more accommodating at this point in time until I hear a
compelling reason for why this might be better.


> Same with the other 2 options.
>

Okay. 

Imagine this scenario. Hopefully, this use case describes what happens when
an exception that extends this CheckedException class is "ignored". If you
get the use-case I am describing here, you can probably imagine what might
happen in other scenarios.

So, you are developing a library that depends on another library. This
other library declares in a module descriptor that a particular exception
is "thrown". It has to do this because this exception extends
CheckedException, and at least one method in this module declares that it
throws this exception.

You're in charge of the module descriptors in your library. In your
library, you have a module governed by a descriptor which says that the
exception thrown from the module defined above is "ignored". You have to
care about this because at least one of the methods defined in your module
calls at least one of the methods defined in the module above. When you
call any method declared within the above defined module from your module,
your calling method cannot either catch this ignored exception in your
code, nor declare that it throws this exception.

Importantly, I think that the checked behaviour of such an exception has
been preserved. Modules defined by others that call one or more methods
defined in yours would likewise have to do something with this ignored
exception just as you have done. A developer using your library would have
to declare in their module descriptor what they are going to do with the
exception that you have ignored if they are going to call any methods of
your module: either to declare that they are "ignored" or "caught"...
another use case.

So, you have "ignored" the fact that a method you call throws a particular
extension of the class CheckedException. Your methods cannot catch, or
declare that they throw this exception because you said in your module's
descriptor that you wanted this concern abstracted away for you. You have,
however, passed this concern onto anyone who might use your module. Others
are free to do with their module as you have done with yours, but they
still have to do something to address the fact that this checked exception
you have elected to ignore has been passed through your module to theirs.

  Owen.

PS:
*A small, and I think favourable twist in the behaviour of checked
exceptions expressed through this mechanism is that one might be able to,
say, have Object.equals() throw these type of checked exceptions. This
would perhaps slightly and temporarily modify the signature for
Object.equals() which has been overridden in some module where a particular
checked exception was "thrown" until the exception was handled somewhere in
another dependent module where the exception was "caught". I can't at this
moment see why this would be a problem; I see it as something I would like.*

PPS: Perhaps, if another developer's library implements a mechanism called
directly from Thread.run(), any "ignored" exception will just behave like
an unchecked exception. Perhaps however, it would be more in-keeping with
the original intentions of the checked exception mechanism that a compiler
error would be issued, and hence I like this latter scenario better.



>
> I think you could do a byte code processor and tweak checked exceptions
> but of course you would change signatures.
>
> --emi
>
> vin., 29 oct. 2021, 03:48 Owen Thomas  a
> scris:
>
>> G'day.
>>
>> Upon seeing some recent emails from this group expressing a somewhat
>> philosophical tone about how the evolving landscape of paradigms in
>> software development may be putting a strain on Java, I just wish to put
>> some comments that others might find interesting down about how a specific
>> Java feature, namely checked exceptions, can be improved so th

Re: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

On Sat, 30 Oct 2021 at 17:53, Owen Thomas 
wrote:

> If checked exceptions could be selectively suppressed like this, then
> perhaps I could override Object.equals() with a throws clause that threw
> any exception [that extends CheckedException] I chose. Developers of
> libraries that were dependent on mine could "ignore" this if that's what
> they wanted.
>
> Thinking about it now, I can't see why that would be a bad thing.
>

Fwd: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

If checked exceptions could be selectively suppressed like this, then
perhaps I could override Object.equals() with a throws clause that threw
any exception I chose. Developers of libraries that were dependent on mine
could "ignore" this if that's what they wanted.

Thinking about it now, I can't see why that would be a bad thing.

Re: OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

Although I do it often enough, I'm not a fan of wrapping a checked
exception in a RuntimeException or even another checked exception like
IOException. I think this solution is ugly, bug prone, and can be avoided
through what I believe are relatively minor and unobtrusive enhancements
given in my suggestions.

Furthermore:

On Fri, 29 Oct 2021 at 11:48, Owen Thomas 
wrote:

> The emphasis above is used to underscore the utility that my suggestion is
> trying to convey. I think that with perhaps a few tweaks, this is a
> flexible suggestion. Although I do not (not yet perhaps... I just need a
> compelling reason to) know much about Java modules, this system of
> selectively dealing with checked exceptions appears as a very good
> candidate for expression there.
>

It definitely looks like the best place to express a feature like this is
in a Java module descriptor. Changes would also be made primarily to the
language specification, and also perhaps to the JVM - though I'm not too
sure if this is necessary. Hece, any other "deployment descriptor" I have
mentioned in my previous email refers to the Java module descriptor. My
ramblings were still perhaps too unsettled to make this clear; I hope I'm
writing something sensible here.

Have a good day.

OT perhaps (better directed to Oracle?): Suggestions for improving checked exceptions in Java.

[Owen Thomas]

G'day.

Upon seeing some recent emails from this group expressing a somewhat
philosophical tone about how the evolving landscape of paradigms in
software development may be putting a strain on Java, I just wish to put
some comments that others might find interesting down about how a specific
Java feature, namely checked exceptions, can be improved so that again,
Java perhaps can show how to do something well enough that other languages
might try and copy it.

I say the following. Have an abstract checked exception class in the Java
SE API. Call it, say, CheckedException. Descendents of this class behave
like any other checked exception, with perhaps a few caveats explained in
this email.

The build script of a deployable artifact (an application or library, but
in this case, probably a library explains the situation more clearly)
somehow indicates that this deployable artifact (hereon referred to as a
library) can declare that descendents of CheckedExceptions (never the
CheckedException class itself) are:

   1. thrown: A more specific descendent of a checked exception under this
   clause occurs in the throws clause of a method that is exposed to libraries
   that are dependent on this one.

   2. caught: A more specific descendent of a checked exception under this
   clause occurs in the catch block of a method that calls a method from a
   library on which this one depends.

   3. ignored: Neither of the above scenarios occurs. *However, methods in
   this library that call methods that throw a descendent of a checked
   exception under this clause do not themselves explicitly declare that they
   throw or catch and deal with the given checked exception*.

If a library declares that it throws or ignores a descendent of a
CheckedException, in its build script or other deployment descriptor, then
any dependent library must either declare that that CheckedException is
thrown, caught, or ignored.

The emphasis above is used to underscore the utility that my suggestion is
trying to convey. I think that with perhaps a few tweaks, this is a
flexible suggestion. Although I do not (not yet perhaps... I just need a
compelling reason to) know much about Java modules, this system of
selectively dealing with checked exceptions appears as a very good
candidate for expression there.

These are just suggestions and I put them out there because someone with
some clout in shaping the future of the Java SE API might think these
suggestions are worth considering further. Happy to share and perhaps to
talk about it here if others share a similar interest.

Have a great day. :)

  Owen.

Re: Pssst! [Kotlin Support]

[Owen Thomas]

It's a nice sentiment (and one I agree with) but I've recently been
employed by people who one might say have swallowed this Kotlin/IntelliJ
cool-aide.

Therefore I either learn Kotlin, or I find another job; before this, I was
unemployed (on a pension) for more than 13 years. Hence, I would rather
that this job succeeded if at all possible. If NetBeans supported Kotlin,
I'd use NetBeans.

On Mon, 11 Oct 2021 at 23:36, Neil C Smith  wrote:

> On Sun, 10 Oct 2021 at 14:42, Emilian Bold  wrote:
> > Looks like Kotlin is working as intended and funneling people into
> IntelliJ.
>
> +1 - this!  IMO it's a good thing when developer tools and languages
> have some distance.
>
> Best wishes,
>
> Neil
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Re: Pssst! [Kotlin Support]

[Owen Thomas]

I would agree with you Emilian. Similar forces drove me to Java 15 years
ago. I have felt for the longest time that my nature for mechanical
curiosity has been used to fulfil the pernicious narcissism of others. I
imagine that in the future, my dalliance with Kotlin may come at some
financial expense.

I just write computer programs.

On Mon, 11 Oct 2021 at 00:42, Emilian Bold  wrote:

> Looks like Kotlin is working as intended and funneling people into
> IntelliJ.
>
> --emi
>
> On Sun, Oct 10, 2021 at 5:38 AM Owen Thomas 
> wrote:
> >
> > I have found myself cajoled into using IntelliJ because it allows one to
> use Java and Kotlin sources simultaneously. To do this however, I have had
> to create a new project using Gradle and copy my Java sources to this new
> project because IntelliJ thumbs it's nose at Ant projects. So, now I am
> pondering the prospect of continuing with the Ant project in NetBeans and
> discarding the Kotlin sources, or making the transition to Gradle (and
> perhaps IntelliJ) permanent. The second option (minus the move to IntelliJ
> perhaps) is inevitable, but I do feel as though IntelliJ is making the
> decision on what is an appropriate build tool for me at a time when I do
> not think it necessary to entertain such a move.
> >
> > I'd like it better if NetBeans was able to intermix Kotlin and Java in a
> way similar to IntelliJ, but without making a judgement call on what build
> tool I choose to use.
> >
> >
> > On Sun, 10 Oct 2021 at 00:23, Eric Bresie  wrote:
> >>
> >> Unrelated but at some point, there was discussion of integrating Kotlin
> support (I believe donated by JetBrain developer)…did anything further
> happen with that?
> >>
> >> Or is Kotlin another candidate for “new LSP language implementation”?
> >>
> >> Eric
> >>
> >> On Fri, Oct 8, 2021 at 11:03 PM Owen Thomas 
> wrote:
> >>>
> >>> Okay... I make a provisional withdrawal and reserve the right to
> reassert.
> >>>
> >>> On Fri, 8 Oct 2021 at 18:59, Owen Thomas 
> wrote:
> >>>>
> >>>> Java and Kotlin interoperability is a fabrication. Stick with Java or
> stick with Kotlin. Don't try it; it will only lead one to rip one's face
> off.
> >>
> >> --
> >> Eric Bresie
> >> ebre...@gmail.com
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Re: Pssst! [Kotlin Support]

[Owen Thomas]

I have found myself cajoled into using IntelliJ because it allows one to
use Java and Kotlin sources simultaneously. To do this however, I have had
to create a new project using Gradle and copy my Java sources to this new
project because IntelliJ thumbs it's nose at Ant projects. So, now I am
pondering the prospect of continuing with the Ant project in NetBeans and
discarding the Kotlin sources, or making the transition to Gradle (and
perhaps IntelliJ) permanent. The second option (minus the move to IntelliJ
perhaps) is inevitable, but I do feel as though IntelliJ is making the
decision on what is an appropriate build tool for me at a time when I do
not think it necessary to entertain such a move.

I'd like it better if NetBeans was able to intermix Kotlin and Java in a
way similar to IntelliJ, but without making a judgement call on what build
tool I choose to use.


On Sun, 10 Oct 2021 at 00:23, Eric Bresie  wrote:

> Unrelated but at some point, there was discussion of integrating Kotlin
> support (I believe donated by JetBrain developer)…did anything further
> happen with that?
>
> Or is Kotlin another candidate for “new LSP language implementation”?
>
> Eric
>
> On Fri, Oct 8, 2021 at 11:03 PM Owen Thomas 
> wrote:
>
>> Okay... I make a provisional withdrawal and reserve the right to reassert.
>>
>> On Fri, 8 Oct 2021 at 18:59, Owen Thomas 
>> wrote:
>>
>>> Java and Kotlin interoperability is a fabrication. Stick with Java or
>>> stick with Kotlin. Don't try it; it will only lead one to rip one's face
>>> off.
>>>
>> --
> Eric Bresie
> ebre...@gmail.com
>

Re: Pssst!

[Owen Thomas]

Okay... I make a provisional withdrawal and reserve the right to reassert.

On Fri, 8 Oct 2021 at 18:59, Owen Thomas  wrote:

> Java and Kotlin interoperability is a fabrication. Stick with Java or
> stick with Kotlin. Don't try it; it will only lead one to rip one's face
> off.
>

Pssst!

[Owen Thomas]

Java and Kotlin interoperability is a fabrication. Stick with Java or stick
with Kotlin. Don't try it; it will only lead one to rip one's face off.

NetBeans isn't syntax checking Kotlin source?

[Owen Thomas]

Hello.

I would like to try writing Kotlin code from NetBeans. I'm using 12.4. I
create a new Kotlin source file from the new file wizard and start typing.
I find that there is no syntax checking; no matter what drivel I write, I
see no red.

What's with this?

Re: James Gosling podcast / Embedded Java

[Owen Thomas]

On Fri, 23 Jul 2021 at 04:25, Geertjan Wielenga  wrote:

> https://foojay.io/today/foojay-podcast-2/
>
> A fun podcast, enjoy!
>
> Gj
>

Indeed, thanks Geertjan.

Re: Losing instanceof variables when class renamed.

[Owen Thomas]

Goodo Jan. Thanks for letting me know. :)

On Tue, 13 Jul 2021 at 16:32, Jan Lahoda  wrote:

> Thanks for the report, Owen. I am looking into this.
>
> Jan
>
> On Sun, Jul 11, 2021 at 7:30 AM Owen Thomas 
> wrote:
>
>> Hello.
>>
>> Thought this might be of interest. When using NB 12.4 with Java SE 16
>> SDK, I'm beginning to use the newly available enhancement to the instanceof
>> operator.
>>
>> When I rename a class in which this operator is used, the renaming
>> process seems to remove the variable name that follows the instanceof
>> operator. The variable 'sig' is removed after the class is renamed to
>> FrameSignal.
>>
>> It might be of interest to some people here; there may even be a bug
>> already outstanding for this apparent problem. See the attached screenshot
>> of what happens to my code when I rename the class.
>>
>>   Owen.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Losing instanceof variables when class renamed.

[Owen Thomas]

Hello.

Thought this might be of interest. When using NB 12.4 with Java SE 16 SDK,
I'm beginning to use the newly available enhancement to the instanceof
operator.

When I rename a class in which this operator is used, the renaming process
seems to remove the variable name that follows the instanceof operator. The
variable 'sig' is removed after the class is renamed to FrameSignal.

It might be of interest to some people here; there may even be a bug
already outstanding for this apparent problem. See the attached screenshot
of what happens to my code when I rename the class.

  Owen.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: No main classes found

[Owen Thomas]

It might help you to know Zulfi that a method's "signature" is more than
just its name. It also includes the number and types of each of its
parameters. You can create more than one method with the same name as long
as the parameters are different. This is why the compiler didn't complain
that you declared the main with a String (not a String[]).

On Tue, 29 Jun 2021 at 12:48, Scott Palmer  wrote:

> Yeah, the main method shown in your screen shot has the wrong signature..
> taking a String instead of a String []
>
> Scott
>
> On Jun 28, 2021, at 9:26 PM, Andreas Reichel <
> andr...@manticore-projects.com> wrote:
>
> Greetings.
>
> You will need to set the "Main Class" in the Project Properties as shown
> below.
> The "Main Class" will need to have a method "public static void
> main(String[] args)"
>
> Best regards
> Andreas
>
> 
>
> On Tue, 2021-06-29 at 01:16 +, Zulfi Khan wrote:
>
> Hi,
> I am working on Netbeans 12.4.
>
> I have created the project FibSeries2. When I am trying to run it by
> selecting the project name from the left pane and right clicking the mouse
> and then selecting “Run”, I am getting a small window which says “no main
> classes Found”.
>
> But when I click Build, it works but run is not working. When I click on
> run,  a small window comes, which tell, no main found.
>
>
> Please guide me.
>
> I have attached the image.
>
>
> Zulfi.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: JavaScript Framework's

[Owen Thomas]

Hmmm... truthiness... naah.

On Sun, 27 Jun 2021 at 13:14, Brain Rebooting 
wrote:

> Dear all,
>
> With due respect, I can't understand why netbeans doesn't support a single
> latest JavaScript framework. I mean, angular/react/vue are extremely
> popular now a days and are must. Though netbeans claims itself a full ide
> for JavaScript. But it supports not a single javascript framework. As a
> netbeans fan boy since last 3 years, I find it inferior.
>
> If there is no one to build those tools for netbeans, then at least can't
> we open a donation account and gather money hire someone with expertise on
> those tech to build tools to support those frameworks in netbeans?
>
> I realizes that, why people are leaving netbeans due to existential
> reasons. If I need to use any text editor to work with those frameworks,
> then still I already writing code outside of netbeans.
>
> We use ide for what? By definition, so that we can write/test/debug/deploy
> everything from one place.
>
> Its not my request as you already know. Even eclipse dont support these
> framework's for free. I saw they recently start angular/react option but
> thats also paid. Our last hope is remains only netbeans.
>
>
> Samiul Alom Sium
> Bangladesh
>

Re: @Nonnull?

[Owen Thomas]

No Maven or Gradle. Ant only. :b

On Fri, 25 Jun 2021 at 17:34, Owen Thomas 
wrote:

> I've just been informed that @Nonnull could be part of javax (the
> documentation does appear to state this). I don't think I have access to
> this package because I'm not using anything other than the Java SE API.
>
>

Re: @Nonnull?

[Owen Thomas]

I've just been informed that @Nonnull could be part of javax (the
documentation does appear to state this). I don't think I have access to
this package because I'm not using anything other than the Java SE API.

Re: @Nonnull?

[Owen Thomas]

I commonly generate custom runtime exceptions for situations like this, but
it perhaps would be nice to have the compiler flag where this situation is
likely to happen too.

Perhaps it is a feature of a later release...

On Fri, 25 Jun 2021 at 15:30, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> Yes, googled a bit for this, doubt it exists as a feature in JDK 16.
>
> Gj
>
> On Fri, 25 Jun 2021 at 07:23, Lars Bruun-Hansen 
> wrote:
>
>> What @Nonnull in Java ?  Have I missed some news about a new feature
>> in the JDK?
>> Various third party libraries implement some form of non-null
>> annotation and you will have to use one such library ... unless I
>> missed some new JDK feature.  :-)
>>
>>
>>
>> /Lars
>>
>>
>>
>>
>>
>> On Fri, Jun 25, 2021 at 5:40 AM Owen Thomas 
>> wrote:
>> >
>> > Ok, thanks Geertjan. Let me know what you find.
>> >
>> > On Fri, 25 Jun 2021 at 12:59, Geertjan Wielenga <
>> geertjan.wiele...@googlemail.com> wrote:
>> >>
>> >>
>> >> Maybe it doesn’t support it yet. Will try to find out.
>> >>
>> >> Gj
>> >>
>> >> On Fri, 25 Jun 2021 at 04:39, Owen Thomas 
>> wrote:
>> >>>
>> >>> I'm using NB 12.4 with JDK 16 and I have been reading a bit of the
>> annotations article from the newest Java Magazine. I thought I'd fiddle
>> with the @Nonnull annotation, so I put one in a method's declaration where
>> I thought it needed to go so I could indicate that a parameter needed a
>> non-null value:
>> >>>
>> >>> protected boolean checkEqual(@Nonnull SU subscription){
>> >>>
>> >>> Netbeans complains that it cannot find the symbol @Nonnull, and it
>> does not give me the option to add an import.
>> >>>
>> >>> Why does this happen?
>>
>

Re: @Nonnull?

[Owen Thomas]

Ok, thanks Geertjan. Let me know what you find.

On Fri, 25 Jun 2021 at 12:59, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

>
> Maybe it doesn’t support it yet. Will try to find out.
>
> Gj
>
> On Fri, 25 Jun 2021 at 04:39, Owen Thomas 
> wrote:
>
>> I'm using NB 12.4 with JDK 16 and I have been reading a bit of the
>> annotations article from the newest Java Magazine. I thought I'd fiddle
>> with the @Nonnull annotation, so I put one in a method's declaration where
>> I thought it needed to go so I could indicate that a parameter needed a
>> non-null value:
>>
>> protected boolean checkEqual(@Nonnull SU subscription){
>>
>> Netbeans complains that it cannot find the symbol @Nonnull, and it does
>> not give me the option to add an import.
>>
>> Why does this happen?
>>
>

@Nonnull?

[Owen Thomas]

I'm using NB 12.4 with JDK 16 and I have been reading a bit of the
annotations article from the newest Java Magazine. I thought I'd fiddle
with the @Nonnull annotation, so I put one in a method's declaration where
I thought it needed to go so I could indicate that a parameter needed a
non-null value:

protected boolean checkEqual(@Nonnull SU subscription){

Netbeans complains that it cannot find the symbol @Nonnull, and it does not
give me the option to add an import.

Why does this happen?

Re: Java 16 Javadocs?

[Owen Thomas]

Thanks Christian. I'll give it a go.

On Wed, 23 Jun 2021 at 17:15, Christian Pervoelz 
wrote:

> If you have added the Java Platform via Tools > Java Platforms it should
> be already there.
>
> If it's not, then:
> 1. Tools > Java Platforms
> 2. On the left side, select the JDK entry
> 3. On the right side, click the tab Javadoc
> 4. Click "Add URL"
> 5. Enter https.//docs.oracle.com/en/java/javase/16/docs/api
>
> If you need it offline, download the docs from here:
> https://www.oracle.com/java/technologies/javase-jdk16-doc-downloads.html
> Store the zip file in a location of your choice and perform the steps as
> above. In step 4. click on "Add Zip/Folder..." and locate your downloaded
> zip.
>
> That's it.
>
> ---C.
>
>
> Am Mi., 23. Juni 2021 um 05:46 Uhr schrieb Owen Thomas <
> owen.paul.tho...@gmail.com>:
>
>> Can someone please point me in the direction of the Javadoc for JDK 16? I
>> want to access it in NetBeans.
>>
>> Thanks,
>>
>>   Owen.
>>
>

Java 16 Javadocs?

[Owen Thomas]

Can someone please point me in the direction of the Javadoc for JDK 16? I
want to access it in NetBeans.

Thanks,

  Owen.

Re: removing the "new project" support for Ant projects

[Owen Thomas]

On Thu, 22 Apr 2021 at 17:15, Geertjan Wielenga
 wrote:

> I don’t think we’re going to resolve this, several people in this
> discussion don’t understand the key point with which this thread started:
> should we consider downplaying the prominence of Ant by removing from
> NetBeans the ability to create new Ant projects (while keeping all other
> Ant functionality).
>

I think you're saying that Ant isn't the best choice of build tool for
modern development methodologies, and I would agree with this sentiment. I
still use Ant for my projects because I created them a long time ago with
Ant, they don't make use of third party stuff, and... admittedly... no one
else works with me, so I've never felt the compulsion to move.

I think Ant is still a good option to do relatively lightweight and
experimental work. I've created more than 100 projects using Ant - most of
which have an active life of about 20 minutes, and many of which don't even
compile. Perhaps I'd put it further down the list of options available from
the create projects menu (I have indeed noticed this has happened in the
12.2 version of NB that I'm using at the moment) but removing it from the
options seems to be an unnecessary snub.

I suppose I've just got to move with the times.

Done... probably.

  Owen.

Re: removing the "new project" support for Ant projects

[Owen Thomas]

If one wants to create an Ant project from within NetBeans, then one should
be able to do that.

I've encountered both Maven and Gradle (Gradle when developing for Android
on IntelliJ... another anecdote about frustration), and I can see their use
when one has to manage one's code base against differing versions of third
party libraries. That's great, but if one is merely doing something small,
especially something that might showcase some feature of SE without
bringing in functionality of third party libraries, Ant leaves the
developer alone to do that. All the stuff that Gradle and Maven introduce
to one's build script becomes useless boilerplate - a distraction
especially when one merely wants to demonstrate or learn a feature of the
SE API and perhaps even to grasp some of the necessity of the build script
itself.

It's not difficult to move a project to Maven or Gradle or any other build
script. Copy one's /src directory from the Ant project to the appropriate
directory of the destination project (maybe set a main class) and off you
go. Novice developers can easily be scared into withdrawal by
considerations that are not salient to their aims, and the distractions
that Maven/Gradle build scripts introduce can only encourage withdrawal
into those developers who are trying to navigate this world alone. I would
consider it a backward step if NB were to adopt the position of other IDEs
and appropriate an air of superiority around the choice of build script.
Because nothing more than an air of superiority is projected by an IDE that
doesn't permit the creation of Ant projects.

I like Ant. Ant is good. Leave Ant alone.

Done.

  Owen.

Re: removing the "new project" support for Ant projects

[Owen Thomas]

Crikey! Looks like I'll have to migrate to Maven then. When in Rome.

On Wed, 21 Apr 2021 at 19:20, John Burgess
 wrote:

> +1 also for me to not eliminating Ant support for new (or existing)
> projects.
>
> -Original Message-
> From: Marco Rossi 
> Sent: 20 April 2021 20:10
> To: Mitch Claborn 
> Cc: users@netbeans.apache.org
> Subject: Re: removing the "new project" support for Ant projects
>
> +1 also for me to not eliminating Ant support for new (or existing)
> projects.
>
> Mark Reds
>
> > Il giorno 20 apr 2021, alle ore 20:08, Mitch Claborn <
> mitch...@claborn.net> ha scritto:
> >
> > +1 for not eliminating Ant support for new (or existing) projects. We've
> been using Ant for a long time, and it still works just fine for us, so
> there is no payback in converting to Maven.
> >
> >
> > Mitch
> >
> > On 4/20/21 12:10 PM, Lisa Ruby wrote:
> >> For those of you who have used Maven for a long time it may seem simple
> and straightforward, but for those of us who haven't it's not. I've
> struggled to try and understand it and figure out how to use it for my
> software project and gave up. And it's a huge amount of overhead, extra
> disk space usage, and more bits and pieces to keep track of that isn't
> justifiable for small simple projects. ANT works just fine for me, and I
> will keep using it for as long as I possibly can. I need to focus my time
> on getting my software out, not on the tools I have to use to do it.
> >> Lisa
> >> On 4/20/2021 10:00 AM, Geertjan Wielenga wrote:
> >>> I agree, the Ant-based project creation should be removed and I
> disagree that there should be any kind of conversion between Ant and Maven
> -- that simply will never work and we'll spend the rest of our days fixing
> bugs in that. To convert from Ant to Maven: create a new Maven project and
> copy the Java source files from your Ant project into it.
> >>>
> >>> Gj
> >>>
> >>> On Tue, Apr 20, 2021 at 6:58 PM  pszud...@throwarock.com>> wrote:
> >>>
> >>>Honestly, I think NB should have an internal conversation about
> >>>removing the "new project" support for Ant projects, while still
> >>>being able to open existing ones. It just confuses a lot of people
> >>>if they're not going to be supported.
> >>>
> >>>I agree, if and ONLY if you provide at least a rudimentary way to
> >>>convert ANT projects to Maven projects.   I have been struggling
> >>>with this issue too long.  I have hundreds of Ant based projects
> >>>that I would love to turn over immediately to Maven... but I can't
> >>>, am struggling, and haven't coded a darn line in two months...  I
> >>>used to code 10 hours a day ... and now... embarrassed by my
> >>>inability to convert.,.
> >>>
> >>>I exaggerate a bit, I still code in "Old" Netbeans 8.2, but I know
> >>>the days are numbered...
> >>>
> >>>
> >>>
> >>>On 2021-04-20 08:23, Will Hartung wrote:
> >>>
> 
> On Mon, Apr 19, 2021 at 12:55 AM Wayne Gemmell | Connect
> mailto:wa...@connect-mobile.co.za>>
> wrote:
> 
> Is the perception that nobody does Maven EAR's anymore or
> that nobody uses EARs? I have a web app that has given me no
> shortage of issuse with ant.
> I'm trying to move it to Maven. If nobody is using maven then
> I need to move to something else. If nobody is using EAR's
> anymore then I'm pretty stuck figuring out this Maven issue.
> 
> Well, it's several things.
> EARs are less popular because their necessity has been greatly
> reduced. Session beans can be placed in WARs now, so for many use
> cases, a WAR is completely adequate to the task.
> However, it's not suitable for all use cases.
> Notably, MDBs can not be deployed in WARs. But only as an EJB
> either deployed standalone, or bundled within an EAR.
> With the hue and cry over micro services and "down with the
> monolith", just the idea of a large application bundled in a EAR
> is falling out of favor.
> Also, there's a history of advocacy underlying this. Sun used
> NetBeans as a mechanism to advocate for Java and Java EE. It
> behooved them to have something like NetBeans to make Java EE
> development easier. So, it was important for NetBeans to have
> really first class Java EE support. Bundling the Java EE wizards
> and templates along with Glassfish all helped promote that.
> Of course, now, with the great Java Diaspora out of Oracle, the
> goals and drivers are different.
> For your project, if all you have is a web app and some session
> beans, then a simple WAR file is good to go. The Ant projects
> seem to essentially be deprecated now, so I would not rely on
> those for anything. If practical, especially if your project is
> young, I would migrate it to Maven. The Maven 

Re: removing the "new project" support for Ant projects

[Owen Thomas]

I think Ant is lovely. Most of my projects only extend the Java SE API. I
don't see the need to change to a build tool that manages third party
libraries unless and until I need to use third party libraries.

Keep supporting Ant and keep the build process as trivial as it needs to be.

On Wed, 21 Apr 2021 at 15:56, Will Hartung  wrote:

>
>
> On Tue, Apr 20, 2021 at 9:32 PM Sean Carrick  wrote:
>
>> Explain to me, Scott, why I **need** to learn Maven and dump Ant. Ant
>> has served me very well all of these years and has never given me one
>> single bit of trouble. Speed? Ant is fast enough for me and my projects.
>> Keeping libraries "up-to-date"? That is just another way of saying "stay on
>> the bleeding edge." Why should I learn Maven and dump Ant? Explain it with
>> facts and reasoning, and without resorting to expressions such as "sticking
>> your head in the sand."
>>
>
> I have a project using JavaFX, JPA, CDI, and Derby. My pom.xml file lists
> 13 direct dependencies. The actual number of jars that get imported is
> closer to 50.
>
> There's a really cool project out there used to write REST based micro web
> services called dropwizard. To use it, you add a single dependency to you
> pom.xml.
>
> When your project builds, it downloads and imports about 90 other jar
> files.
>
> Nowhere on their site will you see this list of jar files that it requires
> to run.
>
> Using the IDE, with two mouse clicks, I can have not just the jars
> downloaded, but all of the available javadoc and source files. Once it's
> all caught up, I have access to all of that within the IDE.
>
> The key point is, that in the modern Java community, projects are shared
> using Maven artifacts. Many sites start their "quick start" instructions
> with "plop this dependency into your project file". From there, magic
> happens. Gradle relies on Maven repositories. Ivy for Ant relies on them
> also. I think there are other Java build tools that do also.
>
> Finally, NB, Eclipse, IDEA, and even Emacs all have first class support
> for Maven projects and pom files. With those pom files, all of the
> autocomplete works MUCH better, and painlessly. This works very well in
> offices with mixed development environments. Eclipse can not open a NB Ant
> project. NB can't open an IDEA project. All of them work with Maven
> projects.
>
> Maintaining the NB libraries is not a really big deal for small numbers of
> jar files. Even with a large number that's incrementally built up over
> time. But adding new projects with new dependencies that all have to be
> tracked down, I find, is a pain in the neck. I'm glad I didn't have to hunt
> down 90 dependencies to try a "hello world" dropwizard service. Now imagine
> updating the library lists across different IDE projects with different
> tools. As if teams don't have enough problems with communication and
> project drag.
>
> Maven absolutely has issues. It has innate complexity. It's slower than
> Ant for the basic Happy Path of building a project. It's reliance on
> internet connectivity sometimes has to be worked around. And any large team
> is better to jump through some hoops to set up a local repository as a
> cache and for local projects, which can be an infrastructure burden. But,
> that's it's big selling point. Maven scales much better than Ant does. And
> if you add Ivy to Ant, well, you have to deal with all of the Maven
> dependency burdens anyway.
>
> Let me give you one of my many experiences with Maven. I downloaded some
>> sample code today to see how someone was using a particular library. It
>> turned out that sample code was in a NB Maven project. I opened that
>> project at around 20:00, I just closed NB about 20 minutes ago. The whole
>> time, Maven was doing something, supposedly in the background, but it had
>> my CPUs up at 68% use and my memory at 82%. I have a Quadcore providing 8
>> threads and 8 GiB of RAM. There is absolutely no reason that Maven should
>> have been pegging my system out like that for the simple little project
>> that I had opened. Ant certainly never does that to my system.
>>
> This is quite likely the very large repository index that NB uses being
> downloaded from Maven Central. This is absolutely a potential pain point. I
> don't have a good solution to work around it. My machine stays on (sleeps)
> 24x7, and I leave NB open all the time. NB will update that index once a
> week if you let it, and it's not an incremental update, it's a complete
> reload. You can disable it after the first time, and trigger the update
> manually. As I said before, I've relaunched at lunch time or before I leave
> work in the afternoon to let this happen on its own time, and not blocking
> me. It also bloats your NB directories. If you have your NB 12.0, 12.1,
> 12.2, 12.3 versions, they all have their own copy of the index. That's
> several GB of data, likely useless in the old version directories. NB
> eventually detects and helps you clean those up, but 

Re: Why isn't this "error" going away?

[Owen Thomas]

Don't worry. Found it.

The error happened because I moved GlialFirstInitiator to a new library.
Even though the Java compiler could see it because the current library was
indirectly dependent on it, NB couldn't see this relationship. I added the
library in the project and the error in the IDE went away.

On Wed, 14 Apr 2021 at 22:40, Owen Thomas 
wrote:

> Hello NetBeans users.
>
> I've tried stopping NB, deleting the cache, and restarting NB. I've done
> this twice. Although the program compiles, the error disclosed in the file
> attached, apparent only to NB, doesn't go away.
>
> Is there something else that is confusing NB?
>
> Thanks,
>
>   Owen.
>

Why isn't this "error" going away?

[Owen Thomas]

Hello NetBeans users.

I've tried stopping NB, deleting the cache, and restarting NB. I've done
this twice. Although the program compiles, the error disclosed in the file
attached, apparent only to NB, doesn't go away.

Is there something else that is confusing NB?

Thanks,

  Owen.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: Control-shift-P.

[Owen Thomas]

On Thu, 25 Mar 2021 at 20:59, Jens Zurawski  wrote:

> To find out, what a specific Hot Key is doping, just focus the "Search
> in Shortcuts" field and press the Hotkey (in your example Ctrl-Shift-P)
> then you can see that its action is "Go to Super Implementation". You
> then can define another Hot Key for it if you want.
>

Being that I've been using NetBeans for some time, I felt silly for having
to ask, so thank you very much for the tip Jens (and Neil). I'll try to
keep this advice in mind.

Control-shift-P.

[Owen Thomas]

I accidentally pressed control-shift-p while in the implementation of a
method from an anonymous inner class, and discovered, somewhat to my
surprise, that I was taken to the methods declaration.

Is this the intended purpose of this keystroke, or is there more to it?
Where can I find out?

Thanks,

  Owen.

Re: [base ide] No help available in Apache Netbeans 12.0?

[Owen Thomas]

Hey Geertjan.

Is that ever going to change? When might JavaHelp be available to versions
of netbeans released after transfer to Apache? Is there a page you can
point to that explains all this?

On Sat, 13 Feb 2021 at 15:08, Geertjan Wielenga
 wrote:

>
> Indeed, the help has been removed, JavaHelp is GPL licensed and cannot be
> included in an Apache project.
>
> Gj
>
> On Sat, 13 Feb 2021 at 03:08,  wrote:
>
>> This query relates to the Base IDE.
>>
>> Some time ago I used Netbeans 8.2 for working with html, php and
>> javascript. It had a
>> comprehensive help system, i.e. there were help buttons on the various
>> IDE Tools -> Options
>> windows, and IDE help under the main screen help option.
>>
>> I havejust installed Apache Netbeans 12.0 and there isn't any help
>> anywhere! There are still
>> help buttons on the various IDE Tools -> Options windows but none of them
>> do anything. The
>> IDE help under the main screen help option has also gone. It just offers
>> "on-line docs and
>> support".
>>
>> Initially, I still had Netbeans 8.2 installed when I first installed
>> Apache Netbeans 12.0. Both
>> worked ok, with help available on 8.2, but no help available on 12.0. I
>> uninstalled Netbeans
>> 8.2, then uninstalled 12.0, and then reinstalled 12.0 again. Installation
>> said it was successful,
>> but still no help available.
>>
>> Here's the configuration information from Help -> About:
>>
>> Product Version: Apache NetBeans IDE 12.0
>> Java: 1.8.0_281; Java HotSpot(TM) 64-Bit Server VM 25.281-b09
>> Runtime: Java(TM) SE Runtime Environment 1.8.0_281-b09
>> System: Windows 10 version 10.0 running on amd64; Cp1252; en_GB (nb)
>>
>> Installed:
>> Base IDE
>> HTML5/Javascript
>> PHP
>>
>> Not installed:
>> Java SE
>> Java EE
>>
>> I do hope someone can tell me what the issue is. I have spent the last
>> couple of evenings
>> tearing my hair out hunting for a solution without success.
>>
>> Thanks.
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>

Re: Something screwy has started happening in NB 12.2?

[Owen Thomas]

Perhaps my code is so thoroughly strange that the poor editor's having a
time understanding it.

On Thu, 28 Jan 2021 at 19:07, Owen Thomas 
wrote:

>
>
> On Thu, 28 Jan 2021 at 19:06, Owen Thomas 
> wrote:
>
>> I was happily using my favourite IDE to edit my source code, and then it
>> froze for a while which upset me. After a while elapsed, it prompted me to
>> download something and I thought to myself, "okay - it must have sensed a
>> new version of  and has rudely but hopefully not to be repeated,
>> trying to update itself". So I said, "what the hell", and proceeded to
>> download and install it.
>>
>> Now after what must have been a few minutes of resumption, the editor's
>> playing up and has become unresponsive.
>>
>> Any clues?
>>
>
> Wait up! It appears as though normality has resumed...
>

Re: Something screwy has started happening in NB 12.2?

[Owen Thomas]

On Thu, 28 Jan 2021 at 19:06, Owen Thomas 
wrote:

> I was happily using my favourite IDE to edit my source code, and then it
> froze for a while which upset me. After a while elapsed, it prompted me to
> download something and I thought to myself, "okay - it must have sensed a
> new version of  and has rudely but hopefully not to be repeated,
> trying to update itself". So I said, "what the hell", and proceeded to
> download and install it.
>
> Now after what must have been a few minutes of resumption, the editor's
> playing up and has become unresponsive.
>
> Any clues?
>

Wait up! It appears as though normality has resumed...

Something screwy has started happening in NB 12.2?

[Owen Thomas]

I was happily using my favourite IDE to edit my source code, and then it
froze for a while which upset me. After a while elapsed, it prompted me to
download something and I thought to myself, "okay - it must have sensed a
new version of  and has rudely but hopefully not to be repeated,
trying to update itself". So I said, "what the hell", and proceeded to
download and install it.

Now after what must have been a few minutes of resumption, the editor's
playing up and has become unresponsive.

Any clues?

Re: Adding dependent project to another project in NetBeans.

[Owen Thomas]

Got it! Thanks Alf.

On Wed, 6 Jan 2021 at 19:09, Alfonso Lourido  wrote:

> Hi Owen,
>
> If I understand you well, nothing has changed from previous versions ….
>
> To add a library to a project, assuming it’s already in the system, select
> the folder “Libraries” on the left (Your_Project/Libraries) and right click
> on it: you’ll see you can add Library, JAR/Folder …
>
> If the required library is not in the system you can go to the
> Menu/Tools/Libraries … and follow the instructions ...
>
> I hope it helps …
>
> Cheers,
>
> __
> Alfonso Lourido
> Alf
> ☎️ +34 607 900 607
>
>
>
> El 6 ene 2021, a las 6:37, Owen Thomas 
> escribió:
>
> Hello NetBeans Users.
>
> I haven't added a dependency in a while, and I am wondering how to do it
> in 12.2. I thought it was done by right-clicking the desired project in the
> projects view, and selecting the Properties option from the menu. From the
> Project Properties dialogue, one then would go to the libraries view and
> add the project one wanted to add to this project.
>
> Has something changed since earlier releases, or have I just forgotten how
> to add a dependent project?
>
> Thanks,
>
>   Owen.
>
>
>

Adding dependent project to another project in NetBeans.

[Owen Thomas]

Hello NetBeans Users.

I haven't added a dependency in a while, and I am wondering how to do it in
12.2. I thought it was done by right-clicking the desired project in the
projects view, and selecting the Properties option from the menu. From the
Project Properties dialogue, one then would go to the libraries view and
add the project one wanted to add to this project.

Has something changed since earlier releases, or have I just forgotten how
to add a dependent project?

Thanks,

  Owen.

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

No. Now that you mention it, the value doesn't seem reasonable to me
either. So, I changed it to /usr/lib/jvm/java-14-openjdk-amd64 and the
problems go away. Thanks Geertjan - hopefully that's the end of that.

I'm sure I just downloaded and installed NetBeans without thinking too
hard, so I don't know how that could have been set.

On Sat, 26 Dec 2020 at 19:55, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> netbeans_jdkhome="/usr"
>
> That's what I see in your file above and that can't be right, can it?
>
> Gj
>
>
> On Sat, Dec 26, 2020 at 8:19 AM Owen Thomas 
> wrote:
>
>> Sure Geertjan, here is netbeans.conf from ~/netbeans-12.2/netbeans/etc
>> which is the default directory in which NetBeans was installed.
>>
>> On Sat, 26 Dec 2020 at 16:37, Geertjan Wielenga <
>> geertjan.wiele...@googlemail.com> wrote:
>>
>>> Can you send your netbeans.conf file here so we can see what is in there?
>>>
>>> Gj
>>>
>>> On Sat, 26 Dec 2020 at 06:10, Owen Thomas 
>>> wrote:
>>>
>>>> On Mon, 30 Nov 2020 at 19:32, Peter Hull  wrote:
>>>>
>>>>> I would check:
>>>>> 1. Does your Java platform setup look reasonable? (in Tools | Java
>>>>> Platforms )
>>>>> 2. Does this error occur for a new project or just existing ones?
>>>>> (e.g. set up a new "Java with Ant" application)
>>>>> I think I've seen something like this before and it was down to the
>>>>> Java platform configuration.
>>>>>
>>>>
>>>> Hello again. Having acquired my new laptop, I am setting it up and have
>>>> encountered the same problem that I was having when I earlier installed
>>>> NetBeans 12.2 on another computer. The other was, and the new one is
>>>> running Ubuntu 20.04.
>>>>
>>>> I tried to create a new project, and I found that the error was also
>>>> occurring; namely that java.lang could not be found on almost every line of
>>>> source code.
>>>>
>>>> When I look at the Java Platforms dialogue as advised by Peter, it
>>>> presents two entries: "Java 14" and "Java 14 (Default)". The first entry
>>>> looks fine, but the second one appears to be amiss because as the attached
>>>> screenshot shows that it is missing apparent details. The remove option
>>>> also appears to be disabled, so I'm currently at a loss. How do I get rid
>>>> of this second entry?
>>>>
>>>>   Owen.
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>>>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>>>
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

Sure Geertjan, here is netbeans.conf from ~/netbeans-12.2/netbeans/etc
which is the default directory in which NetBeans was installed.

On Sat, 26 Dec 2020 at 16:37, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> Can you send your netbeans.conf file here so we can see what is in there?
>
> Gj
>
> On Sat, 26 Dec 2020 at 06:10, Owen Thomas 
> wrote:
>
>> On Mon, 30 Nov 2020 at 19:32, Peter Hull  wrote:
>>
>>> I would check:
>>> 1. Does your Java platform setup look reasonable? (in Tools | Java
>>> Platforms )
>>> 2. Does this error occur for a new project or just existing ones? (e.g.
>>> set up a new "Java with Ant" application)
>>> I think I've seen something like this before and it was down to the Java
>>> platform configuration.
>>>
>>
>> Hello again. Having acquired my new laptop, I am setting it up and have
>> encountered the same problem that I was having when I earlier installed
>> NetBeans 12.2 on another computer. The other was, and the new one is
>> running Ubuntu 20.04.
>>
>> I tried to create a new project, and I found that the error was also
>> occurring; namely that java.lang could not be found on almost every line of
>> source code.
>>
>> When I look at the Java Platforms dialogue as advised by Peter, it
>> presents two entries: "Java 14" and "Java 14 (Default)". The first entry
>> looks fine, but the second one appears to be amiss because as the attached
>> screenshot shows that it is missing apparent details. The remove option
>> also appears to be disabled, so I'm currently at a loss. How do I get rid
>> of this second entry?
>>
>>   Owen.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
>> For additional commands, e-mail: users-h...@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>


netbeans.conf
Description: Binary data

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

On Mon, 30 Nov 2020 at 19:32, Peter Hull  wrote:

> I would check:
> 1. Does your Java platform setup look reasonable? (in Tools | Java
> Platforms )
> 2. Does this error occur for a new project or just existing ones? (e.g.
> set up a new "Java with Ant" application)
> I think I've seen something like this before and it was down to the Java
> platform configuration.
>

Hello again. Having acquired my new laptop, I am setting it up and have
encountered the same problem that I was having when I earlier installed
NetBeans 12.2 on another computer. The other was, and the new one is
running Ubuntu 20.04.

I tried to create a new project, and I found that the error was also
occurring; namely that java.lang could not be found on almost every line of
source code.

When I look at the Java Platforms dialogue as advised by Peter, it presents
two entries: "Java 14" and "Java 14 (Default)". The first entry looks fine,
but the second one appears to be amiss because as the attached screenshot
shows that it is missing apparent details. The remove option also appears
to be disabled, so I'm currently at a loss. How do I get rid of this second
entry?

  Owen.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

Which log files are applicable?

On Sun, 29 Nov 2020 at 20:51, Owen Thomas 
wrote:

> Yes, my apologies Geertjan. It's Ubuntu 20.04.1.
>
> On Sun, 29 Nov 2020 at 19:53, Geertjan Wielenga <
> geertjan.wiele...@googlemail.com> wrote:
>
>> What is the operating system on the new laptop you have acquired?
>>
>> Can you include that information every time you write to this mailing
>> list?
>>
>> Gj
>>
>> On Sun, 29 Nov 2020 at 08:18, Owen Thomas 
>> wrote:
>>
>>> When removing NetBeans 12 prior to reinstallation. I find a folder in my
>>> home folder called .nbi. This looks like something NetBeans created, so I
>>> removed it too.
>>>
>>> After reinstallation, and noting that the .nbi folder had appeared as
>>> expected, I started NetBeans and found no change. NetBeans is still telling
>>> me it cannot find java.lang.
>>>
>>> I have installed netbeans three times, first two times over version 14
>>> of the Open JDK and the third time over version 12 of the Open JDK. I have
>>> no idea what is wrong.
>>>
>>> On Sun, 29 Nov 2020 at 17:50, Owen Thomas 
>>> wrote:
>>>
>>>> I actually installed Open JDK 11 because version 12 doesn't exist. I
>>>> didn't do anything to my NetBeans install... perhaps I'll reinstall it
>>>> again...
>>>>
>>>> I've observed no change, and I have no idea. Help appreciated.
>>>>
>>>> On Sun, 29 Nov 2020 at 16:48, Owen Thomas 
>>>> wrote:
>>>>
>>>>> I did find something on Stack Overflow
>>>>> <https://stackoverflow.com/questions/56952163/ubuntu-18-04-netbeans-10-0-fatal-error-unable-to-find-package-java-lang-in-clas>
>>>>> about using a JDK that is later than the installed version of NetBeans. I
>>>>> have installed OpenJDK 14. I think this advice is dubious, but I am going
>>>>> to follow it now by uninstalling 14 and installing 12. I'll post something
>>>>> saying how I get on.
>>>>>
>>>>> On Sun, 29 Nov 2020 at 16:32, Owen Thomas 
>>>>> wrote:
>>>>>
>>>>>> Hello.
>>>>>>
>>>>>> I've just installed 12.1 on a new computer I have acquired. When I
>>>>>> restart NetBeans after deleting my cache, I get the attached error 
>>>>>> telling
>>>>>> me the IDE cannot find java.lang. I have no idea why this error is
>>>>>> appearing, and would appreciate some advice.
>>>>>>
>>>>>> Thanks in advance for your help.
>>>>>>
>>>>>>   Owen.
>>>>>>
>>>>>

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

Yes, my apologies Geertjan. It's Ubuntu 20.04.1.

On Sun, 29 Nov 2020 at 19:53, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> What is the operating system on the new laptop you have acquired?
>
> Can you include that information every time you write to this mailing list?
>
> Gj
>
> On Sun, 29 Nov 2020 at 08:18, Owen Thomas 
> wrote:
>
>> When removing NetBeans 12 prior to reinstallation. I find a folder in my
>> home folder called .nbi. This looks like something NetBeans created, so I
>> removed it too.
>>
>> After reinstallation, and noting that the .nbi folder had appeared as
>> expected, I started NetBeans and found no change. NetBeans is still telling
>> me it cannot find java.lang.
>>
>> I have installed netbeans three times, first two times over version 14 of
>> the Open JDK and the third time over version 12 of the Open JDK. I have no
>> idea what is wrong.
>>
>> On Sun, 29 Nov 2020 at 17:50, Owen Thomas 
>> wrote:
>>
>>> I actually installed Open JDK 11 because version 12 doesn't exist. I
>>> didn't do anything to my NetBeans install... perhaps I'll reinstall it
>>> again...
>>>
>>> I've observed no change, and I have no idea. Help appreciated.
>>>
>>> On Sun, 29 Nov 2020 at 16:48, Owen Thomas 
>>> wrote:
>>>
>>>> I did find something on Stack Overflow
>>>> <https://stackoverflow.com/questions/56952163/ubuntu-18-04-netbeans-10-0-fatal-error-unable-to-find-package-java-lang-in-clas>
>>>> about using a JDK that is later than the installed version of NetBeans. I
>>>> have installed OpenJDK 14. I think this advice is dubious, but I am going
>>>> to follow it now by uninstalling 14 and installing 12. I'll post something
>>>> saying how I get on.
>>>>
>>>> On Sun, 29 Nov 2020 at 16:32, Owen Thomas 
>>>> wrote:
>>>>
>>>>> Hello.
>>>>>
>>>>> I've just installed 12.1 on a new computer I have acquired. When I
>>>>> restart NetBeans after deleting my cache, I get the attached error telling
>>>>> me the IDE cannot find java.lang. I have no idea why this error is
>>>>> appearing, and would appreciate some advice.
>>>>>
>>>>> Thanks in advance for your help.
>>>>>
>>>>>   Owen.
>>>>>
>>>>

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

When removing NetBeans 12 prior to reinstallation. I find a folder in my
home folder called .nbi. This looks like something NetBeans created, so I
removed it too.

After reinstallation, and noting that the .nbi folder had appeared as
expected, I started NetBeans and found no change. NetBeans is still telling
me it cannot find java.lang.

I have installed netbeans three times, first two times over version 14 of
the Open JDK and the third time over version 12 of the Open JDK. I have no
idea what is wrong.

On Sun, 29 Nov 2020 at 17:50, Owen Thomas 
wrote:

> I actually installed Open JDK 11 because version 12 doesn't exist. I
> didn't do anything to my NetBeans install... perhaps I'll reinstall it
> again...
>
> I've observed no change, and I have no idea. Help appreciated.
>
> On Sun, 29 Nov 2020 at 16:48, Owen Thomas 
> wrote:
>
>> I did find something on Stack Overflow
>> <https://stackoverflow.com/questions/56952163/ubuntu-18-04-netbeans-10-0-fatal-error-unable-to-find-package-java-lang-in-clas>
>> about using a JDK that is later than the installed version of NetBeans. I
>> have installed OpenJDK 14. I think this advice is dubious, but I am going
>> to follow it now by uninstalling 14 and installing 12. I'll post something
>> saying how I get on.
>>
>> On Sun, 29 Nov 2020 at 16:32, Owen Thomas 
>> wrote:
>>
>>> Hello.
>>>
>>> I've just installed 12.1 on a new computer I have acquired. When I
>>> restart NetBeans after deleting my cache, I get the attached error telling
>>> me the IDE cannot find java.lang. I have no idea why this error is
>>> appearing, and would appreciate some advice.
>>>
>>> Thanks in advance for your help.
>>>
>>>   Owen.
>>>
>>

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

I actually installed Open JDK 11 because version 12 doesn't exist. I didn't
do anything to my NetBeans install... perhaps I'll reinstall it again...

I've observed no change, and I have no idea. Help appreciated.

On Sun, 29 Nov 2020 at 16:48, Owen Thomas 
wrote:

> I did find something on Stack Overflow
> <https://stackoverflow.com/questions/56952163/ubuntu-18-04-netbeans-10-0-fatal-error-unable-to-find-package-java-lang-in-clas>
> about using a JDK that is later than the installed version of NetBeans. I
> have installed OpenJDK 14. I think this advice is dubious, but I am going
> to follow it now by uninstalling 14 and installing 12. I'll post something
> saying how I get on.
>
> On Sun, 29 Nov 2020 at 16:32, Owen Thomas 
> wrote:
>
>> Hello.
>>
>> I've just installed 12.1 on a new computer I have acquired. When I
>> restart NetBeans after deleting my cache, I get the attached error telling
>> me the IDE cannot find java.lang. I have no idea why this error is
>> appearing, and would appreciate some advice.
>>
>> Thanks in advance for your help.
>>
>>   Owen.
>>
>

Re: Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

I did find something on Stack Overflow
<https://stackoverflow.com/questions/56952163/ubuntu-18-04-netbeans-10-0-fatal-error-unable-to-find-package-java-lang-in-clas>
about using a JDK that is later than the installed version of NetBeans. I
have installed OpenJDK 14. I think this advice is dubious, but I am going
to follow it now by uninstalling 14 and installing 12. I'll post something
saying how I get on.

On Sun, 29 Nov 2020 at 16:32, Owen Thomas 
wrote:

> Hello.
>
> I've just installed 12.1 on a new computer I have acquired. When I restart
> NetBeans after deleting my cache, I get the attached error telling me the
> IDE cannot find java.lang. I have no idea why this error is appearing, and
> would appreciate some advice.
>
> Thanks in advance for your help.
>
>   Owen.
>

Netbeans 12.1: Cannot access java.lang?

[Owen Thomas]

Hello.

I've just installed 12.1 on a new computer I have acquired. When I restart
NetBeans after deleting my cache, I get the attached error telling me the
IDE cannot find java.lang. I have no idea why this error is appearing, and
would appreciate some advice.

Thanks in advance for your help.

  Owen.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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

LeakingThisInConstructor warning not working correctly?

[Owen Thomas]

 In NB 12.1, I have the following code in a constructor of a class named
Challenge:

@SuppressWarnings("LeakingThisInConstructor")
public Challenge(R
resonance,Connectionconnection,I identity,R_MES
messageResonance)throws Problem{

//...

this.messageResonance.getReferee().addRefereeSubscription(this);
this.messageResonance.getIndex().addIndexSubscription(this);

messageResonance.addChallenge((SU)this);
}

When I remove the @SuppressWarnings annotation, I see two yellow light
bulbs next to the lines ending (this);, but none next to the line ending
(SU(this)); where SU is a parameterised type. Does this perhaps belie a
problem with the editor warnings?

Output from Find Usages...

[Owen Thomas]

The output from the Find Usages function in NB 12 of a constructor that
includes the quotation of generic parameters seems to leave out the left
angle brace as well as other detail. When I run this in NB 11 from a
command prompt, I notice the following appear in my terminal window. The
actual declaration also appears as a screenshot.

I thought someone may find this to be an interesting clue as to what goes
wrong with the Find Usages feature I have earlier commented about. My
cursory diagnosis is that something in NB is trying to parse my generics as
XML/HTML.

Terminal window output appears below:

WARNING [org.openide.awt.HtmlRenderer]: Malformed or unsupported HTML
WARNING [org.openide.awt.HtmlRenderer]:   60:  this.ownerConnection=new
Locker,S,C_I,C_G,C_N,I>(s.getQualeContainer()){
WARNING [org.openide.awt.HtmlRenderer]:


 ^
WARNING [org.openide.awt.HtmlRenderer]:  Full HTML string:60:  this.ownerConnection=new
Locker,S,C_I,C_G,C_N,I>(s.getQualeContainer()){
WARNING [org.openide.awt.HtmlRenderer]: Could not find color identifier in
font declaration
WARNING [org.openide.awt.HtmlRenderer]: 172:  return new
Locker,FeatureMessage,FeatureMessageResonance,
WARNING [org.openide.awt.HtmlRenderer]:  S,C_I,C_G,C_N,I>(this){
WARNING [org.openide.awt.HtmlRenderer]:

^
WARNING [org.openide.awt.HtmlRenderer]:  Full HTML string:  172:  return new
Locker,FeatureMessage,FeatureMessageResonance,
WARNING [org.openide.awt.HtmlRenderer]:  S,C_I,C_G,C_N,I>(this){
WARNING [org.openide.awt.HtmlRenderer]: Illegal hexadecimal color text:
Featur in HTML string
WARNING [org.openide.awt.HtmlRenderer]: 172:  return new
Locker,FeatureMessage,FeatureMessageResonance,
WARNING [org.openide.awt.HtmlRenderer]:  S,C_I,C_G,C_N,I>(this){
WARNING [org.openide.awt.HtmlRenderer]:

^
WARNING [org.openide.awt.HtmlRenderer]:  Full HTML string:  172:  return new
Locker,FeatureMessage,FeatureMessageResonance,
WARNING [org.openide.awt.HtmlRenderer]:  S,C_I,C_G,C_N,I>(this){
WARNING [org.openide.awt.HtmlRenderer]: Unresolvable html color: Featur in
HTML string
WARNING [org.openide.awt.HtmlRenderer]:
WARNING [org.openide.awt.HtmlRenderer]: 172:  return new
Locker,FeatureMessage,FeatureMessageResonance,
WARNING [org.openide.awt.HtmlRenderer]:  S,C_I,C_G,C_N,I>(this){
WARNING [org.openide.awt.HtmlRenderer]:

^
WARNING [org.openide.awt.HtmlRenderer]:  Full HTML string:  172:  return new
Locker,FeatureMessage,FeatureMessageResonance,
WARNING [org.openide.awt.HtmlRenderer]:  S,C_I,C_G,C_N,I>(this){

  Owen.

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

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