Re: Graduating Friend APIs to Public APIs (Web Commons)

2021-10-31 Thread Laszlo Kishalmi 
Just file a PR, that makes the API public. Generally we have no issue to 
do so. The reviewers might take a brief look on the exported API-s, but 
that's all.


On 10/31/21 08:47, Eric Bresie wrote:

While working on a new python module (since I've seen little progress on
python donation completion and trying to make an LSP based version) , I
borrowed code from another language support (javascript/node js) to model
som of the functionality after which had dependencies like

import org.netbeans.modules.web.common.api.Version;
import org.netbeans.modules.web.common.ui.api.ExternalExecutable;


When attempting to build in the final steps (building the nbm) I
encountered a build issue like the following (for full trace see end of
email):

Failed to execute goal
org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend. -> [Help
1]


My assumption is my module is not a "friend" to the web.common and/pr
web.common.ui related packages which is preventing that from finishing up.

While discussing on stack, it was suggested maybe making the Web.Commons
packages "public" instead of requiring to update with all the "friends" may
be a better option.

I found
https://cwiki.apache.org/confluence/display/NETBEANS/Public+vs+Friend+API
which seems to imply after a time it may be worth making things public
(i.e. if there are more than 5 friends, the API is stable and not changing
a lot, etc.)

So with that in mind and the fact that there appears to be a lot of friends
on these packages, is it worth changing the web.common/web.common.ui to be
a public API?

If so, what is the process by which this is normally done (i.e. change from
friend to public, any API documentation updates, any build changes,
regression testing, etc.)?

Eric Bresie
ebre...@gmail.com

Full stack trace:

Failed to execute goal
org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend. -> [Help
1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend.
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
 at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
 at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
 at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
 at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
 at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
 at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
 at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke (Method.java:566)
 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
 at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
 at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoFailureException: Module has friend
dependency on org.netbeans.modules.web.common.ui but is not listed as a
friend.
 at
org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.visibleModuleClasses
(NetBeansManifestUpdateMojo.java:900)
 at
org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.checkModuleClassPath
(NetBeansManifestUpdateMojo.java:717)
 at org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.execute
(NetBeansManifestUpdateMojo.java:561)
 at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
 at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
 at org.apache.maven.lifecycle.internal.MojoExecutor.ex

AW: Graduating Friend APIs to Public APIs (Web Commons)

2021-10-31 Thread Christian Lenz 
I’m again for making the stuff public. Web is working well for years now w/o 
big issues. So why not? The friends API is not that holy grail. If we are 
standing behind the code, we should change it. Just scaring About Nothing, 
because I will be responsive for my Plugin if it is not working.

If you add your plugin as a friend today, it is possible that it will not work 
tomorrow, if we remove the friend or if you change the name of your plugin 
(identification). Geertjan started a plugin yaers ago for adding Kendo UI to 
NetBeans, but it is not possible to build it anymore: 
https://github.com/GeertjanWielenga/KendoNetBeans/issues/3. Changing a public 
API back to private will not make sense and if we change them or make them 
deprecated, then there will be an alternative.

 There was a discussion to let them as they are and make a public layer which 
proxies the stuff to the outside, just as an information.

For your problem with the ExternalExecutable there is a public equivalent for 
that to use: org.netbeans.api.extexecution.base.ProcessBuilder; 

Also this is just my experience from the last years of creating NetBeans 
plugins. Atm a lots are on hold due to lack of time to dig deep into the API to 
make them public.


Cheers

Chris

Von: Eric Bresie
Gesendet: Sonntag, 31. Oktober 2021 16:48
An: Netbeans Developer List
Betreff: Graduating Friend APIs to Public APIs (Web Commons)

While working on a new python module (since I've seen little progress on
python donation completion and trying to make an LSP based version) , I
borrowed code from another language support (javascript/node js) to model
som of the functionality after which had dependencies like

import org.netbeans.modules.web.common.api.Version;
import org.netbeans.modules.web.common.ui.api.ExternalExecutable;


When attempting to build in the final steps (building the nbm) I
encountered a build issue like the following (for full trace see end of
email):

Failed to execute goal
org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend. -> [Help
1]


My assumption is my module is not a "friend" to the web.common and/pr
web.common.ui related packages which is preventing that from finishing up.

While discussing on stack, it was suggested maybe making the Web.Commons
packages "public" instead of requiring to update with all the "friends" may
be a better option.

I found
https://cwiki.apache.org/confluence/display/NETBEANS/Public+vs+Friend+API
which seems to imply after a time it may be worth making things public
(i.e. if there are more than 5 friends, the API is stable and not changing
a lot, etc.)

So with that in mind and the fact that there appears to be a lot of friends
on these packages, is it worth changing the web.common/web.common.ui to be
a public API?

If so, what is the process by which this is normally done (i.e. change from
friend to public, any API documentation updates, any build changes,
regression testing, etc.)?

Eric Bresie
ebre...@gmail.com

Full stack trace:

Failed to execute goal
org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend. -> [Help
1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(Delegating

AW: can't lookup current project

2021-10-31 Thread Christian Lenz 
Thx for the hint, will check this out 😊.

Von: Jaroslav Tulach
Gesendet: Sonntag, 31. Oktober 2021 20:42
An: dev
Betreff: Re: can't lookup current project

Not a code to copy without thinking. Has the function on line 57 ever
returned non-null?
-jt

Dne st 27. 10. 2021 11:07 uživatel Christian Lenz 
napsal:

> Here can you see, how I did this:
> https://github.com/Chris2011/gitlogbeans/blob/main/src/main/java/io/github/chris2011/netbeans/plugins/gitlogbeans/PathUtils.java
> the code is a copy of Markiewbs git branch in status bar plugin.
>
>
> Cheers
>
> CHris
>
> Von: Jaroslav Tulach
> Gesendet: Mittwoch, 27. Oktober 2021 07:22
> An: dev@netbeans.apache.org
> Betreff: Re: can't lookup current project
>
> What do you mean by current project?
>
> There is
>
> https://bits.netbeans.org/12.5/javadoc/org-netbeans-modules-projectuiapi-base/
> org/netbeans/api/project/ui/OpenProjects.html#getOpenProjects--
> 
>
> or there is
>
> https://bits.netbeans.org/12.5/javadoc/org-netbeans-modules-projectapi/org/
> netbeans/api/project/ProjectManager.html#findProject-
> 
> org.openide.filesystems.FileObject-
>
> -jt
>
> > Hi All
> >
> >These give me null:
> >
> > Lookup lookup = Utilities.actionsGlobalContext();
> > Project project = lookup.lookup(Project.class);
> >
> > This also null:
> >
> > OpenProjects.getDefault().getMainProject()
> >
> > How can I find the current selected project? thanks
> >
> >
> > Thanks
> >
> > From Peter (System Architect, Quantr Limited https://www.quantr.hk ,
> Mobile
> > : 96554595)
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>

Re: can't lookup current project

2021-10-31 Thread Jaroslav Tulach 
Not a code to copy without thinking. Has the function on line 57 ever
returned non-null?
-jt

Dne st 27. 10. 2021 11:07 uživatel Christian Lenz 
napsal:

> Here can you see, how I did this:
> https://github.com/Chris2011/gitlogbeans/blob/main/src/main/java/io/github/chris2011/netbeans/plugins/gitlogbeans/PathUtils.java
> the code is a copy of Markiewbs git branch in status bar plugin.
>
>
> Cheers
>
> CHris
>
> Von: Jaroslav Tulach
> Gesendet: Mittwoch, 27. Oktober 2021 07:22
> An: dev@netbeans.apache.org
> Betreff: Re: can't lookup current project
>
> What do you mean by current project?
>
> There is
>
> https://bits.netbeans.org/12.5/javadoc/org-netbeans-modules-projectuiapi-base/
> org/netbeans/api/project/ui/OpenProjects.html#getOpenProjects--
> 
>
> or there is
>
> https://bits.netbeans.org/12.5/javadoc/org-netbeans-modules-projectapi/org/
> netbeans/api/project/ProjectManager.html#findProject-
> 
> org.openide.filesystems.FileObject-
>
> -jt
>
> > Hi All
> >
> >These give me null:
> >
> > Lookup lookup = Utilities.actionsGlobalContext();
> > Project project = lookup.lookup(Project.class);
> >
> > This also null:
> >
> > OpenProjects.getDefault().getMainProject()
> >
> > How can I find the current selected project? thanks
> >
> >
> > Thanks
> >
> > From Peter (System Architect, Quantr Limited https://www.quantr.hk ,
> Mobile
> > : 96554595)
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>

Question about ParserResult.getDiagnostics()

2021-10-31 Thread Bartosz Tomasik 
Hi

 quick question: what is this method supposed to do?
https://github.com/apache/netbeans/blob/76448e5011d37650a804a9a1c4fdf36f676807f3/ide/csl.types/src/org/netbeans/modules/csl/spi/ParserResult.java#L37


 Do I need to create my own syntax error highlighter tasl/factory if I
provide list of syntax errors via getDiagnostics()?


-- 

regards

Bartosz


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

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

Re: LSP Language Server Protocol

2021-10-31 Thread Eric Bresie 
Thanks Chris, this is very helpful and appreciated,  Some more below..

Eric Bresie
ebre...@gmail.com


On Wed, Oct 27, 2021 at 1:47 PM Christian Lenz 
wrote:

> Hey Eric,
>
> probably you already found your answers, but this may also be helpful for
> others. Here are some answers to your questions from my understanding,
> please if smth is wrong, someone correct me:
>
> > I’ve seen the tutorial and appreciated the context, but was curious if
> more
> generalized perspective can be expanded on as this is a specific
> implementation.  Some of the following may be implied by the article
> indirectly but wanted to confirm it here as well.
>
> The article you are talking about (
> https://blogs.apache.org/netbeans/entry/lsp-client-demo-ba-sh) is for
> implementing a custom language
> via textmate and a language server. This seems more or less generic.


Drilling down some,I was able to find some of the more general things, as
well as based on previous discussions.
For this I was talking about general "sub-tasks" (i.e. implement
preferences, handling different "versions", execution, autocompletion,
etc.).

For textmate it is, for LSP maybe also but not for all LSP implementations
> out there
> (
> https://microsoft.github.io/language-server-protocol/implementors/servers/).
>


So is this saying the LSP may already provide some aspects of what the
textmate highlighting functionality?


> A friend of mine tried to implement the omnisharp LSP into NetBeans
> but he needed to updaate the eclipse lsp. Please see the repo here why and
> what he did: https://github.com/ranSprd/netbeans-lsp-client-fork.
>

Will look at this to see more.


> I also had a talk with a developer. They said that the LSP is more or less
> generic but as we all know, you can implement your own stuff into it,
> what might break the concept of that. So it could be, that you need to add
> specific code for each LSP anyway but should be not that much.
>
> Not each language needs a LSP. Textmate and LSP are 2 different things.
> Maybe the LSP also uses the same textmate files or others to parse the file,
> but you can add languages with textmate without having a LSP. I did this
> for example: https://github.com/Chris2011/netbeans-textmate-files


> But that means, that you just have basic syntax highlighting, thats it.


 I found the python textmate from above and was able to get some basic
language highlighting working, so this was very helpful.

The LSP implementation in NetBeans, hopefully will work with most of the
> stuff,
> didn't test it yet, but I think we need to be up to date with all
> dependencies and mentioned above for the OmniSharp LS.
>

Is a ticket to update that needed?


> > Assume if a server is not available then one may need to be implemented.
> Assume to do this would require compliance with LSP interface of some type
> and if so where can this be found?  Is there interface defined in Netbeans
> which can be extended or implemented from?
>
> Yes, if there is no LS for a specific language is available, we or someone
> else needs to create one. But step by step. For doing that, I would prefer
> to read about the stuff at the MS page:
> https://microsoft.github.io/language-server-protocol/. But I think for
> most of the langauges, there is one.
> I also find one for NixOS nix config files.
>
>
> > If an server is available how should that be brought in?  Add a
> dependency
> which gets pulled in with maybe some wrapper layer having it?
>
> If a server is available, you should see the tutorial from Jan in which he
> called just the command line tool. In the example it is node but could be
> any exe or CLI tool that you want. As long as you post the arguments
> correctly.
>

Started trying to use one of the implementations which in the case of
python involves executing a python script.  After that I'm not really sure
if this is working or not.  I assume it depends on specific servers but
assume when starting up the LSP, it awaits for "LSP" calls and responses
back.  So how are those triggered?  For example, for autocompletion, what
triggers (and what specific call) from "autocomplete client" to call to the
"LSP Server" running in the background?

> In what context does the “server” get started up/loaded within Netbeans?
> Are there specific triggers to start it (i.e. when working on a specific
> file type of the given language, if the language support is “active”, at
> startup, or some other trigger)?
>
> On the last sentence of the tutorial it says: Caveat: the language server
> is started only for files that are inside a project, so create (any) new
> project, and inside the project, put a shell file. E.g. copy "bin/netbeans"
> as "test.sh" into the project. Open it in the editor - there should be
> syntax highlighting, Navigator, and code completion should show something,
> etc.
>

With what I've implemented so far, the coloration works but not the code
completion.  Assume this is where the LSP needs to pick up some of the
wor

Graduating Friend APIs to Public APIs (Web Commons)

2021-10-31 Thread Eric Bresie 
While working on a new python module (since I've seen little progress on
python donation completion and trying to make an LSP based version) , I
borrowed code from another language support (javascript/node js) to model
som of the functionality after which had dependencies like

import org.netbeans.modules.web.common.api.Version;
import org.netbeans.modules.web.common.ui.api.ExternalExecutable;


When attempting to build in the final steps (building the nbm) I
encountered a build issue like the following (for full trace see end of
email):

Failed to execute goal
org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend. -> [Help
1]


My assumption is my module is not a "friend" to the web.common and/pr
web.common.ui related packages which is preventing that from finishing up.

While discussing on stack, it was suggested maybe making the Web.Commons
packages "public" instead of requiring to update with all the "friends" may
be a better option.

I found
https://cwiki.apache.org/confluence/display/NETBEANS/Public+vs+Friend+API
which seems to imply after a time it may be worth making things public
(i.e. if there are more than 5 friends, the API is stable and not changing
a lot, etc.)

So with that in mind and the fact that there appears to be a lot of friends
on these packages, is it worth changing the web.common/web.common.ui to be
a public API?

If so, what is the process by which this is normally done (i.e. change from
friend to public, any API documentation updates, any build changes,
regression testing, etc.)?

Eric Bresie
ebre...@gmail.com

Full stack trace:

Failed to execute goal
org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend. -> [Help
1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.netbeans.utilities:nbm-maven-plugin:4.6:manifest
(default-manifest) on project python: Module has friend dependency on
org.netbeans.modules.web.common.ui but is not listed as a friend.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoFailureException: Module has friend
dependency on org.netbeans.modules.web.common.ui but is not listed as a
friend.
at
org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.visibleModuleClasses
(NetBeansManifestUpdateMojo.java:900)
at
org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.checkModuleClassPath
(NetBeansManifestUpdateMojo.java:717)
at org.apache.netbeans.nbm.NetBeansManifestUpdateMojo.execute
(NetBeansManifestUpdateMojo.java:561)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:1

Re: UTF-8 input is broken in Maven project

2021-10-31 Thread Vladimir Machat 

Great, it works! Thanks

I hope it will make it into 12.6...

On 31/10/2021 03:22, Michael Bien wrote:
the hint that it was a maven specific issue helped me to find it 
relatively quickly - thanks :)


https://github.com/apache/netbeans/pull/3289

i don't know if it will make it into NB 12.6, thats in the hand of the 
reviewers.


best regards,
michael


On 30.10.21 12:19, Vladimir Machat wrote:


Hi Michael,

yes I have tried that, but nothing changed :(

On 30/10/2021 11:10, Michael Bien wrote:

Hi Vladimir,

thats interesting. Since you are on linux, UTF-8 should be the 
default as far as I know.


have you tried to add -J-Dfile.encoding=UTF-8 to your 
etc/netbeans.conf (netbeans_default_options property)?


regards,
michael


On 30.10.21 11:55, Vladimir Machat wrote:

Hi All,

When I create a Java with Maven Project and try to run simple code 
like this:


Scanner sc = new Scanner(System.in, "UTF-8");
System.out.println("Enter text: ");
String text = sc.nextLine();
System.out.println("You have entered: " + text);

If I enter anything containing letters like ščřžýáíé (from the 
czech language), the output in the output window would be broken, 
the special letters replaced with characters like �.


The exactly same code works perfectly in the same Netbeans 
installation, just using the project Java with Ant.


Also if I  run the project in terminal outside Netbeans, using the 
command from the output window, it works correctly.


I tried this on Manjaro Linux and Windows 10, with Netbeans 12.5 
12.4 12.3, with the same result.


Any ideas how to solve this problem?

Thanks

PS: I created an issue in Netbeans Jira about it a while ago:

https://issues.apache.org/jira/browse/NETBEANS-6115

verilog plugin

2021-10-31 Thread Peter Cheung 
Hi
   This is our verilog plugin for netbeans 
https://www.quantr.foundation/project/netbeansverilog


Thanks

>From Peter (System Architect, Quantr Limited https://www.quantr.hk , Mobile : 
>96554595)