[jira] [Comment Edited] (NETBEANS-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464168#comment-17464168 ] Gregory Sartucci edited comment on NETBEANS-6107 at 12/23/21, 3:23 AM: --- I think I'm having the same issue, or something close. I'm currently trying to work with a java 16+ project using Gradle, in Netbeans, and I'm getting this error: A problem occurred evaluating root project 'architectury-example-mod'. > Failed to apply plugin 'dev.architectury.loom'. > You are using an outdated version of Java (11). Java 16 or higher is required. The JAVA_HOME environment variable is currently set to (/usr/lib/jvm/graalvm-ce-java17-21.3.0). I've set my Netbeans to use Java 17 anywhere and everywhere I can. I don't see any option for setting the JDK version used for Gradle, the way there is for Maven, though. Is that the problem? And, if so, is there a way for me to fix it? :/ Edit: Okay, I was eventually able to get Netbeans to run on java 17. I had to make a whole new installation, but I got it working. was (Author: angularangel): I think I'm having the same issue, or something close. I'm currently trying to work with a java 16+ project using Gradle, in Netbeans, and I'm getting this error: A problem occurred evaluating root project 'architectury-example-mod'. > Failed to apply plugin 'dev.architectury.loom'. > You are using an outdated version of Java (11). Java 16 or higher is required. The JAVA_HOME environment variable is currently set to (/usr/lib/jvm/graalvm-ce-java17-21.3.0). I've set my Netbeans to use Java 17 anywhere and everywhere I can. I don't see any option for setting the JDK version used for Gradle, the way there is for Maven, though. Is that the problem? And, if so, is there a way for me to fix it? :/ Edit: Okay, I was eventually able to get Netbeans to run on java 17. I had to make a whole new installation, but I got it working. > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Comment Edited] (NETBEANS-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464168#comment-17464168 ] Gregory Sartucci edited comment on NETBEANS-6107 at 12/23/21, 12:20 AM: I think I'm having the same issue, or something close. I'm currently trying to work with a java 16+ project using Gradle, in Netbeans, and I'm getting this error: A problem occurred evaluating root project 'architectury-example-mod'. > Failed to apply plugin 'dev.architectury.loom'. > You are using an outdated version of Java (11). Java 16 or higher is required. The JAVA_HOME environment variable is currently set to (/usr/lib/jvm/graalvm-ce-java17-21.3.0). I've set my Netbeans to use Java 17 anywhere and everywhere I can. I don't see any option for setting the JDK version used for Gradle, the way there is for Maven, though. Is that the problem? And, if so, is there a way for me to fix it? :/ Edit: Okay, I was eventually able to get Netbeans to run on java 17. I had to make a whole new installation, but I got it working. was (Author: angularangel): I think I'm having the same issue, or something close. I'm currently trying to work with a java 16+ project using Gradle, in Netbeans, and I'm getting this error: A problem occurred evaluating root project 'architectury-example-mod'. > Failed to apply plugin 'dev.architectury.loom'. > You are using an outdated version of Java (11). Java 16 or higher is required. The JAVA_HOME environment variable is currently set to (/usr/lib/jvm/graalvm-ce-java17-21.3.0). I've set my Netbeans to use Java 17 anywhere and everywhere I can. I don't see any option for setting the JDK version used for Gradle, the way there is for Maven, though. Is that the problem? And, if so, is there a way for me to fix it? :/ > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-6107) Gradle support does not work when NB/project is JDK17
[ https://issues.apache.org/jira/browse/NETBEANS-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17464168#comment-17464168 ] Gregory Sartucci commented on NETBEANS-6107: I think I'm having the same issue, or something close. I'm currently trying to work with a java 16+ project using Gradle, in Netbeans, and I'm getting this error: A problem occurred evaluating root project 'architectury-example-mod'. > Failed to apply plugin 'dev.architectury.loom'. > You are using an outdated version of Java (11). Java 16 or higher is required. The JAVA_HOME environment variable is currently set to (/usr/lib/jvm/graalvm-ce-java17-21.3.0). I've set my Netbeans to use Java 17 anywhere and everywhere I can. I don't see any option for setting the JDK version used for Gradle, the way there is for Maven, though. Is that the problem? And, if so, is there a way for me to fix it? :/ > Gradle support does not work when NB/project is JDK17 > - > > Key: NETBEANS-6107 > URL: https://issues.apache.org/jira/browse/NETBEANS-6107 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle >Affects Versions: 12.5 > Environment: macOS, GraalVM JDK17, using Micronaut Gradle project, > generated by wizard. >Reporter: Martin Balin >Assignee: Svata Dedic >Priority: Major > Labels: pull-request-available > Fix For: 12.6 > > Attachments: Screenshot 2021-10-05 at 10.57.02.png > > Time Spent: 3h 20m > Remaining Estimate: 0h > > Opening Gradle based project which uses JDK17 and running NB on JDK17 does > not Resolve Problems when project is open. > It is stuck in this with attached screenshot error. Running Build as command > completes as it uses Gradle 7.2 along with JDK17. > I don't know why JDK16 is referenced, it does not exist on the system and I > also removed all NB user dirs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-6298) Match NetBeans console encoding to system/app console encoding
[ https://issues.apache.org/jira/browse/NETBEANS-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463887#comment-17463887 ] luke commented on NETBEANS-6298: [~almson] Here is the entire output： !full_output.png! > Match NetBeans console encoding to system/app console encoding > -- > > Key: NETBEANS-6298 > URL: https://issues.apache.org/jira/browse/NETBEANS-6298 > Project: NetBeans > Issue Type: Bug > Components: cnd - Editor >Affects Versions: 12.0, 12.1, 12.2, 12.3, 12.4, 12.5, 12.6, NB13, 13 > Environment: Windows 10、JDK1.8.201、Maven3.6.0、Netbeans12.6、Project > encoding UTF-8 >Reporter: luke >Priority: Blocker > Attachments: Garbled.gif, Garbled.png, full_output.png > > > My Windows OS language is Simplified Chinese and the default OS encoding is > GBK. When I open a properties file or a text file, the editor shows the file > contents as garbled, if I add the parameter -J-Dfile.encoding=UTF-8, the > editor opens the file in UTF-8 encoding format and the file is not garbled, > but the console output is garbled. > !Garbled.gif|width=1055,height=536! > !Garbled.png|width=1542,height=843! -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-6305) ProjectManager.find() return null for project dir - race between Git and Projects
[
https://issues.apache.org/jira/browse/NETBEANS-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463878#comment-17463878
]
Jaroslav Tulach commented on NETBEANS-6305:
---
Workaround pushed as https://github.com/apache/netbeans/pull/3375
> ProjectManager.find() return null for project dir - race between Git and
> Projects
> -
>
> Key: NETBEANS-6305
> URL: https://issues.apache.org/jira/browse/NETBEANS-6305
> Project: NetBeans
> Issue Type: Bug
> Components: projects - Generic Infrastructure, versioncontrol - Git
>Reporter: Svatopluk Dedic
>Assignee: Jaroslav Tulach
>Priority: Major
> Labels: VSNetBeans
> Attachments: git-project-race-strack.png, git-project-race1.png,
> git-project-race2.png
>
>
> I was trying to write some gradle projects tests using NbModuleSuite – the
> plan was to create a simpel gradle project (just buildscript), then open it
> as a project and inspect.
> To my surprise, calls like FileObject.createAndOpen or
> FileObject.getOuputStream() write (inside FS Atomic Action) resulted in the
> project directory not being recognized at all ! When I tried to debug the
> situation, a stop in the debugger (just a single thread) caused the project
> to be found magically.
> It turned to be a race between Git module (the workdir is created inside the
> source tree managed by git) and the Project system: Git module runs as
> extension to filesystems even inside FS Atomic Action (shown on a pictured
> stacktrace from debugger) and executes {*}FileOwnerQuery{*}{*}.findOwner{*}
> on the to-be-project directory before the buildscript is even created. The
> result of *not being a project* is then cached - and the cache is reset
> asynchronously when/after the project file is created.
> But the test manages to call ProjectManager.findProject sooner, while the
> cache still holds the negative result.
> One of the screenshots shows a debugger that stopped in a situation when the
> script file has been already created (a message in the output window), but
> project manager call invoked *after* the creation does not find a project.
> Uncommenting the m.invoke() line in HACK section will fix the situation -
> caches must be reset.
> The other screenshot is a debugger stopping when the to-be-project directory
> is first inspected, showing that the directory's is yet empty.
> // cc: [~entlicher]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-6298) Match NetBeans console encoding to system/app console encoding
[ https://issues.apache.org/jira/browse/NETBEANS-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] luke updated NETBEANS-6298: --- Attachment: full_output.png > Match NetBeans console encoding to system/app console encoding > -- > > Key: NETBEANS-6298 > URL: https://issues.apache.org/jira/browse/NETBEANS-6298 > Project: NetBeans > Issue Type: Bug > Components: cnd - Editor >Affects Versions: 12.0, 12.1, 12.2, 12.3, 12.4, 12.5, 12.6, NB13, 13 > Environment: Windows 10、JDK1.8.201、Maven3.6.0、Netbeans12.6、Project > encoding UTF-8 >Reporter: luke >Priority: Blocker > Attachments: Garbled.gif, Garbled.png, full_output.png > > > My Windows OS language is Simplified Chinese and the default OS encoding is > GBK. When I open a properties file or a text file, the editor shows the file > contents as garbled, if I add the parameter -J-Dfile.encoding=UTF-8, the > editor opens the file in UTF-8 encoding format and the file is not garbled, > but the console output is garbled. > !Garbled.gif|width=1055,height=536! > !Garbled.png|width=1542,height=843! -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-6186) NbModuleSuite can fail on Java 11 while working on Java 8
[ https://issues.apache.org/jira/browse/NETBEANS-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463874#comment-17463874 ] Jaroslav Tulach commented on NETBEANS-6186: --- My Nov 4 suggestion: https://github.com/apache/netbeans/pull/3298#issuecomment-960494881 hasn't been implemented yet, as far as can tell. Does anyone care about running our tests on JDK11 and newer? > NbModuleSuite can fail on Java 11 while working on Java 8 > - > > Key: NETBEANS-6186 > URL: https://issues.apache.org/jira/browse/NETBEANS-6186 > Project: NetBeans > Issue Type: Bug > Components: platform - JDK Problems >Reporter: Laszlo Kishalmi >Assignee: Jaroslav Tulach >Priority: Major > > This one is the result of:https://github.com/apache/netbeans/pull/3298 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Resolved] (NETBEANS-5689) NetBeans does not start on JDK build with JEP 411
[
https://issues.apache.org/jira/browse/NETBEANS-5689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-5689.
---
Fix Version/s: 12.5
Resolution: Fixed
thanks to enormous community work of [~geertjan] & other NetBeans members, the
JEP-411 has been significantly modified, and phased out into the future.
NetBeans do start with JDK17 and we have enough time to get ready for
up-comming changes. Many of them already happened:
https://github.com/apache/netbeans/commit/4c9d9492f70b09aaeae2b8b10fc26ae29433d667
> NetBeans does not start on JDK build with JEP 411
> -
>
> Key: NETBEANS-5689
> URL: https://issues.apache.org/jira/browse/NETBEANS-5689
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Module System
>Reporter: Jan Lahoda
>Assignee: Jaroslav Tulach
>Priority: Blocker
> Fix For: 12.5
>
>
> Using a build of JDK with this change:
> [https://github.com/openjdk/jdk/pull/4073]
> which implements JEP 411:
> [https://openjdk.java.net/jeps/411]
>
> NetBeans does not start anymore:
> {code:java}
> $ ./netbeans --userdir /tmp/jep411-test --jdkhome
> java.lang.UnsupportedOperationException: Runtime configured to disallow
> security manager
> at java.base/java.lang.System.setSecurityManager(System.java:394)
> at
> org.netbeans.TopSecurityManager.install(TopSecurityManager.java:525)
> at
> org.netbeans.core.NbLifecycleManager.advancePolicy(NbLifecycleManager.java:69)
>
> at org.netbeans.core.GuiRunLevel.run(GuiRunLevel.java:84)
> at org.netbeans.core.startup.Main.start(Main.java:295)
> at
> org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Closed] (NETBEANS-3104) Extend ArchetypeWizards.definedArchetype to include optional nbactions
[
https://issues.apache.org/jira/browse/NETBEANS-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-3104.
-
Resolution: Won't Fix
Adding optional {{nbactions}} is fine. I suggest to do it as part of the PR
that is going to use them.
> Extend ArchetypeWizards.definedArchetype to include optional nbactions
> --
>
> Key: NETBEANS-3104
> URL: https://issues.apache.org/jira/browse/NETBEANS-3104
> Project: NetBeans
> Issue Type: Improvement
>Reporter: Geertjan Wielenga
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: 12.2
>
>
> http://bits.netbeans.org/dev/javadoc/org-netbeans-api-maven/org/netbeans/api/maven/archetype/ArchetypeWizards.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Closed] (NETBEANS-5158) More user friendly configuration for mx projects
[
https://issues.apache.org/jira/browse/NETBEANS-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-5158.
-
Fix Version/s: 12.5
Resolution: Fixed
Since 12.6 there is "Edit" action on the "mx projects" that opens various
existing {{suite.py}} and {{env}} files in editor.
> More user friendly configuration for mx projects
>
>
> Key: NETBEANS-5158
> URL: https://issues.apache.org/jira/browse/NETBEANS-5158
> Project: NetBeans
> Issue Type: New Feature
> Components: java - Project
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
> Fix For: 12.5
>
>
> "mx project support" as provided by
> [PR-2575|https://github.com/apache/netbeans/pull/2575] is assuming that
> {{mx}} is on execution path, that {{$HOME/.mx/env}} is set properly and
> doesn't provide any UI to configure that. Should be improved, if the support
> is supposed to be used by non-educated users.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[netbeans-website] branch master updated: imports and custom conditions
This is an automated email from the ASF dual-hosted git repository.
geertjan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/netbeans-website.git
The following commit(s) were added to refs/heads/master by this push:
new de7625b imports and custom conditions
new 82f42b6 Merge pull request #565 from mbien/patch-1
de7625b is described below
commit de7625beecc498cc45473ae557340a3b888603dd
Author: Michael Bien
AuthorDate: Sat Oct 23 03:51:13 2021 +0200
imports and custom conditions
added examples for imports and custom conditions. Mostly taken from the old
bitbucket wiki, minor updates.
---
.../src/content/jackpot/HintsFileFormat.asciidoc | 53 --
1 file changed, 49 insertions(+), 4 deletions(-)
diff --git a/netbeans.apache.org/src/content/jackpot/HintsFileFormat.asciidoc
b/netbeans.apache.org/src/content/jackpot/HintsFileFormat.asciidoc
index 831d13d..f57428d 100644
--- a/netbeans.apache.org/src/content/jackpot/HintsFileFormat.asciidoc
+++ b/netbeans.apache.org/src/content/jackpot/HintsFileFormat.asciidoc
@@ -32,9 +32,10 @@ The rules file consists of any number of transformation
rules.
The rule is defined as follows:
[source,java]
-
- =>
- =>
+"description text":
+ ::
+ => ::
+ => ::
;;
@@ -63,6 +64,8 @@ to:
Note: `$1` is a variable, explained in the <> section.
+Note: conditions are explained in the <> section.
+
Note: batch refactoring will typically use only the first applicable fix
patterns of each applicable rule.
== Patterns
@@ -313,7 +316,32 @@ Note: Special variable `$_` represents the whole matching
region.
=== Custom Conditions
-TBD
+The following rule finds variables of the type `com.whatever.Option` and name
"foo" or "bar" and renames them.
+
+[source,java]
+
+
+
+$opt:: $opt instanceof com.whatever.Option && matchName($opt)
+=> $optNew :: changeVariableName($opt, $optNew)
+;;
+
+ names = Set.of("foo", "bar");
+?>
+
== Display Names and Localization
@@ -322,6 +350,23 @@ TBD
[[custom-imports]]
== Custom Imports
+[source,java]
+
+
+
+ new LinkedList()
+=> new ArrayList()
+;;
+
+ LinkedList $0;
+=> ArrayList $0;
+;;
+
+
+
== Notable Patterns
=== Catch Pattern
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-6298) Match NetBeans console encoding to system/app console encoding
[ https://issues.apache.org/jira/browse/NETBEANS-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463787#comment-17463787 ] Aleksandr Dubinsky commented on NETBEANS-6298: -- It'd be helpful to see the entire output, including Maven Exec parameters. The console encoding is mismatched. The application is using "x-mswin-936" while Netbeans terminal is using UTF-8. The sun.*.encoding VM options should have an effect, and did for me. Not sure what you're doing wrong. It would be an easy fix to get the Netbeans console to use the system encoding. Hopefully some of the devs take notice. > Match NetBeans console encoding to system/app console encoding > -- > > Key: NETBEANS-6298 > URL: https://issues.apache.org/jira/browse/NETBEANS-6298 > Project: NetBeans > Issue Type: Bug > Components: cnd - Editor >Affects Versions: 12.0, 12.1, 12.2, 12.3, 12.4, 12.5, 12.6, NB13, 13 > Environment: Windows 10、JDK1.8.201、Maven3.6.0、Netbeans12.6、Project > encoding UTF-8 >Reporter: luke >Priority: Blocker > Attachments: Garbled.gif, Garbled.png > > > My Windows OS language is Simplified Chinese and the default OS encoding is > GBK. When I open a properties file or a text file, the editor shows the file > contents as garbled, if I add the parameter -J-Dfile.encoding=UTF-8, the > editor opens the file in UTF-8 encoding format and the file is not garbled, > but the console output is garbled. > !Garbled.gif|width=1055,height=536! > !Garbled.png|width=1542,height=843! -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-5614) nb-javac error on Java 1.8 project with profile
[ https://issues.apache.org/jira/browse/NETBEANS-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463783#comment-17463783 ] Peter Loveall commented on NETBEANS-5614: - Still occurring in 12.6. Attached is XML from error report.[^errorlogxml.txt] > nb-javac error on Java 1.8 project with profile > --- > > Key: NETBEANS-5614 > URL: https://issues.apache.org/jira/browse/NETBEANS-5614 > Project: NetBeans > Issue Type: Bug > Components: java - Compiler >Affects Versions: 12.3 > Environment: Netbeans 12.3 for Windows. nb-javac 15.0.0.2. >Reporter: Peter Loveall >Priority: Major > > When working on a Java 8 (1.8) project, the following error will occur if any > profile other than Full JRE is defined: > Caused: java.lang.IllegalStateException: error: option -profile not allowed > with target 15 > This is easily reproduceable: > Create a Java 8 project and set the profile to something other than Full JRE. > Issue occurs regardless of JDK being used to run Netbeans (JDK 8, 11, and 15 > tested). JDK 1.8 is used for library and JDK 8 is source/binary format. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-5614) nb-javac error on Java 1.8 project with profile
[ https://issues.apache.org/jira/browse/NETBEANS-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Loveall updated NETBEANS-5614: Attachment: errorlogxml.txt > nb-javac error on Java 1.8 project with profile > --- > > Key: NETBEANS-5614 > URL: https://issues.apache.org/jira/browse/NETBEANS-5614 > Project: NetBeans > Issue Type: Bug > Components: java - Compiler >Affects Versions: 12.3 > Environment: Netbeans 12.3 for Windows. nb-javac 15.0.0.2. >Reporter: Peter Loveall >Priority: Major > Attachments: errorlogxml.txt > > > When working on a Java 8 (1.8) project, the following error will occur if any > profile other than Full JRE is defined: > Caused: java.lang.IllegalStateException: error: option -profile not allowed > with target 15 > This is easily reproduceable: > Create a Java 8 project and set the profile to something other than Full JRE. > Issue occurs regardless of JDK being used to run Netbeans (JDK 8, 11, and 15 > tested). JDK 1.8 is used for library and JDK 8 is source/binary format. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-6328) IllegalArgumentException caused by FoldManagerImpl in LSP client
[
https://issues.apache.org/jira/browse/NETBEANS-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated NETBEANS-6328:
-
Labels: pull-request-available (was: )
> IllegalArgumentException caused by FoldManagerImpl in LSP client
>
>
> Key: NETBEANS-6328
> URL: https://issues.apache.org/jira/browse/NETBEANS-6328
> Project: NetBeans
> Issue Type: Bug
> Components: lsp
>Affects Versions: 12.6
> Environment: Windows and Linux
> Tested with Python language server:
> https://github.com/palantir/python-language-server
>Reporter: Michael Küttner
>Assignee: Michael Küttner
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{java.lang.IllegalArgumentException: Invalid end offset: -2, start is: 28}}
> {{at org.netbeans.spi.editor.fold.FoldInfo.(FoldInfo.java:103)}}
> {{at org.netbeans.spi.editor.fold.FoldInfo.range(FoldInfo.java:94)}}
> {{at
> org.netbeans.modules.lsp.client.bindings.FoldManagerImpl.run(FoldManagerImpl.java:126)}}
> {{at
> org.netbeans.modules.lsp.client.LSPBindings.lambda$addBackgroundTask$13(LSPBindings.java:411)}}
> {{at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)}}
> {{at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)}}
> {{at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)}}
> {{at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)}}
> {{[catch] at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033) }}
> This exception occurs if a language server returns FoldingRanges without an
> endCharacter (only lines are set) and if the fold reaches until end of
> current document.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
