[jira] [Resolved] (NETBEANS-6478) Support for Knockout's "checked" binding broken.
[
https://issues.apache.org/jira/browse/NETBEANS-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-6478.
---
Fix Version/s: 14
Resolution: Fixed
> Support for Knockout's "checked" binding broken.
>
>
> Key: NETBEANS-6478
> URL: https://issues.apache.org/jira/browse/NETBEANS-6478
> Project: NetBeans
> Issue Type: Bug
> Components: platform - HTML4J
>Reporter: Dusan Balek
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: 14
>
> Attachments: kobinding.zip
>
>
> HTML4J does not correctly support Knockout's "checked" binding that includes
> {{checkedValue.}} The following code snippet illustrating the use case is
> copied from the Knockout documentation:
> {code:java}
>
>
>
>
>
> var viewModel = {
> items: ko.observableArray([
> { itemName: 'Choice 1' },
> { itemName: 'Choice 2' }
> ]),
> chosenItems: ko.observableArray()
> };
> {code}
> Having the corresponding Java:
> {code:java}
> @HTMLDialog(url = ".html")
> static HTMLDialog.OnSubmit showUI() {
> ViewModel model = new ViewModel();
> model.applyBindings();
> return (id) -> {
> List chosenItems = model.getChosenItems();
> return !chosenItems.isEmpty();
> };
> }
> @Model(className = "ViewModel", targetId = "", instance = true, builder =
> "with", properties = {
> @Property(name = "chosenItems", type = Item.class, array = true)
> })
> static final class ViewModelControl {
> @ComputedProperty
> static List items() {
> return Arrays.asList(new Item("Choice 1"), new Item("Choice 2"));
> }
> }
> @Model(className = "Item", instance = true, properties = {
> @Property(name = "itemName", type = String.class)
> })
> static final class ItemControl {
> }
> {code}
> The content of `chosenItems` does not reflect changes in checkbox selection.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
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-6478) Support for Knockout's "checked" binding broken.
[
https://issues.apache.org/jira/browse/NETBEANS-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606328#comment-17606328
]
Jaroslav Tulach commented on NETBEANS-6478:
---
I got the binding working in the [^kobinding.zip] example. It maintains two
lists {{todos}} and {{selectedTodos}}. Run and/or debug in NetBeans, *Add* new
items and *Change* their checked status. All seems to be working.
> Support for Knockout's "checked" binding broken.
>
>
> Key: NETBEANS-6478
> URL: https://issues.apache.org/jira/browse/NETBEANS-6478
> Project: NetBeans
> Issue Type: Bug
> Components: platform - HTML4J
>Reporter: Dusan Balek
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: kobinding.zip
>
>
> HTML4J does not correctly support Knockout's "checked" binding that includes
> {{checkedValue.}} The following code snippet illustrating the use case is
> copied from the Knockout documentation:
> {code:java}
>
>
>
>
>
> var viewModel = {
> items: ko.observableArray([
> { itemName: 'Choice 1' },
> { itemName: 'Choice 2' }
> ]),
> chosenItems: ko.observableArray()
> };
> {code}
> Having the corresponding Java:
> {code:java}
> @HTMLDialog(url = ".html")
> static HTMLDialog.OnSubmit showUI() {
> ViewModel model = new ViewModel();
> model.applyBindings();
> return (id) -> {
> List chosenItems = model.getChosenItems();
> return !chosenItems.isEmpty();
> };
> }
> @Model(className = "ViewModel", targetId = "", instance = true, builder =
> "with", properties = {
> @Property(name = "chosenItems", type = Item.class, array = true)
> })
> static final class ViewModelControl {
> @ComputedProperty
> static List items() {
> return Arrays.asList(new Item("Choice 1"), new Item("Choice 2"));
> }
> }
> @Model(className = "Item", instance = true, properties = {
> @Property(name = "itemName", type = String.class)
> })
> static final class ItemControl {
> }
> {code}
> The content of `chosenItems` does not reflect changes in checkbox selection.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
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-6478) Support for Knockout's "checked" binding broken.
[
https://issues.apache.org/jira/browse/NETBEANS-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-6478:
--
Attachment: kobinding.zip
> Support for Knockout's "checked" binding broken.
>
>
> Key: NETBEANS-6478
> URL: https://issues.apache.org/jira/browse/NETBEANS-6478
> Project: NetBeans
> Issue Type: Bug
> Components: platform - HTML4J
>Reporter: Dusan Balek
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: kobinding.zip
>
>
> HTML4J does not correctly support Knockout's "checked" binding that includes
> {{checkedValue.}} The following code snippet illustrating the use case is
> copied from the Knockout documentation:
> {code:java}
>
>
>
>
>
> var viewModel = {
> items: ko.observableArray([
> { itemName: 'Choice 1' },
> { itemName: 'Choice 2' }
> ]),
> chosenItems: ko.observableArray()
> };
> {code}
> Having the corresponding Java:
> {code:java}
> @HTMLDialog(url = ".html")
> static HTMLDialog.OnSubmit showUI() {
> ViewModel model = new ViewModel();
> model.applyBindings();
> return (id) -> {
> List chosenItems = model.getChosenItems();
> return !chosenItems.isEmpty();
> };
> }
> @Model(className = "ViewModel", targetId = "", instance = true, builder =
> "with", properties = {
> @Property(name = "chosenItems", type = Item.class, array = true)
> })
> static final class ViewModelControl {
> @ComputedProperty
> static List items() {
> return Arrays.asList(new Item("Choice 1"), new Item("Choice 2"));
> }
> }
> @Model(className = "Item", instance = true, properties = {
> @Property(name = "itemName", type = String.class)
> })
> static final class ItemControl {
> }
> {code}
> The content of `chosenItems` does not reflect changes in checkbox selection.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
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-5829) Incorrect "Text blocks aren't supported"
[
https://issues.apache.org/jira/browse/NETBEANS-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17513226#comment-17513226
]
Jaroslav Tulach edited comment on NETBEANS-5829 at 3/28/22, 8:17 AM:
-
With [PR-3715|https://github.com/apache/netbeans/pull/3715] the behavior is
sufficiently acceptable.
was (Author: jtulach):
With [PR-3715](https://github.com/apache/netbeans/pull/3715) the behavior is
sufficiently acceptable.
> Incorrect "Text blocks aren't supported"
>
>
> Key: NETBEANS-5829
> URL: https://issues.apache.org/jira/browse/NETBEANS-5829
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Major
> Labels: pull-request-available
> Fix For: 14
>
> Attachments: image-2021-07-02-08-47-25-560.png
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Get
> [https://github.com/apache/netbeans-html4j/blob/release-1.7.2/json-tck/src/main/java/net/java/html/js/tests/AsyncJavaScriptAction.java#L36],
> open it in most recent NetBeans IDE running on JDK8 (with nbjavac@16.0.0.0
> installed) and try to convince the editor to not show errors about text
> blocks:
> !image-2021-07-02-08-47-25-560.png!
> Is there some way to do so? It is very annoying to have the source tree full
> of useless errors related to text blocks, when everything compiles and runs
> fine. The project's source level is set to 15 and Maven support shall report
> that to {{java.source}}. Any help welcomed.
--
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-5829) Incorrect "Text blocks aren't supported"
[
https://issues.apache.org/jira/browse/NETBEANS-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-5829.
---
Fix Version/s: 14
Resolution: Fixed
With [PR-3715](https://github.com/apache/netbeans/pull/3715) the behavior is
sufficiently acceptable.
> Incorrect "Text blocks aren't supported"
>
>
> Key: NETBEANS-5829
> URL: https://issues.apache.org/jira/browse/NETBEANS-5829
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Major
> Labels: pull-request-available
> Fix For: 14
>
> Attachments: image-2021-07-02-08-47-25-560.png
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Get
> [https://github.com/apache/netbeans-html4j/blob/release-1.7.2/json-tck/src/main/java/net/java/html/js/tests/AsyncJavaScriptAction.java#L36],
> open it in most recent NetBeans IDE running on JDK8 (with nbjavac@16.0.0.0
> installed) and try to convince the editor to not show errors about text
> blocks:
> !image-2021-07-02-08-47-25-560.png!
> Is there some way to do so? It is very annoying to have the source tree full
> of useless errors related to text blocks, when everything compiles and runs
> fine. The project's source level is set to 15 and Maven support shall report
> that to {{java.source}}. Any help welcomed.
--
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] [Assigned] (NETBEANS-5829) Incorrect "Text blocks aren't supported"
[
https://issues.apache.org/jira/browse/NETBEANS-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-5829:
-
Assignee: Jaroslav Tulach (was: Jan Lahoda)
> Incorrect "Text blocks aren't supported"
>
>
> Key: NETBEANS-5829
> URL: https://issues.apache.org/jira/browse/NETBEANS-5829
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2021-07-02-08-47-25-560.png
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Get
> [https://github.com/apache/netbeans-html4j/blob/release-1.7.2/json-tck/src/main/java/net/java/html/js/tests/AsyncJavaScriptAction.java#L36],
> open it in most recent NetBeans IDE running on JDK8 (with nbjavac@16.0.0.0
> installed) and try to convince the editor to not show errors about text
> blocks:
> !image-2021-07-02-08-47-25-560.png!
> Is there some way to do so? It is very annoying to have the source tree full
> of useless errors related to text blocks, when everything compiles and runs
> fine. The project's source level is set to 15 and Maven support shall report
> that to {{java.source}}. Any help welcomed.
--
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-4998) Annotation processor completions not displayed in VSCode
[
https://issues.apache.org/jira/browse/NETBEANS-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-4998.
-
Resolution: Fixed
I guess this has already been fixed for 12.6 or earlier.
> Annotation processor completions not displayed in VSCode
>
>
> Key: NETBEANS-4998
> URL: https://issues.apache.org/jira/browse/NETBEANS-4998
> Project: NetBeans
> Issue Type: Bug
> Components: vscode
>Affects Versions: 12.2
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Minor
>
> The VSCode doesn't display hints from annotation processors. To reproduce
> clone:
> {code:java}
> https://github.com/jtulach/netbeans-html4j {code}
> and checkout revision
> {code:java}
> eb1841800ae16782b781a60bda4a23593502ae60 {code}
> after building the gradle (please use JDK11) -
> {code:java}
> $ JAVA_HOME=/jdk-11 ./gradlew assemble
> {code}
> you can open {{TicTacToe1.java}} and go to line 37, after second {{{}} there
> should be a CC:
> {code:java}
> {|shows list of parameters}{code}
> This seems to work in NetBeans 12.2, but not in VSCode.
--
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-5896) Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
[
https://issues.apache.org/jira/browse/NETBEANS-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17488840#comment-17488840
]
Jaroslav Tulach commented on NETBEANS-5896:
---
{quote}What's the latest long-term plan for nb-javac vs. vanilla javac?
{quote}
The ultimate plan is described at a [dedicated wiki
page|https://cwiki.apache.org/confluence/display/NETBEANS/Overview:+nb-javac].
> Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
> ---
>
> Key: NETBEANS-5896
> URL: https://issues.apache.org/jira/browse/NETBEANS-5896
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.4
> Environment: Java 11.0.11 on Windows 10 on NetBeans 12.4 with vanilla
> javac (nb-javac _not_ installed)
>Reporter: Eirik Bakke
>Assignee: Jan Lahoda
>Priority: Major
>
> Working with Compile-on-Save enabled on a Maven-based NetBeans Platform
> project, with vanilla javac (nb-javac _not_ installed), I frequently get the
> following stack trace:
> {noformat}
> java.lang.NoSuchMethodException:
> com.sun.tools.javac.comp.Enter.unenter(com.sun.tools.javac.tree.JCTree$JCCompilationUnit,
> com.sun.tools.javac.tree.JCTree)
> at java.base/java.lang.Class.getDeclaredMethod(Class.java:2475)
> at
> org.netbeans.api.java.source.TreeUtilities.unenter(TreeUtilities.java:927)
> at
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:916)
> at
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:845)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:502)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:477)
> at
> org.netbeans.modules.java.source.parsing.MimeTask.run(MimeTask.java:60)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
> at
> org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
> at
> org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
> at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
> at
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:431)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.resolve(DeclarativeHintsParser.java:477)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.access$000(DeclarativeHintsParser.java:83)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseCondition(DeclarativeHintsParser.java:311)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseConditions(DeclarativeHintsParser.java:258)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseRule(DeclarativeHintsParser.java:215)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseInput(DeclarativeHintsParser.java:184)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.access$200(DeclarativeHintsParser.java:90)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.parse(DeclarativeHintsParser.java:395)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHints(DeclarativeHintRegistry.java:263)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHintFile(DeclarativeHintRegistry.java:239)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.readHints(DeclarativeHintRegistry.java:128)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.computeHints(DeclarativeHintRegistry.java:111)
> at
>
[jira] [Resolved] (NETBEANS-6384) Detect another Java support ext and recommend to Disable one
[
https://issues.apache.org/jira/browse/NETBEANS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-6384.
---
Resolution: Fixed
[PR-3510|https://github.com/apache/netbeans/pull/3510] has been integrated and
will be available in 13.0.0 version of the Apache NetBeans Language Server
extension.
> Detect another Java support ext and recommend to Disable one
>
>
> Key: NETBEANS-6384
> URL: https://issues.apache.org/jira/browse/NETBEANS-6384
> Project: NetBeans
> Issue Type: Task
> Components: vscode
>Affects Versions: 12.5
>Reporter: Martin Balin
>Assignee: Jaroslav Tulach
>Priority: Major
> Labels: pull-request-available
> Fix For: NB13
>
> Attachments: Screenshot 2022-01-25 at 11.59.09.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> VSNetBeans currently detects installation of MS Java ext pack and informs
> user it disables some services of it, code lenses and code completion.
> See
> [https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
> {code:javascript}
> conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
> disablingFailed);
> conf.update('java.debug.settings.enableRunDebugCodeLens', false,
> false).then(() => {}, disablingFailed);
> {code}
> This behaviour should change to better coexist with MS Java ext.
> VSNetBeans needs to show user a dialog recommending to Enable per workspace
> one of the Java ext packs. Looking at VSCode API it seems there is still
> missing API to DISABLE extension programatically, while there is
> [uninstallExtension|https://code.visualstudio.com/api/references/commands]
> command?
> Proposed solution is not perfect:
> VSNetBeans will show dialog with text like: _Another Java support extension
> is already installed. It is recommended to use only one Java support per
> workspace. Please Disable one of Java ext for workspace._ *OK* button to open
> Extensions panel and user has to do it UX is TBD.
> Some context info:
> VSCode plans to stop recommend extensions see
> [https://github.com/microsoft/vscode/issues/136301] in Feb.
> And they are also working on extension sets per workspace
> [https://github.com/microsoft/vscode/issues/40239]
--
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-6384) Detect another Java support ext and recommend to Disable one
[
https://issues.apache.org/jira/browse/NETBEANS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-6384:
--
Description:
VSNetBeans currently detects installation of MS Java ext pack and informs user
it disables some services of it, code lenses and code completion.
See
[https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
{code:javascript}
conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
disablingFailed);
conf.update('java.debug.settings.enableRunDebugCodeLens', false, false).then(()
=> {}, disablingFailed);
{code}
This behaviour should change to better coexist with MS Java ext.
VSNetBeans needs to show user a dialog recommending to Enable per workspace one
of the Java ext packs. Looking at VSCode API it seems there is still missing
API to DISABLE extension programatically, while there is
[uninstallExtension|https://code.visualstudio.com/api/references/commands]
command?
Proposed solution is not perfect:
VSNetBeans will show dialog with text like: _Another Java support extension is
already installed. It is recommended to use only one Java support per
workspace. Please Disable one of Java ext for workspace._ *OK* button to open
Extensions panel and user has to do it UX is TBD.
Some context info:
VSCode plans to stop recommend extensions see
[https://github.com/microsoft/vscode/issues/136301] in Feb.
And they are also working on extension sets per workspace
[https://github.com/microsoft/vscode/issues/40239]
was:
VSNetBeans currently detects installation of MS Java ext pack and informs user
it will disable some services of it, code lenses and code completion.
See
[https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
{code:javascript}
conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
disablingFailed);
conf.update('java.debug.settings.enableRunDebugCodeLens', false, false).then(()
=> {}, disablingFailed);
{code}
This behaviour should change to better coexist with MS Java ext.
VSNetBeans needs to show user a dialog recommending to Enable per workspace one
of the Java ext packs. Looking at VSCode API it seems there is still missing
API to DISABLE extension programatically, while there is
[uninstallExtension|https://code.visualstudio.com/api/references/commands]
command?
Proposed solution is not perfect:
VSNetBeans will show dialog with text like: _Another Java support extension is
already installed. It is recommended to use only one Java support per
workspace. Please Disable one of Java ext for workspace._ *OK* button to open
Extensions panel and user has to do it UX is TBD.
Some context info:
VSCode plans to stop recommend extensions see
[https://github.com/microsoft/vscode/issues/136301] in Feb.
And they are also working on extension sets per workspace
[https://github.com/microsoft/vscode/issues/40239]
> Detect another Java support ext and recommend to Disable one
>
>
> Key: NETBEANS-6384
> URL: https://issues.apache.org/jira/browse/NETBEANS-6384
> Project: NetBeans
> Issue Type: Task
> Components: vscode
>Affects Versions: 12.5
>Reporter: Martin Balin
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: NB13
>
> Attachments: Screenshot 2022-01-25 at 11.59.09.png
>
>
> VSNetBeans currently detects installation of MS Java ext pack and informs
> user it disables some services of it, code lenses and code completion.
> See
> [https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
> {code:javascript}
> conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
> disablingFailed);
> conf.update('java.debug.settings.enableRunDebugCodeLens', false,
> false).then(() => {}, disablingFailed);
> {code}
> This behaviour should change to better coexist with MS Java ext.
> VSNetBeans needs to show user a dialog recommending to Enable per workspace
> one of the Java ext packs. Looking at VSCode API it seems there is still
> missing API to DISABLE extension programatically, while there is
> [uninstallExtension|https://code.visualstudio.com/api/references/commands]
> command?
> Proposed solution is not perfect:
> VSNetBeans will show dialog with text like: _Another Java support extension
> is already installed. It is recommended to use only one Java support per
> workspace. Please Disable one of Java ext for workspace._ *OK* button to open
> Extensions panel and user has to do it UX is TBD.
> Some context info:
> VSCode plans to stop recommend extensions see
> [https://github.com/microsoft/vscode/issues/136301] in Feb.
> And they are also working on extension sets per
[jira] [Commented] (NETBEANS-6384) Detect another Java support ext and recommend to Disable one
[
https://issues.apache.org/jira/browse/NETBEANS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17481750#comment-17481750
]
Jaroslav Tulach commented on NETBEANS-6384:
---
Dušane, what do you think about {{command 'java.clean.workspace' already
exists}}?
> Detect another Java support ext and recommend to Disable one
>
>
> Key: NETBEANS-6384
> URL: https://issues.apache.org/jira/browse/NETBEANS-6384
> Project: NetBeans
> Issue Type: Task
> Components: vscode
>Affects Versions: 12.5
>Reporter: Martin Balin
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: NB13
>
> Attachments: Screenshot 2022-01-25 at 11.59.09.png
>
>
> VSNetBeans currently detects installation of MS Java ext pack and informs
> user it will disable some services of it, code lenses and code completion.
> See
> [https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
> {code:javascript}
> conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
> disablingFailed);
> conf.update('java.debug.settings.enableRunDebugCodeLens', false,
> false).then(() => {}, disablingFailed);
> {code}
> This behaviour should change to better coexist with MS Java ext.
> VSNetBeans needs to show user a dialog recommending to Enable per workspace
> one of the Java ext packs. Looking at VSCode API it seems there is still
> missing API to DISABLE extension programatically, while there is
> [uninstallExtension|https://code.visualstudio.com/api/references/commands]
> command?
> Proposed solution is not perfect:
> VSNetBeans will show dialog with text like: _Another Java support extension
> is already installed. It is recommended to use only one Java support per
> workspace. Please Disable one of Java ext for workspace._ *OK* button to open
> Extensions panel and user has to do it UX is TBD.
> Some context info:
> VSCode plans to stop recommend extensions see
> [https://github.com/microsoft/vscode/issues/136301] in Feb.
> And they are also working on extension sets per workspace
> [https://github.com/microsoft/vscode/issues/40239]
--
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-6384) Detect another Java support ext and recommend to Disable one
[
https://issues.apache.org/jira/browse/NETBEANS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474644#comment-17474644
]
Jaroslav Tulach edited comment on NETBEANS-6384 at 1/25/22, 11:25 AM:
--
Code is at
[https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions
|https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions]
the newly rebuilt sample extension is [available as
well|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/838/]
was (Author: jtulach):
Code is at
[https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions
|https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions]
sample extension is [available as
well|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/808/]
> Detect another Java support ext and recommend to Disable one
>
>
> Key: NETBEANS-6384
> URL: https://issues.apache.org/jira/browse/NETBEANS-6384
> Project: NetBeans
> Issue Type: Task
> Components: vscode
>Affects Versions: 12.5
>Reporter: Martin Balin
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: NB13
>
> Attachments: Screenshot 2022-01-25 at 11.59.09.png
>
>
> VSNetBeans currently detects installation of MS Java ext pack and informs
> user it will disable some services of it, code lenses and code completion.
> See
> [https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
> {code:javascript}
> conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
> disablingFailed);
> conf.update('java.debug.settings.enableRunDebugCodeLens', false,
> false).then(() => {}, disablingFailed);
> {code}
> This behaviour should change to better coexist with MS Java ext.
> VSNetBeans needs to show user a dialog recommending to Enable per workspace
> one of the Java ext packs. Looking at VSCode API it seems there is still
> missing API to DISABLE extension programatically, while there is
> [uninstallExtension|https://code.visualstudio.com/api/references/commands]
> command?
> Proposed solution is not perfect:
> VSNetBeans will show dialog with text like: _Another Java support extension
> is already installed. It is recommended to use only one Java support per
> workspace. Please Disable one of Java ext for workspace._ *OK* button to open
> Extensions panel and user has to do it UX is TBD.
> Some context info:
> VSCode plans to stop recommend extensions see
> [https://github.com/microsoft/vscode/issues/136301] in Feb.
> And they are also working on extension sets per workspace
> [https://github.com/microsoft/vscode/issues/40239]
--
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-6384) Detect another Java support ext and recommend to Disable one
[
https://issues.apache.org/jira/browse/NETBEANS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474644#comment-17474644
]
Jaroslav Tulach edited comment on NETBEANS-6384 at 1/12/22, 3:57 PM:
-
Code is at
[https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions
|https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions]
sample extension is [available as
well|https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/808/]
was (Author: jtulach):
Code is at
https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions
> Detect another Java support ext and recommend to Disable one
>
>
> Key: NETBEANS-6384
> URL: https://issues.apache.org/jira/browse/NETBEANS-6384
> Project: NetBeans
> Issue Type: Task
> Components: vscode
>Affects Versions: 12.5
>Reporter: Martin Balin
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: 13.0
>
>
> VSNetBeans currently detects installation of MS Java ext pack and informs
> user it will disable some services of it, code lenses and code completion.
> See
> [https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
> {code:javascript}
> conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
> disablingFailed);
> conf.update('java.debug.settings.enableRunDebugCodeLens', false,
> false).then(() => {}, disablingFailed);
> {code}
> This behaviour should change to better coexist with MS Java ext.
> VSNetBeans needs to show user a dialog recommending to Enable per workspace
> one of the Java ext packs. Looking at VSCode API it seems there is still
> missing API to DISABLE extension programatically, while there is
> [uninstallExtension|https://code.visualstudio.com/api/references/commands]
> command?
> Proposed solution is not perfect:
> VSNetBeans will show dialog with text like: _Another Java support extension
> is already installed. It is recommended to use only one Java support per
> workspace. Please Disable one of Java ext for workspace._ *OK* button to open
> Extensions panel and user has to do it UX is TBD.
> Some context info:
> VSCode plans to stop recommend extensions see
> [https://github.com/microsoft/vscode/issues/136301] in Feb.
> And they are also working on extension sets per workspace
> [https://github.com/microsoft/vscode/issues/40239]
--
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-6384) Detect another Java support ext and recommend to Disable one
[
https://issues.apache.org/jira/browse/NETBEANS-6384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474644#comment-17474644
]
Jaroslav Tulach commented on NETBEANS-6384:
---
Code is at
https://github.com/apache/netbeans/compare/master...JaroslavTulach:jtulach/DetectMultipleJavaExtensions
> Detect another Java support ext and recommend to Disable one
>
>
> Key: NETBEANS-6384
> URL: https://issues.apache.org/jira/browse/NETBEANS-6384
> Project: NetBeans
> Issue Type: Task
> Components: vscode
>Affects Versions: 12.5
>Reporter: Martin Balin
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: 13.0
>
>
> VSNetBeans currently detects installation of MS Java ext pack and informs
> user it will disable some services of it, code lenses and code completion.
> See
> [https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/src/extension.ts#L284]
> {code:javascript}
> conf.update('java.test.editor.enableShortcuts', false, false).then(() => {},
> disablingFailed);
> conf.update('java.debug.settings.enableRunDebugCodeLens', false,
> false).then(() => {}, disablingFailed);
> {code}
> This behaviour should change to better coexist with MS Java ext.
> VSNetBeans needs to show user a dialog recommending to Enable per workspace
> one of the Java ext packs. Looking at VSCode API it seems there is still
> missing API to DISABLE extension programatically, while there is
> [uninstallExtension|https://code.visualstudio.com/api/references/commands]
> command?
> Proposed solution is not perfect:
> VSNetBeans will show dialog with text like: _Another Java support extension
> is already installed. It is recommended to use only one Java support per
> workspace. Please Disable one of Java ext for workspace._ *OK* button to open
> Extensions panel and user has to do it UX is TBD.
> Some context info:
> VSCode plans to stop recommend extensions see
> [https://github.com/microsoft/vscode/issues/136301] in Feb.
> And they are also working on extension sets per workspace
> [https://github.com/microsoft/vscode/issues/40239]
--
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-6349) Recent builds of the module responsible for java source parsing break BC to JDK 8
[
https://issues.apache.org/jira/browse/NETBEANS-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-6349.
-
Fix Version/s: 13
Resolution: Fixed
Fixed by https://github.com/apache/netbeans/pull/3418
> Recent builds of the module responsible for java source parsing break BC to
> JDK 8
> -
>
> Key: NETBEANS-6349
> URL: https://issues.apache.org/jira/browse/NETBEANS-6349
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Parsing Indexing
>Affects Versions: 12.5, 12.6
>Reporter: Thomas Schapitz
>Assignee: Jaroslav Tulach
>Priority: Critical
> Fix For: 13
>
>
> There are 6 linked Issues, that all follow a common pattern, pointing to a
> common cause:
> * They are accompanied by an java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> * The users indicate, they are running NB 12.5+ with JDK8
> * The errors occur during parsing.
> Sure enough, JDK 8 hasn't
> java.nio.CharBuffer.flip()Ljava/nio/{*}+CharBuffer+{*},
> it has only java.nio.CharBuffer.flip()Ljava/nio/{+}*Buffer,*{+} which it
> inherits from Buffer.
> Which means: the Module in question has obviously been compiled against a
> library more recent then JDK8, at least JDK9, which has this method.
>
> Consequences:
> This and the 6 linked issues will automatically be fixed with the rollout of
> NB 13, which will require JDK 11 as prerequisite anyway.
> In the mean time, users may work around the problem, by immediately switching
> to JDK 9+ when executing Netbeans. Note that they should still be able to
> develop and build for JDKs 8 an prior.
--
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-6285) Netbeans 12.6 compiles against JDK9+ CharBuffer.flip() and no longer runs on JDK 8
[ https://issues.apache.org/jira/browse/NETBEANS-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach closed NETBEANS-6285. - Fix Version/s: 13 Resolution: Fixed Fixed by https://github.com/apache/netbeans/pull/3418 > Netbeans 12.6 compiles against JDK9+ CharBuffer.flip() and no longer runs on > JDK 8 > -- > > Key: NETBEANS-6285 > URL: https://issues.apache.org/jira/browse/NETBEANS-6285 > Project: NetBeans > Issue Type: Bug > Components: java - Platform >Affects Versions: 12.6 >Reporter: Jean-Marc Borer >Assignee: Jaroslav Tulach >Priority: Blocker > Labels: pull-request-available > Fix For: 13 > > Attachments: messages.log > > Time Spent: 1h 20m > Remaining Estimate: 0h > > After a full fresh install of NB12.6 and trying to run with Azul Open JDK 1.8 > 312, there are several ClassNotFoundExceptions in the logs. It seems that NB > looks for missing methods that make NB not longer properly. For example, it > is no longer possible to properly format Java sources files due to a > java/nio/CharBuffer method missing. > Is NB platform supposed to no longer work with Java 8? -- 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-6349) Recent builds of the module responsible for java source parsing break BC to JDK 8
[
https://issues.apache.org/jira/browse/NETBEANS-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469742#comment-17469742
]
Jaroslav Tulach edited comment on NETBEANS-6349 at 1/6/22, 7:23 AM:
The problem with CharBuffer.flip() can easily be fixed by downcasting to
{{Buffer}} first like:
{code:java}
netbeans$ git diff
diff --git
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
index dcc5c286ad24..1208cf76dbb5 100644
---
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
+++
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
@@ -44,6 +44,7 @@ import java.net.URI;
import java.net.URISyntaxException;
import java.net.URL;
import java.net.URLEncoder;
+import java.nio.Buffer;
import java.nio.CharBuffer;
import java.nio.channels.CompletionHandler;
import java.nio.charset.Charset;
@@ -513,7 +514,9 @@ public class FileObjects {
return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
CharBuffer.wrap( content ) );
}
else {
- return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
(CharBuffer)CharBuffer.allocate( length + 1 ).append( content ).append( ' '
).flip() );
+ Buffer buf = CharBuffer.allocate( length + 1 ).append( content
).append( ' ' );
+ CharBuffer flipped = (CharBuffer) buf.flip();
+ return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
flipped);
}
}
{code}
feel free to apply the fix where needed. Thank you.
was (Author: jtulach):
The problem with {{CharBuffer.flip() }}can easily be fixed with:
{code:java}
netbeans$ git diff
diff --git
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
index dcc5c286ad24..1208cf76dbb5 100644
---
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
+++
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
@@ -44,6 +44,7 @@ import java.net.URI;
import java.net.URISyntaxException;
import java.net.URL;
import java.net.URLEncoder;
+import java.nio.Buffer;
import java.nio.CharBuffer;
import java.nio.channels.CompletionHandler;
import java.nio.charset.Charset;
@@ -513,7 +514,9 @@ public class FileObjects {
return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
CharBuffer.wrap( content ) );
}
else {
- return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
(CharBuffer)CharBuffer.allocate( length + 1 ).append( content ).append( ' '
).flip() );
+ Buffer buf = CharBuffer.allocate( length + 1 ).append( content
).append( ' ' );
+ CharBuffer flipped = (CharBuffer) buf.flip();
+ return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
flipped);
}
}
{code}
feel free to apply the fix where needed. Thank you.
> Recent builds of the module responsible for java source parsing break BC to
> JDK 8
> -
>
> Key: NETBEANS-6349
> URL: https://issues.apache.org/jira/browse/NETBEANS-6349
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Parsing Indexing
>Affects Versions: 12.5, 12.6
>Reporter: Thomas Schapitz
>Assignee: Jaroslav Tulach
>Priority: Critical
>
> There are 6 linked Issues, that all follow a common pattern, pointing to a
> common cause:
> * They are accompanied by an java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> * The users indicate, they are running NB 12.5+ with JDK8
> * The errors occur during parsing.
> Sure enough, JDK 8 hasn't
> java.nio.CharBuffer.flip()Ljava/nio/{*}+CharBuffer+{*},
> it has only java.nio.CharBuffer.flip()Ljava/nio/{+}*Buffer,*{+} which it
> inherits from Buffer.
> Which means: the Module in question has obviously been compiled against a
> library more recent then JDK8, at least JDK9, which has this method.
>
> Consequences:
> This and the 6 linked issues will automatically be fixed with the rollout of
> NB 13, which will require JDK 11 as prerequisite anyway.
> In the mean time, users may work around the problem, by immediately switching
> to JDK 9+ when executing Netbeans. Note that they should still be able to
> develop and build for JDKs 8 an prior.
--
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:
[jira] [Comment Edited] (NETBEANS-6349) Recent builds of the module responsible for java source parsing break BC to JDK 8
[
https://issues.apache.org/jira/browse/NETBEANS-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469742#comment-17469742
]
Jaroslav Tulach edited comment on NETBEANS-6349 at 1/6/22, 7:22 AM:
The problem with {{CharBuffer.flip() }}can easily be fixed with:
{code:java}
netbeans$ git diff
diff --git
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
index dcc5c286ad24..1208cf76dbb5 100644
---
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
+++
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
@@ -44,6 +44,7 @@ import java.net.URI;
import java.net.URISyntaxException;
import java.net.URL;
import java.net.URLEncoder;
+import java.nio.Buffer;
import java.nio.CharBuffer;
import java.nio.channels.CompletionHandler;
import java.nio.charset.Charset;
@@ -513,7 +514,9 @@ public class FileObjects {
return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
CharBuffer.wrap( content ) );
}
else {
- return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
(CharBuffer)CharBuffer.allocate( length + 1 ).append( content ).append( ' '
).flip() );
+ Buffer buf = CharBuffer.allocate( length + 1 ).append( content
).append( ' ' );
+ CharBuffer flipped = (CharBuffer) buf.flip();
+ return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
flipped);
}
}
{code}
feel free to apply the fix where needed. Thank you.
was (Author: jtulach):
The problem with \{{CharBuffer.flip()} can easily be fixed with:
{code:java}
netbeans$ git diff
diff --git
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
index dcc5c286ad24..1208cf76dbb5 100644
---
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
+++
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
@@ -44,6 +44,7 @@ import java.net.URI;
import java.net.URISyntaxException;
import java.net.URL;
import java.net.URLEncoder;
+import java.nio.Buffer;
import java.nio.CharBuffer;
import java.nio.channels.CompletionHandler;
import java.nio.charset.Charset;
@@ -513,7 +514,9 @@ public class FileObjects {
return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
CharBuffer.wrap( content ) );
}
else {
- return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
(CharBuffer)CharBuffer.allocate( length + 1 ).append( content ).append( ' '
).flip() );
+ Buffer buf = CharBuffer.allocate( length + 1 ).append( content
).append( ' ' );
+ CharBuffer flipped = (CharBuffer) buf.flip();
+ return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
flipped);
}
}
{code}
feel free to apply the fix where needed. Thank you.
> Recent builds of the module responsible for java source parsing break BC to
> JDK 8
> -
>
> Key: NETBEANS-6349
> URL: https://issues.apache.org/jira/browse/NETBEANS-6349
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Parsing Indexing
>Affects Versions: 12.5, 12.6
>Reporter: Thomas Schapitz
>Assignee: Jaroslav Tulach
>Priority: Critical
>
> There are 6 linked Issues, that all follow a common pattern, pointing to a
> common cause:
> * They are accompanied by an java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> * The users indicate, they are running NB 12.5+ with JDK8
> * The errors occur during parsing.
> Sure enough, JDK 8 hasn't
> java.nio.CharBuffer.flip()Ljava/nio/{*}+CharBuffer+{*},
> it has only java.nio.CharBuffer.flip()Ljava/nio/{+}*Buffer,*{+} which it
> inherits from Buffer.
> Which means: the Module in question has obviously been compiled against a
> library more recent then JDK8, at least JDK9, which has this method.
>
> Consequences:
> This and the 6 linked issues will automatically be fixed with the rollout of
> NB 13, which will require JDK 11 as prerequisite anyway.
> In the mean time, users may work around the problem, by immediately switching
> to JDK 9+ when executing Netbeans. Note that they should still be able to
> develop and build for JDKs 8 an prior.
--
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
[jira] [Commented] (NETBEANS-6349) Recent builds of the module responsible for java source parsing break BC to JDK 8
[
https://issues.apache.org/jira/browse/NETBEANS-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469742#comment-17469742
]
Jaroslav Tulach commented on NETBEANS-6349:
---
The problem with \{{CharBuffer.flip()} can easily be fixed with:
{code:java}
netbeans$ git diff
diff --git
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
index dcc5c286ad24..1208cf76dbb5 100644
---
a/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
+++
b/java/java.source.base/src/org/netbeans/modules/java/source/parsing/FileObjects.java
@@ -44,6 +44,7 @@ import java.net.URI;
import java.net.URISyntaxException;
import java.net.URL;
import java.net.URLEncoder;
+import java.nio.Buffer;
import java.nio.CharBuffer;
import java.nio.channels.CompletionHandler;
import java.nio.charset.Charset;
@@ -513,7 +514,9 @@ public class FileObjects {
return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
CharBuffer.wrap( content ) );
}
else {
- return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
(CharBuffer)CharBuffer.allocate( length + 1 ).append( content ).append( ' '
).flip() );
+ Buffer buf = CharBuffer.allocate( length + 1 ).append( content
).append( ' ' );
+ CharBuffer flipped = (CharBuffer) buf.flip();
+ return new MemoryFileObject(pkgStr, nameStr, uri, lastModified,
flipped);
}
}
{code}
feel free to apply the fix where needed. Thank you.
> Recent builds of the module responsible for java source parsing break BC to
> JDK 8
> -
>
> Key: NETBEANS-6349
> URL: https://issues.apache.org/jira/browse/NETBEANS-6349
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Parsing Indexing
>Affects Versions: 12.5, 12.6
>Reporter: Thomas Schapitz
>Assignee: Jaroslav Tulach
>Priority: Critical
>
> There are 6 linked Issues, that all follow a common pattern, pointing to a
> common cause:
> * They are accompanied by an java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> * The users indicate, they are running NB 12.5+ with JDK8
> * The errors occur during parsing.
> Sure enough, JDK 8 hasn't
> java.nio.CharBuffer.flip()Ljava/nio/{*}+CharBuffer+{*},
> it has only java.nio.CharBuffer.flip()Ljava/nio/{+}*Buffer,*{+} which it
> inherits from Buffer.
> Which means: the Module in question has obviously been compiled against a
> library more recent then JDK8, at least JDK9, which has this method.
>
> Consequences:
> This and the 6 linked issues will automatically be fixed with the rollout of
> NB 13, which will require JDK 11 as prerequisite anyway.
> In the mean time, users may work around the problem, by immediately switching
> to JDK 9+ when executing Netbeans. Note that they should still be able to
> develop and build for JDKs 8 an prior.
--
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-6285) Netbeans 12.6 compiles against JDK9+ CharBuffer.flip() and no longer runs on JDK 8
[ https://issues.apache.org/jira/browse/NETBEANS-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-6285: -- Summary: Netbeans 12.6 compiles against JDK9+ CharBuffer.flip() and no longer runs on JDK 8 (was: Netbeans 12.6 seems no properly run on JDK 8) > Netbeans 12.6 compiles against JDK9+ CharBuffer.flip() and no longer runs on > JDK 8 > -- > > Key: NETBEANS-6285 > URL: https://issues.apache.org/jira/browse/NETBEANS-6285 > Project: NetBeans > Issue Type: Bug > Components: java - Platform >Affects Versions: 12.6 >Reporter: Jean-Marc Borer >Assignee: Jaroslav Tulach >Priority: Major > Attachments: messages.log > > > After a full fresh install of NB12.6 and trying to run with Azul Open JDK 1.8 > 312, there are several ClassNotFoundExceptions in the logs. It seems that NB > looks for missing methods that make NB not longer properly. For example, it > is no longer possible to properly format Java sources files due to a > java/nio/CharBuffer method missing. > Is NB platform supposed to no longer work with Java 8? -- 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-6285) Netbeans 12.6 compiles against JDK9+ CharBuffer.flip() and no longer runs on JDK 8
[ https://issues.apache.org/jira/browse/NETBEANS-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-6285: -- Priority: Blocker (was: Major) > Netbeans 12.6 compiles against JDK9+ CharBuffer.flip() and no longer runs on > JDK 8 > -- > > Key: NETBEANS-6285 > URL: https://issues.apache.org/jira/browse/NETBEANS-6285 > Project: NetBeans > Issue Type: Bug > Components: java - Platform >Affects Versions: 12.6 >Reporter: Jean-Marc Borer >Assignee: Jaroslav Tulach >Priority: Blocker > Attachments: messages.log > > > After a full fresh install of NB12.6 and trying to run with Azul Open JDK 1.8 > 312, there are several ClassNotFoundExceptions in the logs. It seems that NB > looks for missing methods that make NB not longer properly. For example, it > is no longer possible to properly format Java sources files due to a > java/nio/CharBuffer method missing. > Is NB platform supposed to no longer work with Java 8? -- 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-6272) Auto-indent function or pressing tab character in java editor throws NoSuchMethodError
[
https://issues.apache.org/jira/browse/NETBEANS-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-6272.
-
Resolution: Duplicate
The same problem as NETBEANS-6285:
{code:java}
java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
at org.netbeans.modules.java.source.parsing{code}
> Auto-indent function or pressing tab character in java editor throws
> NoSuchMethodError
> --
>
> Key: NETBEANS-6272
> URL: https://issues.apache.org/jira/browse/NETBEANS-6272
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Formatting Indentation
>Affects Versions: 12.6
>Reporter: Petr Miksik
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: ide.log, java_source.png, netbeans-enter-error.gif,
> ui.log
>
>
> When running NetBeans under JDK 1.8, the auto-indentation or inserting a tab
> character on a new line throws a NoSuchMethodError, if the source file is
> managed by a versioning system (see the attached picture). Running NetBeans
> under JDK 11 or higher is OK.
--
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] [Assigned] (NETBEANS-6272) Auto-indent function or pressing tab character in java editor throws NoSuchMethodError
[ https://issues.apache.org/jira/browse/NETBEANS-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-6272: - Assignee: Jaroslav Tulach > Auto-indent function or pressing tab character in java editor throws > NoSuchMethodError > -- > > Key: NETBEANS-6272 > URL: https://issues.apache.org/jira/browse/NETBEANS-6272 > Project: NetBeans > Issue Type: Bug > Components: editor - Formatting Indentation >Affects Versions: 12.6 >Reporter: Petr Miksik >Assignee: Jaroslav Tulach >Priority: Major > Attachments: ide.log, java_source.png, netbeans-enter-error.gif, > ui.log > > > When running NetBeans under JDK 1.8, the auto-indentation or inserting a tab > character on a new line throws a NoSuchMethodError, if the source file is > managed by a versioning system (see the attached picture). Running NetBeans > under JDK 11 or higher is OK. -- 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-6182) Implement abstract methods -> java.lang.NoSuchMethodError
[
https://issues.apache.org/jira/browse/NETBEANS-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-6182.
-
Resolution: Duplicate
The same problem as NETBEANS-6285:
{code:java}
java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
at org.netbeans.modules.java.source.parsing{code}
> Implement abstract methods -> java.lang.NoSuchMethodError
> -
>
> Key: NETBEANS-6182
> URL: https://issues.apache.org/jira/browse/NETBEANS-6182
> Project: NetBeans
> Issue Type: Bug
> Components: java - Editor, java - Hints
>Affects Versions: 12.5
>Reporter: Bartosz Tomasik
>Assignee: Jaroslav Tulach
>Priority: Major
>
> *Product Version:* Apache NetBeans IDE 12.5
> *Java:* 1.8.0_292; OpenJDK 64-Bit Server VM 25.292-b10
> *Runtime:* OpenJDK Runtime Environment 1.8.0_292-8u292-b10-0ubuntu1~20.04-b10
>
> I'm unable to use `implement abstract methods` hint - it throws:
>
> {quote}SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
> org.netbeans.modules.editor.hints.HintsUI$1
> java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> at
> org.netbeans.modules.java.source.parsing.FileObjects.memoryFileObject(FileObjects.java:516)
> at
> org.netbeans.modules.java.source.parsing.FileObjects.memoryFileObject(FileObjects.java:490)
> at
> org.netbeans.modules.java.source.save.Reformatter.reformat(Reformatter.java:114)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.printAnnotationsFormatted(VeryPretty.java:2747)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.printAnnotations(VeryPretty.java:2766)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.visitMethodDef(VeryPretty.java:985)
> at com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:908)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.doAccept(VeryPretty.java:421)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.print(VeryPretty.java:283)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffList(CasualDiff.java:4259)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffClassDef(CasualDiff.java:1102)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl0(CasualDiff.java:5549)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl(CasualDiff.java:5443)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5370)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5341)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffList(CasualDiff.java:4176)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTopLevel(CasualDiff.java:594)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl0(CasualDiff.java:5522)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl(CasualDiff.java:5443)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5370)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5353)
> at org.netbeans.modules.java.source.save.CasualDiff.diff(CasualDiff.java:350)
> at
> org.netbeans.api.java.source.WorkingCopy.processCurrentCompilationUnit(WorkingCopy.java:920)
> at org.netbeans.api.java.source.WorkingCopy.getChanges(WorkingCopy.java:1332)
> at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:676)
> at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:663)
> at org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:502)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
> at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
> at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:452)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
> at
>
[jira] [Closed] (NETBEANS-6064) java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()
[
https://issues.apache.org/jira/browse/NETBEANS-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach closed NETBEANS-6064.
-
Resolution: Duplicate
The same problem as NETBEANS-6285:
{code:java}
java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
at org.netbeans.modules.java.source.parsing{code}
> java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()
> ---
>
> Key: NETBEANS-6064
> URL: https://issues.apache.org/jira/browse/NETBEANS-6064
> Project: NetBeans
> Issue Type: Bug
> Components: cnd - Other
>Affects Versions: 12.5
>Reporter: Randy Nieuwenburg
>Assignee: Jaroslav Tulach
>Priority: Major
>
>
> 2021-09-25T12:33:46
> 1632587626910
> 1198
> org.netbeans.ui.actions.editor
> 500
> 29
> UI_ACTION_EDITOR
> UI_ACTION_EDITOR
> null
>
> java.awt.event.ActionEvent[ACTION_PERFORMED,cmd=ENTER,when=1632587626903,modifiers=]
> on
> org.openide.text.QuietEditorPane[,0,0,1020x4951,layout=javax.swing.plaf.basic.BasicTextUI$UpdateHandler,alignmentX=0.0,alignmentY=0.0,border=javax.swing.plaf.basic.BasicBorders$MarginBorder@1e723e6d,flags=296,maximumSize=,minimumSize=,preferredSize=,caretColor=java.awt.Color[r=0,g=0,b=0],disabledTextColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],editable=true,margin=java.awt.Insets[top=0,left=0,bottom=0,right=0],selectedTextColor=sun.swing.PrintColorUIResource[r=51,g=51,b=51],selectionColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],kit=org.netbeans.modules.editor.java.JavaKit@61175c56,typeHandlers=]
>
> java.awt.event.ActionEvent[ACTION_PERFORMED,cmd=ENTER,when=1632587626903,modifiers=]
> on
> org.openide.text.QuietEditorPane[,0,0,1020x4951,layout=javax.swing.plaf.basic.BasicTextUI$UpdateHandler,alignmentX=0.0,alignmentY=0.0,border=javax.swing.plaf.basic.BasicBorders$MarginBorder@1e723e6d,flags=296,maximumSize=,minimumSize=,preferredSize=,caretColor=java.awt.Color[r=0,g=0,b=0],disabledTextColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],editable=true,margin=java.awt.Insets[top=0,left=0,bottom=0,right=0],selectedTextColor=sun.swing.PrintColorUIResource[r=51,g=51,b=51],selectionColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],kit=org.netbeans.modules.editor.java.JavaKit@61175c56,typeHandlers=]
> org.netbeans.editor.BaseKit$InsertBreakAction[insert-break]
> org.netbeans.editor.BaseKit$InsertBreakAction@156266e5
> insert-break
>
>
> 2021-09-25T12:33:46
> 1632587626942
> 1200
> global
> 1000
> 29
>
> java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
>
> org.netbeans.modules.java.source.parsing.FileObjects
> memoryFileObject
> 516
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.java.source.parsing.FileObjects
> memoryFileObject
> 490
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.java.source.save.Reindenter
> initRegionData
> 268
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.java.source.save.Reindenter
> reindent
> 121
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.editor.indent.TaskHandler$MimeItem
> runTask
> 548
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.TaskHandler
> runTasks
> 309
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.IndentImpl
> reindent
> 282
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.api.Indent
> reindent
> 146
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.api.Indent
> reindent
> 130
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction
> performLineBreakInsertion
> 1624
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction
> access$400
> 1439
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction$2
> run
> 1529
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.GuardedDocument
> runAtomicAsUser
> 333
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction
> actionPerformed
> 1520
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseAction
> actionPerformed
> 322
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> javax.swing.SwingUtilities
> notifyAction
>
[jira] [Assigned] (NETBEANS-6182) Implement abstract methods -> java.lang.NoSuchMethodError
[
https://issues.apache.org/jira/browse/NETBEANS-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-6182:
-
Assignee: Jaroslav Tulach
> Implement abstract methods -> java.lang.NoSuchMethodError
> -
>
> Key: NETBEANS-6182
> URL: https://issues.apache.org/jira/browse/NETBEANS-6182
> Project: NetBeans
> Issue Type: Bug
> Components: java - Editor, java - Hints
>Affects Versions: 12.5
>Reporter: Bartosz Tomasik
>Assignee: Jaroslav Tulach
>Priority: Major
>
> *Product Version:* Apache NetBeans IDE 12.5
> *Java:* 1.8.0_292; OpenJDK 64-Bit Server VM 25.292-b10
> *Runtime:* OpenJDK Runtime Environment 1.8.0_292-8u292-b10-0ubuntu1~20.04-b10
>
> I'm unable to use `implement abstract methods` hint - it throws:
>
> {quote}SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
> org.netbeans.modules.editor.hints.HintsUI$1
> java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> at
> org.netbeans.modules.java.source.parsing.FileObjects.memoryFileObject(FileObjects.java:516)
> at
> org.netbeans.modules.java.source.parsing.FileObjects.memoryFileObject(FileObjects.java:490)
> at
> org.netbeans.modules.java.source.save.Reformatter.reformat(Reformatter.java:114)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.printAnnotationsFormatted(VeryPretty.java:2747)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.printAnnotations(VeryPretty.java:2766)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.visitMethodDef(VeryPretty.java:985)
> at com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:908)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.doAccept(VeryPretty.java:421)
> at
> org.netbeans.modules.java.source.pretty.VeryPretty.print(VeryPretty.java:283)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffList(CasualDiff.java:4259)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffClassDef(CasualDiff.java:1102)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl0(CasualDiff.java:5549)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl(CasualDiff.java:5443)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5370)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5341)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffList(CasualDiff.java:4176)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTopLevel(CasualDiff.java:594)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl0(CasualDiff.java:5522)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTreeImpl(CasualDiff.java:5443)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5370)
> at
> org.netbeans.modules.java.source.save.CasualDiff.diffTree(CasualDiff.java:5353)
> at org.netbeans.modules.java.source.save.CasualDiff.diff(CasualDiff.java:350)
> at
> org.netbeans.api.java.source.WorkingCopy.processCurrentCompilationUnit(WorkingCopy.java:920)
> at org.netbeans.api.java.source.WorkingCopy.getChanges(WorkingCopy.java:1332)
> at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:676)
> at org.netbeans.api.java.source.JavaSource$1.run(JavaSource.java:663)
> at org.netbeans.api.java.source.JavaSource$MultiTask.run(JavaSource.java:502)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:130)
> at
> org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:114)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
> at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
> at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:452)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
> at
> org.netbeans.api.java.source.JavaSource.runModificationTask(JavaSource.java:684)
> at
>
[jira] [Assigned] (NETBEANS-6064) java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()
[
https://issues.apache.org/jira/browse/NETBEANS-6064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-6064:
-
Assignee: Jaroslav Tulach
> java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()
> ---
>
> Key: NETBEANS-6064
> URL: https://issues.apache.org/jira/browse/NETBEANS-6064
> Project: NetBeans
> Issue Type: Bug
> Components: cnd - Other
>Affects Versions: 12.5
>Reporter: Randy Nieuwenburg
>Assignee: Jaroslav Tulach
>Priority: Major
>
>
> 2021-09-25T12:33:46
> 1632587626910
> 1198
> org.netbeans.ui.actions.editor
> 500
> 29
> UI_ACTION_EDITOR
> UI_ACTION_EDITOR
> null
>
> java.awt.event.ActionEvent[ACTION_PERFORMED,cmd=ENTER,when=1632587626903,modifiers=]
> on
> org.openide.text.QuietEditorPane[,0,0,1020x4951,layout=javax.swing.plaf.basic.BasicTextUI$UpdateHandler,alignmentX=0.0,alignmentY=0.0,border=javax.swing.plaf.basic.BasicBorders$MarginBorder@1e723e6d,flags=296,maximumSize=,minimumSize=,preferredSize=,caretColor=java.awt.Color[r=0,g=0,b=0],disabledTextColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],editable=true,margin=java.awt.Insets[top=0,left=0,bottom=0,right=0],selectedTextColor=sun.swing.PrintColorUIResource[r=51,g=51,b=51],selectionColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],kit=org.netbeans.modules.editor.java.JavaKit@61175c56,typeHandlers=]
>
> java.awt.event.ActionEvent[ACTION_PERFORMED,cmd=ENTER,when=1632587626903,modifiers=]
> on
> org.openide.text.QuietEditorPane[,0,0,1020x4951,layout=javax.swing.plaf.basic.BasicTextUI$UpdateHandler,alignmentX=0.0,alignmentY=0.0,border=javax.swing.plaf.basic.BasicBorders$MarginBorder@1e723e6d,flags=296,maximumSize=,minimumSize=,preferredSize=,caretColor=java.awt.Color[r=0,g=0,b=0],disabledTextColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],editable=true,margin=java.awt.Insets[top=0,left=0,bottom=0,right=0],selectedTextColor=sun.swing.PrintColorUIResource[r=51,g=51,b=51],selectionColor=javax.swing.plaf.ColorUIResource[r=184,g=207,b=229],kit=org.netbeans.modules.editor.java.JavaKit@61175c56,typeHandlers=]
> org.netbeans.editor.BaseKit$InsertBreakAction[insert-break]
> org.netbeans.editor.BaseKit$InsertBreakAction@156266e5
> insert-break
>
>
> 2021-09-25T12:33:46
> 1632587626942
> 1200
> global
> 1000
> 29
>
> java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
>
> org.netbeans.modules.java.source.parsing.FileObjects
> memoryFileObject
> 516
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.java.source.parsing.FileObjects
> memoryFileObject
> 490
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.java.source.save.Reindenter
> initRegionData
> 268
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.java.source.save.Reindenter
> reindent
> 121
> ${netBeansDir}modules/org-netbeans-modules-java-source-base.jar
>
>
> org.netbeans.modules.editor.indent.TaskHandler$MimeItem
> runTask
> 548
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.TaskHandler
> runTasks
> 309
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.IndentImpl
> reindent
> 282
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.api.Indent
> reindent
> 146
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.modules.editor.indent.api.Indent
> reindent
> 130
> ${netBeansDir}modules/org-netbeans-modules-editor-indent.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction
> performLineBreakInsertion
> 1624
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction
> access$400
> 1439
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction$2
> run
> 1529
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.GuardedDocument
> runAtomicAsUser
> 333
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseKit$InsertBreakAction
> actionPerformed
> 1520
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> org.netbeans.editor.BaseAction
> actionPerformed
> 322
> ${netBeansDir}modules/org-netbeans-modules-editor-lib.jar
>
>
> javax.swing.SwingUtilities
> notifyAction
> 1668
> ${java.home}lib/rt.jar
>
>
> javax.swing.JComponent
> processKeyBinding
> 2882
> ${java.home}lib/rt.jar
>
>
> javax.swing.JComponent
>
[jira] [Commented] (NETBEANS-6285) Netbeans 12.6 seems no properly run on JDK 8
[
https://issues.apache.org/jira/browse/NETBEANS-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469687#comment-17469687
]
Jaroslav Tulach commented on NETBEANS-6285:
---
I've just built recent NetBeans:
{code}
netbeans$ git log | head -n 1
commit 76183f342a62d9f0e6732d7b500430d34d813b54
netbeans$ JAVA_HOME=/jdk-11/ ant build
{code}
and then verified whether the classfiles are correct using the
[ValidateClassFilesTest introduced by
PR-2761|https://github.com/apache/netbeans/pull/2761]:
{code}
netbeans$ ant -f platform/o.n.core/ -Dtest.type=qa-functional test-single
-Dtest.includes=**/ValidateClassFilesTest*
{code}
they are - e.g. they all shall have [major classpath version
52|https://stackoverflow.com/questions/9170832/list-of-java-class-file-format-major-version-numbers]
and thus be targetted for JDK8. The same applies to
{{org.netbeans.modules.java.source.parsing.FileObjects}}:
{code}
netbeans$ cd nbbuild
nbbuild$ javap -v -c -cp
netbeans/java/modules/org-netbeans-modules-java-source-base.jar
org/netbeans/modules/java/source/parsing/FileObjects | head -n7
Classfile
jar:file:/netbeans/java/modules/org-netbeans-modules-java-source-base.jar!/org/netbeans/modules/java/source/parsing/FileObjects.class
Last modified 6.1.2022; size 29135 bytes
MD5 checksum 8b8fe1fd32aa92135598fe1947a5c420
Compiled from "FileObjects.java"
public class org.netbeans.modules.java.source.parsing.FileObjects
minor version: 0
major version: 52
{code}
however, there is really a call to {{CharBuffer.flip()}}:
{code}
nbbuild$ javap -c -cp
netbeans/java/modules/org-netbeans-modules-java-source-base.jar
org/netbeans/modules/java/source/parsing/FileObjects | grep flip -C3
132: invokevirtual #75 // Method
java/nio/CharBuffer.append:(Ljava/lang/CharSequence;)Ljava/nio/CharBuffer;
135: bipush32
137: invokevirtual #76 // Method
java/nio/CharBuffer.append:(C)Ljava/nio/CharBuffer;
140: invokevirtual #77 // Method
java/nio/CharBuffer.flip:()Ljava/nio/CharBuffer;
143: invokespecial #73 // Method
org/netbeans/modules/java/source/parsing/FileObjects$MemoryFileObject."":(Ljava/lang/String;Ljava/lang/String;Ljava/net/URI;JLjava/nio/CharBuffer;)V
146: areturn
{code}
this is caused by nb-javac passing bootclasspath option when compiling the
module and thus disabling usage of {{--release}}:
{code}
netbeans$ JAVA_HOME=~/bin/jdk-11 ant -f java/java.source.base/ -v build | grep
-- -X.*bootclasspath
[nb-javac]
'-Xbootclasspath/p:/home/devel/NetBeansProjects/netbeans/java/libs.javacapi/external/nb-javac-jdk-17.0.1-ga-api.jar:/home/devel/NetBeansProjects/netbeans/java/libs.javacapi/external/nb-javac-jdk-17.0.1-ga.jar'
{code}
> Netbeans 12.6 seems no properly run on JDK 8
>
>
> Key: NETBEANS-6285
> URL: https://issues.apache.org/jira/browse/NETBEANS-6285
> Project: NetBeans
> Issue Type: Bug
> Components: java - Platform
>Affects Versions: 12.6
>Reporter: Jean-Marc Borer
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: messages.log
>
>
> After a full fresh install of NB12.6 and trying to run with Azul Open JDK 1.8
> 312, there are several ClassNotFoundExceptions in the logs. It seems that NB
> looks for missing methods that make NB not longer properly. For example, it
> is no longer possible to properly format Java sources files due to a
> java/nio/CharBuffer method missing.
> Is NB platform supposed to no longer work with Java 8?
--
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] [Assigned] (NETBEANS-6285) Netbeans 12.6 seems no properly run on JDK 8
[ https://issues.apache.org/jira/browse/NETBEANS-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-6285: - Assignee: Jaroslav Tulach > Netbeans 12.6 seems no properly run on JDK 8 > > > Key: NETBEANS-6285 > URL: https://issues.apache.org/jira/browse/NETBEANS-6285 > Project: NetBeans > Issue Type: Bug > Components: java - Platform >Affects Versions: 12.6 >Reporter: Jean-Marc Borer >Assignee: Jaroslav Tulach >Priority: Major > Attachments: messages.log > > > After a full fresh install of NB12.6 and trying to run with Azul Open JDK 1.8 > 312, there are several ClassNotFoundExceptions in the logs. It seems that NB > looks for missing methods that make NB not longer properly. For example, it > is no longer possible to properly format Java sources files due to a > java/nio/CharBuffer method missing. > Is NB platform supposed to no longer work with Java 8? -- 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] [Assigned] (NETBEANS-6349) Recent builds of the module responsible for java source parsing break BC to JDK 8
[
https://issues.apache.org/jira/browse/NETBEANS-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-6349:
-
Assignee: Jaroslav Tulach
> Recent builds of the module responsible for java source parsing break BC to
> JDK 8
> -
>
> Key: NETBEANS-6349
> URL: https://issues.apache.org/jira/browse/NETBEANS-6349
> Project: NetBeans
> Issue Type: Bug
> Components: editor - Parsing Indexing
>Affects Versions: 12.5, 12.6
>Reporter: Thomas Schapitz
>Assignee: Jaroslav Tulach
>Priority: Critical
>
> There are 6 linked Issues, that all follow a common pattern, pointing to a
> common cause:
> * They are accompanied by an java.lang.NoSuchMethodError:
> java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
> * The users indicate, they are running NB 12.5+ with JDK8
> * The errors occur during parsing.
> Sure enough, JDK 8 hasn't
> java.nio.CharBuffer.flip()Ljava/nio/{*}+CharBuffer+{*},
> it has only java.nio.CharBuffer.flip()Ljava/nio/{+}*Buffer,*{+} which it
> inherits from Buffer.
> Which means: the Module in question has obviously been compiled against a
> library more recent then JDK8, at least JDK9, which has this method.
>
> Consequences:
> This and the 6 linked issues will automatically be fixed with the rollout of
> NB 13, which will require JDK 11 as prerequisite anyway.
> In the mean time, users may work around the problem, by immediately switching
> to JDK 9+ when executing Netbeans. Note that they should still be able to
> develop and build for JDKs 8 an prior.
--
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] [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
[jira] [Commented] (NETBEANS-6294) FileObject for folder has no presentation Node in its lookup
[
https://issues.apache.org/jira/browse/NETBEANS-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17458973#comment-17458973
]
Jaroslav Tulach commented on NETBEANS-6294:
---
FYI: There also is [non recursive
folder|https://bits.netbeans.org/dev/javadoc/org-netbeans-modules-queries/org/netbeans/api/fileinfo/NonRecursiveFolder.html]
which may be somehow related to the "non-presence" of {{FileObject}} in the
lookup. Anyway I support exposing {{FileObject}} from
{{DataFolder.getLookup()}} and lookup if its node.
> FileObject for folder has no presentation Node in its lookup
>
>
> Key: NETBEANS-6294
> URL: https://issues.apache.org/jira/browse/NETBEANS-6294
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Data Systems
>Affects Versions: 12.5
>Reporter: Svatopluk Dedic
>Priority: Major
> Labels: VSNetBeans
>
> ... and DataFolder (and its Node) does not provide FileObject from its
> Lookup. For details see PR [https://github.com/apache/netbeans/pull/3363] and
> hacked code in
> [https://github.com/apache/netbeans/pull/3363/files#diff-8e1f3f0485b58ff61a67f45673d37af218d3bcbb7501d0754b09edb8c5e4fd27R120]
>
> The bug is there probably from ancient ages, and need to be fixed carefully
> so it does not break *subclasses* of DataFolder or *delegates* to folder node
> that could eventually list the FileObject twice.
--
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-5884) Jackpot doesn't work on JDK 17
[
https://issues.apache.org/jira/browse/NETBEANS-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17450573#comment-17450573
]
Jaroslav Tulach commented on NETBEANS-5884:
---
OracleLabs tried to use new version of Jackpot, but had to revert it:
[https://github.com/graalvm/mx/commit/d5c508e] this is the error:
{code:java}
java.lang.NoSuchMethodException:
com.sun.tools.javac.comp.Enter.unenter(com.sun.tools.javac.tree.JCTree$JCCompilationUnit,
com.sun.tools.javac.tree.JCTree)
at java.base/java.lang.Class.getDeclaredMethod(Class.java:2475)
at
org.netbeans.api.java.source.TreeUtilities.unenter(TreeUtilities.java:927)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:916)
at
org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:845)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:502)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.source.parsing.MimeTask.run(MimeTask.java:60)
at
org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
at
org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
at
org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
at
org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
at
org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
at
org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
at
org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
at
org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
at
org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:431)
at
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.resolve(DeclarativeHintsParser.java:477)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.access$000(DeclarativeHintsParser.java:83)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseCondition(DeclarativeHintsParser.java:311)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseConditions(DeclarativeHintsParser.java:258)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseRule(DeclarativeHintsParser.java:215)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseInput(DeclarativeHintsParser.java:184)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.access$200(DeclarativeHintsParser.java:90)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.parse(DeclarativeHintsParser.java:395)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHints(DeclarativeHintRegistry.java:263)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHintFile(DeclarativeHintRegistry.java:239)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.readHints(DeclarativeHintRegistry.java:128)
at
org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.computeHints(DeclarativeHintRegistry.java:111)
at
org.netbeans.modules.java.hints.spiimpl.RulesManagerImpl.readHints(RulesManagerImpl.java:139)
at org.netbeans.modules.jackpot30.cmdline.Main.readHints(Main.java:801)
at
org.netbeans.modules.jackpot30.cmdline.Main.handleGroup(Main.java:460)
at org.netbeans.modules.jackpot30.cmdline.Main.compile(Main.java:340)
at org.netbeans.modules.jackpot30.cmdline.Main.main(Main.java:136)
{code}
> Jackpot doesn't work on JDK 17
> --
>
> Key: NETBEANS-5884
> URL: https://issues.apache.org/jira/browse/NETBEANS-5884
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Major
>
> {code:java}
> java.lang.NoSuchMethodError: 'void
> com.sun.tools.javac.util.Log.(com.sun.tools.javac.util.Context,
>
[jira] [Commented] (NETBEANS-2842) Using of deprecated pack200 tool in nbm packaging
[ https://issues.apache.org/jira/browse/NETBEANS-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446951#comment-17446951 ] Jaroslav Tulach commented on NETBEANS-2842: --- The original NetBeans 8.1 [^nbpython.zip] NBMs are packed with pack200. > Using of deprecated pack200 tool in nbm packaging > - > > Key: NETBEANS-2842 > URL: https://issues.apache.org/jira/browse/NETBEANS-2842 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager >Affects Versions: 11.3 >Reporter: Benjamin Graf >Priority: Critical > Attachments: nbpython.zip, unpack200 failure.png > > > Netbeans plugins are mostly compressed in size by the JDK internal pack200 > tool which is deprecated since JDK 11 ([https://openjdk.java.net/jeps/336]). > It should be thought about an alternative as it might get removed in next JDK > releases. -- 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-2842) Using of deprecated pack200 tool in nbm packaging
[ https://issues.apache.org/jira/browse/NETBEANS-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-2842: -- Attachment: nbpython.zip > Using of deprecated pack200 tool in nbm packaging > - > > Key: NETBEANS-2842 > URL: https://issues.apache.org/jira/browse/NETBEANS-2842 > Project: NetBeans > Issue Type: Bug > Components: platform - Plugin Manager >Affects Versions: 11.3 >Reporter: Benjamin Graf >Priority: Critical > Attachments: nbpython.zip, unpack200 failure.png > > > Netbeans plugins are mostly compressed in size by the JDK internal pack200 > tool which is deprecated since JDK 11 ([https://openjdk.java.net/jeps/336]). > It should be thought about an alternative as it might get removed in next JDK > releases. -- 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] [Assigned] (NETBEANS-5896) Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
[
https://issues.apache.org/jira/browse/NETBEANS-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-5896:
-
Assignee: Jan Lahoda
> Missing "com.sun.tools.javac.comp.Enter.unenter" with vanilla javac
> ---
>
> Key: NETBEANS-5896
> URL: https://issues.apache.org/jira/browse/NETBEANS-5896
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.4
> Environment: Java 11.0.11 on Windows 10 on NetBeans 12.4 with vanilla
> javac (nb-javac _not_ installed)
>Reporter: Eirik Bakke
>Assignee: Jan Lahoda
>Priority: Major
>
> Working with Compile-on-Save enabled on a Maven-based NetBeans Platform
> project, with vanilla javac (nb-javac _not_ installed), I frequently get the
> following stack trace:
> {noformat}
> java.lang.NoSuchMethodException:
> com.sun.tools.javac.comp.Enter.unenter(com.sun.tools.javac.tree.JCTree$JCCompilationUnit,
> com.sun.tools.javac.tree.JCTree)
> at java.base/java.lang.Class.getDeclaredMethod(Class.java:2475)
> at
> org.netbeans.api.java.source.TreeUtilities.unenter(TreeUtilities.java:927)
> at
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:916)
> at
> org.netbeans.api.java.source.TreeUtilities.attributeTree(TreeUtilities.java:845)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:502)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$1.run(DeclarativeHintsParser.java:477)
> at
> org.netbeans.modules.java.source.parsing.MimeTask.run(MimeTask.java:60)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:586)
> at
> org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:357)
> at
> org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.run(ParserManager.java:340)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:181)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:178)
> at
> org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:153)
> at
> org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:335)
> at
> org.netbeans.modules.parsing.nb.DataObjectEnvFactory.runPriorityIO(DataObjectEnvFactory.java:118)
> at
> org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:67)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:178)
> at
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:311)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:431)
> at
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.resolve(DeclarativeHintsParser.java:477)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.access$000(DeclarativeHintsParser.java:83)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseCondition(DeclarativeHintsParser.java:311)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseConditions(DeclarativeHintsParser.java:258)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseRule(DeclarativeHintsParser.java:215)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.parseInput(DeclarativeHintsParser.java:184)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser$Impl.access$200(DeclarativeHintsParser.java:90)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintsParser.parse(DeclarativeHintsParser.java:395)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHints(DeclarativeHintRegistry.java:263)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.parseHintFile(DeclarativeHintRegistry.java:239)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.readHints(DeclarativeHintRegistry.java:128)
> at
> org.netbeans.modules.java.hints.declarative.DeclarativeHintRegistry.computeHints(DeclarativeHintRegistry.java:111)
> at
> org.netbeans.modules.java.hints.spiimpl.RulesManagerImpl.readHints(RulesManagerImpl.java:139)
> at
> org.netbeans.modules.java.hints.spiimpl.hints.HintsInvoker.computeHints(HintsInvoker.java:133)
> at
>
[jira] [Commented] (NETBEANS-6179) Open Project dialog can take over 30 seconds to appear on Windows.
[ https://issues.apache.org/jira/browse/NETBEANS-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17439919#comment-17439919 ] Jaroslav Tulach commented on NETBEANS-6179: --- According to [^NetBeans126_OpenProject.nps] the EDT thread is blocked for 45s in * com.formdev.flatlaf.ui.FlatFileChooserUI$FlatFileView.getIcon() > Open Project dialog can take over 30 seconds to appear on Windows. > -- > > Key: NETBEANS-6179 > URL: https://issues.apache.org/jira/browse/NETBEANS-6179 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance > Environment: Wndows10 Pro > Java 17.0.1 (Zulu + JavaFX) > NetBeans 12.6-rc2 (and earlier) >Reporter: Scott Palmer >Priority: Major > Labels: performance > Attachments: NetBeans126_OpenProject.nps, NetBeans126_OpenProject2.nps > > > On Windows systems with disconnected mapped network drives, the "Open > Project" dialog can take over 30 seconds to appear. The "Open File" dialog > does not suffer from this issue. > While attempts to actually access the unavailable network drives can > logically lead to timeouts, since the open Project dialog will initially be > browsing in folder unrelated to the disconnected drive letters, there is no > reason that they should be holding up the initialization of the dialog. > VisualVM snapshot data collected while triggering and waiting for the Open > Project dialog is attached. -- 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] [Created] (NETBEANS-6170) java.mx.project SdkSuiteTest is unstable
Jaroslav Tulach created NETBEANS-6170:
-
Summary: java.mx.project SdkSuiteTest is unstable
Key: NETBEANS-6170
URL: https://issues.apache.org/jira/browse/NETBEANS-6170
Project: NetBeans
Issue Type: Bug
Components: java - Source
Reporter: Jaroslav Tulach
Assignee: Dusan Balek
There are frequent failures in our gate (like
[https://app.travis-ci.com/github/apache/netbeans/jobs/546099463)]. It seems to
be random, yet persistent:
{code:java}
verified 88 java files and 1 non-java files in 2813 ms, overall running for 29
s
/data/graal/sdk/src/org.graalvm.nativeimage/src/org/graalvm/nativeimage/Isolate.java:
43: package org.graalvm.nativeimage.c.struct does not exist
/data/graal/sdk/src/org.graalvm.nativeimage/src/org/graalvm/nativeimage/Isolate.java:
52: cannot find symbol symbol: class CStruct
errors found in
/home/travis/build/apache/netbeans/java/java.mx.project/build/test/unit/data/graal/sdk/src/org.graalvm.nativeimage/src/org/graalvm/nativeimage/Isolate.java@8b3faa1d:7ac780f2
Classpath:
cp#1:
/home/travis/build/apache/netbeans/java/java.mx.project/build/test/unit/data/graal/sdk/mxbuild/org.graalvm.options/bin@b1d88340:2590c44a
cp#2:
/home/travis/build/apache/netbeans/java/java.mx.project/build/test/unit/data/graal/sdk/mxbuild/org.graalvm.word/bin@426c9c36:775534f1{code}
Try locally on JDK-8:
{code:java}
X=0; while ant -f java/java.mx.project test; do X=`expr $X + 1`; echo Round $X;
sleep 3; done; ant -f java/java.mx.project test-generate-html; echo Fail at $X
round{code}
it has just fallen for me on 3rd round.
Originally we thought it is an error in the way classpath is computed, but it
seems that symbols from the same package aren't found - e.g. it is likely a bug
in Java source.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5884) Jackpot doesn't work on JDK 17
[
https://issues.apache.org/jira/browse/NETBEANS-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17426948#comment-17426948
]
Jaroslav Tulach commented on NETBEANS-5884:
---
The voting for new version 12.5 is on
https://lists.apache.org/thread.html/r95f0420ac8f2f89091492364921c1f85815dd44cf1c2d9d9d0ea895c%40%3Cdev.netbeans.apache.org%3E
> Jackpot doesn't work on JDK 17
> --
>
> Key: NETBEANS-5884
> URL: https://issues.apache.org/jira/browse/NETBEANS-5884
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Major
>
> {code:java}
> java.lang.NoSuchMethodError: 'void
> com.sun.tools.javac.util.Log.(com.sun.tools.javac.util.Context,
> java.io.PrintWriter, java.io.PrintWriter, java.io.PrintWriter)'
> at org.netbeans.lib.nbjavac.services.NBLog.(NBLog.java:55)
> at org.netbeans.lib.nbjavac.services.NBLog.(NBLog.java:40)
> at org.netbeans.lib.nbjavac.services.NBLog$1.make(NBLog.java:73)
> at org.netbeans.lib.nbjavac.services.NBLog$1.make(NBLog.java:70) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5064) Support for specific NB (feature release) versions
[
https://issues.apache.org/jira/browse/NETBEANS-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420081#comment-17420081
]
Jaroslav Tulach edited comment on NETBEANS-5064 at 9/25/21, 7:58 AM:
-
The NetBeans IDE versions are meaningless from an engineering perspective. If
we want to simplify life of plugin writes (and we should), then I suggest to
support many range dependencies:
[http://wiki.apidesign.org/wiki/RangeDependenciesAnalysed] to quote:
{quote}Should there be a repository of modules and their
[dependencies|http://wiki.apidesign.org/wiki/Dependencies] including module _M_
in versions 1.1,1.2,1.5,2.0,2.5,3.0. If majority of other modules having a
dependency on _M_ uses range [1.1,2.0) (e.g. the classical range for [semantic
versioning|http://wiki.apidesign.org/wiki/Semantic_versioning]), then we can
deduce that the owner of module _M_ is doing good job keeping
[BackwardCompatibility|http://wiki.apidesign.org/wiki/BackwardCompatibility].
If many dependencies on _M_ use for example [1.1,1.5), then we can deduce that
something unnatural (from the point of [semantic
versioning|http://wiki.apidesign.org/wiki/Semantic_versioning] happened in
version 1.5) and that the owner of the module _M_ underestimated the impact of
changes in version 1.5. On the other hand, if many dependencies on _M_ use
range like [1.1,3.0) then the
[incompatible|http://wiki.apidesign.org/wiki/Incompatible] change was probably
not as [incompatible|http://wiki.apidesign.org/wiki/Incompatible] as it might
have seen.
{quote}
Let, for each published NBM, allow the author to specify the (essential)
dependencies on some modules from NetBeans IDE distribution and the supported
ranges. Lower bound (that's in the NBM's JAR manifest anyway) and an upper
bound (implicit to major module version, but let module writers restrict it
even more).
The module catalog for a version of NetBeans IDE should then offer all NBMs
that have their dependencies (lower and upper bounds) satisfied.
was (Author: jtulach):
The NetBeans IDE versions are meaningless from an engineering perspective. If
we want to simplify life of plugin writes (and we should), the I suggest to
support many range dependencies:
[http://wiki.apidesign.org/wiki/RangeDependenciesAnalysed] to quote:
{quote}Should there be a repository of modules and their
[dependencies|http://wiki.apidesign.org/wiki/Dependencies] including module _M_
in versions 1.1,1.2,1.5,2.0,2.5,3.0. If majority of other modules having a
dependency on _M_ uses range [1.1,2.0) (e.g. the classical range for [semantic
versioning|http://wiki.apidesign.org/wiki/Semantic_versioning]), then we can
deduce that the owner of module _M_ is doing good job keeping
[BackwardCompatibility|http://wiki.apidesign.org/wiki/BackwardCompatibility].
If many dependencies on _M_ use for example [1.1,1.5), then we can deduce that
something unnatural (from the point of [semantic
versioning|http://wiki.apidesign.org/wiki/Semantic_versioning] happened in
version 1.5) and that the owner of the module _M_ underestimated the impact of
changes in version 1.5. On the other hand, if many dependencies on _M_ use
range like [1.1,3.0) then the
[incompatible|http://wiki.apidesign.org/wiki/Incompatible] change was probably
not as [incompatible|http://wiki.apidesign.org/wiki/Incompatible] as it might
have seen.
{quote}
Let, for each published NBM, allow the author to specify the (essential)
dependencies on some modules from NetBeans IDE distribution and the supported
ranges. Lower bound (that's in the NBM's JAR manifest anyway) and an upper
bound (implicit to major module version, but let module writers restrict it
even more).
The module catalog for a version of NetBeans IDE should then offer all NBMs
that have their dependencies (lower and upper bounds) satisfied.
> Support for specific NB (feature release) versions
> --
>
> Key: NETBEANS-5064
> URL: https://issues.apache.org/jira/browse/NETBEANS-5064
> Project: NetBeans
> Issue Type: Wish
> Components: updatecenters - Pluginportal
>Reporter: Junichi Yamamoto
>Priority: Major
>
> Maybe, currently, URLs for feature versions(e.g. 12.1) are redirected to the
> URL for the LTS(e.g. 12.0) version, right?
> That has a problem. We can't use an nbm of the LTS version if a feature
> version has incompatible changes.
> There are incompatible changes for PHP support in NetBeans 12.2. So, some
> plugins related to PHP don't work any longer in 12.2 with the nbm for 12.0.
> So, I have to provide nbms for 12.2. However, we can't add them to PP at the
> moment. So, I have to upload them to another place(e.g. GitHub).
> It would be nice for users/developers if we can add nbms for specific
> versions. OTOH, it may be hard work for
[jira] [Commented] (NETBEANS-5064) Support for specific NB (feature release) versions
[
https://issues.apache.org/jira/browse/NETBEANS-5064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420081#comment-17420081
]
Jaroslav Tulach commented on NETBEANS-5064:
---
The NetBeans IDE versions are meaningless from an engineering perspective. If
we want to simplify life of plugin writes (and we should), the I suggest to
support many range dependencies:
[http://wiki.apidesign.org/wiki/RangeDependenciesAnalysed] to quote:
{quote}Should there be a repository of modules and their
[dependencies|http://wiki.apidesign.org/wiki/Dependencies] including module _M_
in versions 1.1,1.2,1.5,2.0,2.5,3.0. If majority of other modules having a
dependency on _M_ uses range [1.1,2.0) (e.g. the classical range for [semantic
versioning|http://wiki.apidesign.org/wiki/Semantic_versioning]), then we can
deduce that the owner of module _M_ is doing good job keeping
[BackwardCompatibility|http://wiki.apidesign.org/wiki/BackwardCompatibility].
If many dependencies on _M_ use for example [1.1,1.5), then we can deduce that
something unnatural (from the point of [semantic
versioning|http://wiki.apidesign.org/wiki/Semantic_versioning] happened in
version 1.5) and that the owner of the module _M_ underestimated the impact of
changes in version 1.5. On the other hand, if many dependencies on _M_ use
range like [1.1,3.0) then the
[incompatible|http://wiki.apidesign.org/wiki/Incompatible] change was probably
not as [incompatible|http://wiki.apidesign.org/wiki/Incompatible] as it might
have seen.
{quote}
Let, for each published NBM, allow the author to specify the (essential)
dependencies on some modules from NetBeans IDE distribution and the supported
ranges. Lower bound (that's in the NBM's JAR manifest anyway) and an upper
bound (implicit to major module version, but let module writers restrict it
even more).
The module catalog for a version of NetBeans IDE should then offer all NBMs
that have their dependencies (lower and upper bounds) satisfied.
> Support for specific NB (feature release) versions
> --
>
> Key: NETBEANS-5064
> URL: https://issues.apache.org/jira/browse/NETBEANS-5064
> Project: NetBeans
> Issue Type: Wish
> Components: updatecenters - Pluginportal
>Reporter: Junichi Yamamoto
>Priority: Major
>
> Maybe, currently, URLs for feature versions(e.g. 12.1) are redirected to the
> URL for the LTS(e.g. 12.0) version, right?
> That has a problem. We can't use an nbm of the LTS version if a feature
> version has incompatible changes.
> There are incompatible changes for PHP support in NetBeans 12.2. So, some
> plugins related to PHP don't work any longer in 12.2 with the nbm for 12.0.
> So, I have to provide nbms for 12.2. However, we can't add them to PP at the
> moment. So, I have to upload them to another place(e.g. GitHub).
> It would be nice for users/developers if we can add nbms for specific
> versions. OTOH, it may be hard work for verifiers(/developers) to
> verify(/add) them...
> e.g. Although I'm not sure whether it is possible, if there is no nbm of
> specific versions, it would be nice to be able to use nbms of LTS versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-6044) Annotation processors configured for compiler plugin are not used for editor parsing
[ https://issues.apache.org/jira/browse/NETBEANS-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418946#comment-17418946 ] Jaroslav Tulach commented on NETBEANS-6044: --- The fix will have to use [PluginPropertyUtils|https://github.com/apache/netbeans/blob/c084119009d2e0f736f225d706bc1827af283501/java/maven/src/org/netbeans/modules/maven/queries/MavenSourceLevelImpl.java#L165] somehow, I guess. > Annotation processors configured for compiler plugin are not used for editor > parsing > > > Key: NETBEANS-6044 > URL: https://issues.apache.org/jira/browse/NETBEANS-6044 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 12.5 >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > Maven supplies "classpath/compile" ClassPath as the processor classpath. But > the compiler-maven-plugin supports a special processor classpath that can be > set in plugin configuration and should be used for discovery in addition(?) > to regular compile classpath. > This technique is used in e.g. *micronaut* where the *micronaut-parent* POM > inherited into user projects configures annotation processors this way. > Errors that appear at compile time are not reported or underlined in the > IDE's editor. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans IDE
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Summary: Using groovy compiler for parsing, code completion and navigation in NetBeans IDE (was: Using groovy compiler for parsing, code completion and navigation in NetBeans) > Using groovy compiler for parsing, code completion and navigation in NetBeans > IDE > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute the IDE related fixes to > the Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of writing Groovy in the NetBeans > IDE (and its derivatives like VSCode) better, richer, easier to use, faster > to gain response and overall more reliable. In particular the IDE has to be > able to deal with broken code (user code in editor is broken most of the > time) - as such we expect fixes in the area of error recovery to make the > parser more bulletproof and robust. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it uses type checking and static > compilation heavily. It would be ideal if the IDE could just use the static > compilation info/errors and present them to the user in a reasonable and > valuable way. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of writing Groovy in the NetBeans IDE (and its derivatives like VSCode) better, richer, easier to use, faster to gain response and overall more reliable. In particular the IDE has to be able to deal with broken code (user code in editor is broken most of the time) - as such we expect fixes in the area of error recovery to make the parser more bulletproof and robust. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present them to the user in a reasonable and valuable way. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE (and its derivatives like VSCode) better, richer, easier to use, faster to gain response and overall more reliable. In particular the IDE has to be able to deal with broken code (user code in editor is broken most of the time) - as such we expect fixes in the area of error recovery to make the parser more bulletproof and robust. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present them to the user in a reasonable and valuable way. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute the IDE related fixes to > the Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of writing Groovy in the NetBeans > IDE (and its derivatives like VSCode) better, richer, easier to use, faster > to gain response and overall more reliable. In particular the IDE has to be > able to deal with
[jira] [Updated] (NETBEANS-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE (and its derivatives like VSCode) better, richer, easier to use, faster to gain response and overall more reliable. In particular the IDE has to be able to deal with broken code (user code in editor is broken most of the time) - as such we expect fixes in the area of error recovery to make the parser more bulletproof and robust. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present them to the user in a reasonable and valuable way. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE (and its derivatives like VSCode) better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present them to the user in a reasonable and valuable way. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute the IDE related fixes to > the Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE (and its derivatives like VSCode) better, richer, easier to use, faster > to gain response and overall more reliable. In particular the IDE has to be > able to deal with broken code (user code in editor is broken most of the > time) - as such we expect fixes in the area of error recovery to make the > parser more bulletproof and robust. > Some of the reported issues may feel
[jira] [Updated] (NETBEANS-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE (and its derivatives like VSCode) better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present them to the user in a reasonable and valuable way. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE (and its derivatives like VSCode) better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute the IDE related fixes to > the Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE (and its derivatives like VSCode) better, richer, easier to use, faster > to gain response and overall more reliable. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it uses type checking and static > compilation heavily. It would be ideal if the IDE could just use the static > compilation info/errors and present them to the user in a reasonable and > valuable way. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (NETBEANS-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE (and its derivatives like VSCode) better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute the IDE related fixes to > the Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE (and its derivatives like VSCode) better, richer, easier to use, faster > to gain response and overall more reliable. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it uses type checking and static > compilation heavily. It would be ideal if the IDE could just use the static > compilation info/errors and present it to the user. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional
[jira] [Updated] (NETBEANS-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute the IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute the IDE related fixes to > the Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE and derivatives better, richer, easier to use, faster to gain response > and overall more reliable. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it uses type checking and static > compilation heavily. It would be ideal if the IDE could just use the static > compilation info/errors and present it to the user. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail:
[jira] [Updated] (NETBEANS-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real compiler allowed NetBeans to keep the WYSIWYG experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real compiler allowed NetBeans to keep the WYSIWYG experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it turns on the > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real compiler allowed > NetBeans to keep the WYSIWYG experience (the errors reported in the editor > are exactly the same as on command line or continuous integration) with > relatively low effort. However maintaining a fork turned out to be costly and > we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to > do even better. We want to contribute IDE related fixes to the Groovy > compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE and derivatives better, richer, easier to use, faster to gain response > and overall more reliable. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it uses type checking and static > compilation heavily. It would be ideal if the IDE could just use the static > compilation info/errors and present it to the user. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the WYSIWYG experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real compiler allowed NetBeans to keep the WYSIWYG experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the WYSIWYG experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute IDE related fixes to the > Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE and derivatives better, richer, easier to use, faster to gain response > and overall more reliable. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it uses type checking and static > compilation heavily. It would be ideal if the IDE could just use the static > compilation info/errors and present it to the user. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For
[jira] [Updated] (NETBEANS-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. was: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real Java compiler allowed NetBeans to keep the WYSIWYG experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it uses type checking and static compilation heavily. It would be ideal if the IDE could just use the static compilation info/errors and present it to the user. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real Java compiler > allowed NetBeans to keep the *WYSIWYG* experience (the errors reported in the > editor are exactly the same as on command line or continuous integration) > with relatively low effort. However maintaining a fork turned out to be > costly and we are looking forward to reuse *javac* unmodified. With Groovy, > we'd like to do even better. We want to contribute IDE related fixes to the > Groovy compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE and derivatives better, richer, easier to use, faster to gain response > and overall more reliable. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it uses type checking and static > compilation heavily. It would be ideal if the IDE could just use the static > compilation info/errors and present it to the user. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org
[jira] [Updated] (NETBEANS-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Description: NetBeans IDE has a tradition of using the real compiler for each language to provide the best user experience in its editor. A famous example is [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] - NetBeans fork of the *javac* compiler. Using the real compiler allowed NetBeans to keep the WYSIWYG experience (the errors reported in the editor are exactly the same as on command line or continuous integration) with relatively low effort. However maintaining a fork turned out to be costly and we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to do even better. We want to contribute IDE related fixes to the Groovy compiler to begin with! This issue is an umbrella collecting various issues filed against Groovy. Fixing them would make the user experience of using of Groovy in the NetBeans IDE and derivatives better, richer, easier to use, faster to gain response and overall more reliable. Some of the reported issues may feel strange from a plain Groovy point of view. Please take into account that the IDE needs to compute all the info without running the user code. As such it turns on the was: Umbrella issue, that could help to collect dependent errors filed in Groovy. Maybe it could be split to an issue tracking possible improvements and an issue that tracks improvment necessary for the next release. > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > NetBeans IDE has a tradition of using the real compiler for each language to > provide the best user experience in its editor. A famous example is > [nb-javac|https://cwiki.apache.org/confluence/display/NETBEANS/Overview%3A+nb-javac] > - NetBeans fork of the *javac* compiler. Using the real compiler allowed > NetBeans to keep the WYSIWYG experience (the errors reported in the editor > are exactly the same as on command line or continuous integration) with > relatively low effort. However maintaining a fork turned out to be costly and > we are looking forward to reuse *javac* unmodified. With Groovy, we'd like to > do even better. We want to contribute IDE related fixes to the Groovy > compiler to begin with! > This issue is an umbrella collecting various issues filed against Groovy. > Fixing them would make the user experience of using of Groovy in the NetBeans > IDE and derivatives better, richer, easier to use, faster to gain response > and overall more reliable. > Some of the reported issues may feel strange from a plain Groovy point of > view. Please take into account that the IDE needs to compute all the info > without running the user code. As such it turns on the -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5992) Using groovy compiler for parsing, code completion and navigation in NetBeans
[ https://issues.apache.org/jira/browse/NETBEANS-5992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5992: -- Summary: Using groovy compiler for parsing, code completion and navigation in NetBeans (was: Groovy compiler / parser bugs affecting NB code completion) > Using groovy compiler for parsing, code completion and navigation in NetBeans > - > > Key: NETBEANS-5992 > URL: https://issues.apache.org/jira/browse/NETBEANS-5992 > Project: NetBeans > Issue Type: Task > Components: groovy - Editor >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > > Umbrella issue, that could help to collect dependent errors filed in Groovy. > Maybe it could be split to an issue tracking possible improvements and an > issue that tracks improvment necessary for the next release. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-4171) Gradle issue in Netbeans, creating a basic gadle project in Netbeans 11.3
[
https://issues.apache.org/jira/browse/NETBEANS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-4171.
---
Fix Version/s: 12.6
Assignee: Jaroslav Tulach
Resolution: Fixed
Since [PR-3084|https://github.com/apache/netbeans/pull/3084] the new project
functionality is using {{gradlew init}} - e.g. the generated project should
match Gradle 7.0 standards.
Certainly it is worth to check the behavior in 12.6 development builds.
> Gradle issue in Netbeans, creating a basic gadle project in Netbeans 11.3
> -
>
> Key: NETBEANS-4171
> URL: https://issues.apache.org/jira/browse/NETBEANS-4171
> Project: NetBeans
> Issue Type: Bug
> Environment: Windows 10 Prof.
>Reporter: Fahad
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: 12.6
>
>
> After creating a new gradle project in NetBeans 11.3, I get the following
> error while trying to edit the build.gradle file.
>
> java.lang.NoClassDefFoundError: Could not initialize class
> org.codehaus.groovy.classgen.Verifier
> at
> org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170)
> at
> org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64)
> at
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441)
> at
> org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598)
> at
> org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:775)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279)
> at
> org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.execute(TaskProcessor.java:702)
> [catch] at
> org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:663)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> 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)
> at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-4171) Gradle issue in Netbeans, creating a basic gradle project in Netbeans 11.3
[ https://issues.apache.org/jira/browse/NETBEANS-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-4171: -- Summary: Gradle issue in Netbeans, creating a basic gradle project in Netbeans 11.3 (was: Gradle issue in Netbeans, creating a basic gadle project in Netbeans 11.3) > Gradle issue in Netbeans, creating a basic gradle project in Netbeans 11.3 > -- > > Key: NETBEANS-4171 > URL: https://issues.apache.org/jira/browse/NETBEANS-4171 > Project: NetBeans > Issue Type: Bug > Environment: Windows 10 Prof. >Reporter: Fahad >Assignee: Jaroslav Tulach >Priority: Major > Fix For: 12.6 > > > After creating a new gradle project in NetBeans 11.3, I get the following > error while trying to edit the build.gradle file. > > java.lang.NoClassDefFoundError: Could not initialize class > org.codehaus.groovy.classgen.Verifier > at > org.codehaus.groovy.control.CompilationUnit.(CompilationUnit.java:170) > at > org.netbeans.modules.groovy.editor.compiler.CompilationUnit.(CompilationUnit.java:64) > at > org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parseBuffer(GroovyParser.java:441) > at > org.netbeans.modules.groovy.editor.api.parser.GroovyParser.parse(GroovyParser.java:137) > at > org.netbeans.modules.parsing.impl.TaskProcessor.callParse(TaskProcessor.java:598) > at > org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:228) > at > org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.run(TaskProcessor.java:775) > at org.openide.util.lookup.Lookups.executeWith(Lookups.java:279) > at > org.netbeans.modules.parsing.impl.TaskProcessor$RequestPerformer.execute(TaskProcessor.java:702) > [catch] at > org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:663) > at > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > 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) > at > org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033) -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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] [Assigned] (NETBEANS-5971) Support Maven Wrapper (mvnw)
[ https://issues.apache.org/jira/browse/NETBEANS-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-5971: - Assignee: (was: Jaroslav Tulach) > Support Maven Wrapper (mvnw) > > > Key: NETBEANS-5971 > URL: https://issues.apache.org/jira/browse/NETBEANS-5971 > Project: NetBeans > Issue Type: Improvement > Components: projects - Maven >Affects Versions: 12.4 >Reporter: Bruno Borges >Priority: Major > > Many projects now use the Maven Wrapper command-line tool to ensure > reproducibility and ease onboarding. > Maven Wrapper is also a tool now part of Apache Maven. > Currently, NetBeans only supports either the Bundled Maven distro (always a > few versions behind latest), or a Maven installation elsewhere. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406560#comment-17406560 ] Jaroslav Tulach commented on NETBEANS-5914: --- All the here-in listed deadlocks are going to be fixed by https://github.com/apache/netbeans/pull/3136 and especially https://github.com/apache/netbeans/commit/9227546960199ecec44755a03cce6f1d59ade69d > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.5 > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Assignee: Jaroslav Tulach >Priority: Blocker > Labels: pull-request-available > Fix For: 12.6 > > Attachments: 12.5-beta2-threaddump-1629986898821.tdump, 210506 > NetBeans Deadlock on Startup 2.txt, 210506 NetBeans Deadlock on Startup.txt, > 210516 Another NetBeans Deadlock.txt, 210526 NetBeans Deadlock again.txt > > Time Spent: 50m > Remaining Estimate: 0h > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406126#comment-17406126 ] Jaroslav Tulach edited comment on NETBEANS-5914 at 8/28/21, 6:31 AM: - The new [^12.5-beta2-threaddump-1629986898821.tdump] dump doesn't contain the word "auxiliary" like the previous ones ( [^210506 NetBeans Deadlock on Startup.txt] and [^210506 NetBeans Deadlock on Startup 2.txt] and [^210526 NetBeans Deadlock again.txt] ). The [^12.5-beta2-threaddump-1629986898821.tdump] and [^210516 Another NetBeans Deadlock.txt] are different - e.g. without "auxiliary". [PR-3136|https://github.com/apache/netbeans/pull/3136] shall fix [^12.5-beta2-threaddump-1629986898821.tdump]. was (Author: jtulach): The new [^12.5-beta2-threaddump-1629986898821.tdump] dump doesn't contain the word "auxiliary" like the previous ones ( [^210506 NetBeans Deadlock on Startup.txt] and [^210506 NetBeans Deadlock on Startup 2.txt] and [^210526 NetBeans Deadlock again.txt] ). The [^12.5-beta2-threaddump-1629986898821.tdump] and [^210516 Another NetBeans Deadlock.txt] are different - e.g. without "auxiliary". > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.5 > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Assignee: Jaroslav Tulach >Priority: Blocker > Labels: pull-request-available > Fix For: 12.6 > > Attachments: 12.5-beta2-threaddump-1629986898821.tdump, 210506 > NetBeans Deadlock on Startup 2.txt, 210506 NetBeans Deadlock on Startup.txt, > 210516 Another NetBeans Deadlock.txt, 210526 NetBeans Deadlock again.txt > > Time Spent: 10m > Remaining Estimate: 0h > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17406126#comment-17406126 ] Jaroslav Tulach commented on NETBEANS-5914: --- The new [^12.5-beta2-threaddump-1629986898821.tdump] dump doesn't contain the word "auxiliary" like the previous ones ( [^210506 NetBeans Deadlock on Startup.txt] and [^210506 NetBeans Deadlock on Startup 2.txt] and [^210526 NetBeans Deadlock again.txt] ). The [^12.5-beta2-threaddump-1629986898821.tdump] and [^210516 Another NetBeans Deadlock.txt] are different - e.g. without "auxiliary". > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.5 > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Assignee: Jaroslav Tulach >Priority: Blocker > Fix For: 12.6 > > Attachments: 12.5-beta2-threaddump-1629986898821.tdump, 210506 > NetBeans Deadlock on Startup 2.txt, 210506 NetBeans Deadlock on Startup.txt, > 210516 Another NetBeans Deadlock.txt, 210526 NetBeans Deadlock again.txt > > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5914: -- Fix Version/s: 12.6 > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.5 > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Assignee: Jaroslav Tulach >Priority: Blocker > Fix For: 12.6 > > Attachments: 12.5-beta2-threaddump-1629986898821.tdump, 210506 > NetBeans Deadlock on Startup 2.txt, 210506 NetBeans Deadlock on Startup.txt, > 210516 Another NetBeans Deadlock.txt, 210526 NetBeans Deadlock again.txt > > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5914) NetBeans 12.4 freezes on startup
[ https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405585#comment-17405585 ] Jaroslav Tulach commented on NETBEANS-5914: --- Right. While the deadlock is unfortunate, it is not a regression in 12.5. If people could live it so far, they will be able to live with it one more release. > NetBeans 12.4 freezes on startup > > > Key: NETBEANS-5914 > URL: https://issues.apache.org/jira/browse/NETBEANS-5914 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.5 > Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10. >Reporter: Eirik Bakke >Assignee: Jaroslav Tulach >Priority: Blocker > Attachments: 12.5-beta2-threaddump-1629986898821.tdump, 210506 > NetBeans Deadlock on Startup 2.txt, 210506 NetBeans Deadlock on Startup.txt, > 210516 Another NetBeans Deadlock.txt, 210526 NetBeans Deadlock again.txt > > > On NetBeans 12.4, I was previously experiencing some intermittent freezes on > startup, at the time when projects were being loaded and such. I did some > thread dumps of the frozen IDE using VisualVM. I'm uploading these now in > case they are related to NETBEANS-5913. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5526) New Java project for NBLS over LSP for Maven and Gradle
[ https://issues.apache.org/jira/browse/NETBEANS-5526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach resolved NETBEANS-5526. --- Fix Version/s: (was: Next) 12.5 Resolution: Fixed https://github.com/apache/netbeans/pull/3084 https://github.com/apache/netbeans/pull/2999 > New Java project for NBLS over LSP for Maven and Gradle > --- > > Key: NETBEANS-5526 > URL: https://issues.apache.org/jira/browse/NETBEANS-5526 > Project: NetBeans > Issue Type: New Feature > Components: vscode >Affects Versions: 12.4 >Reporter: Martin Balin >Assignee: Jaroslav Tulach >Priority: Major > Labels: Gradle, maven > Fix For: 12.5 > > > VSNetBeans is missing an easy way to create a New Java project. This is > really missing and I personally switch to NetBeans to jump start new project > so pom.xml... is created for me as well as main Java class. > To really enable Java development in VSCode we need to provide this > functionality. Otherwise it is missing the _Start of Java journey_ for > ordinary developer. > It will be good if connect this to NBLS project support and enable > Maven+Gradle projects there. Wizard should be invoked from Command Palette > and will likely consists of several steps for simplest project types. > For the start we can support just some simple projects. > Original idea was to get pom.xml with main Java class set for execution, jar > packaging and listing main class for jar execution in Manifest.mf... -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5159) Select proper JDK for mx project
[
https://issues.apache.org/jira/browse/NETBEANS-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-5159.
---
Fix Version/s: 12.5
Resolution: Fixed
Fixed by https://github.com/apache/netbeans/pull/3071
> Select proper JDK for mx project
>
>
> Key: NETBEANS-5159
> URL: https://issues.apache.org/jira/browse/NETBEANS-5159
> Project: NetBeans
> Issue Type: New Feature
> Components: java - Project
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Major
> Fix For: 12.5
>
>
> "mx project support" as developed in
> [PR-2575|https://github.com/apache/netbeans/pull/2575] should be able to
> properly select the right JDK for each "javaCompliance" level. Various
> {{EXTRA_JAVA_HOMES}} can be specified in {{mx}}'s {{env}} files and the right
> JDK should be used for each source root.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Assigned] (NETBEANS-5159) Select proper JDK for mx project
[
https://issues.apache.org/jira/browse/NETBEANS-5159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-5159:
-
Assignee: Jaroslav Tulach
> Select proper JDK for mx project
>
>
> Key: NETBEANS-5159
> URL: https://issues.apache.org/jira/browse/NETBEANS-5159
> Project: NetBeans
> Issue Type: New Feature
> Components: java - Project
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Major
>
> "mx project support" as developed in
> [PR-2575|https://github.com/apache/netbeans/pull/2575] should be able to
> properly select the right JDK for each "javaCompliance" level. Various
> {{EXTRA_JAVA_HOMES}} can be specified in {{mx}}'s {{env}} files and the right
> JDK should be used for each source root.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5215) Progress API use-cases aren't valid
[
https://issues.apache.org/jira/browse/NETBEANS-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-5215:
--
Description:
Looking at
[https://bits.netbeans.org/11.1/javadoc/org-netbeans-api-progress/overview-summary.html]
I see that the documentation hasn't been properly updated to reflect the split
of Progress API and Progress Swing API. For example:
{code:java}
ProgressHandle handle = ProgressHandleFactory.creatHandle("My custom task");
{code}
there is a typo (consider using @codesnippet tag, at least in documentation
inside of classes). Moreover the {{ProgressHandleFactory}} isn't even in the
Progress API!
Various other apichanges entries like {{showProgressDialogAndRun}} are also out
of scope and belong to Progress Swing API.
was:
Looking at
[https://bits.netbeans.org/11.1/javadoc/org-netbeans-api-progress/overview-summary.html]
I see that the documentation hasn't been properly updated to reflect the split
of Progress API and Progress Swing API. For example:
{code:java}
ProgressHandle handle = ProgressHandleFactory.creatHandle("My custom task");
{code}
there is a typo (consider using @codesnippet tag, at least in documentation
inside of classes). Moreover the {{ProgressHandleFactory}} isn't even in the
Progress API!
Various other apichanges entries like showProgressDialogAndRun are also
out of scope and belong to Progress Swing API.
> Progress API use-cases aren't valid
> ---
>
> Key: NETBEANS-5215
> URL: https://issues.apache.org/jira/browse/NETBEANS-5215
> Project: NetBeans
> Issue Type: Bug
> Components: platform - Progress
>Affects Versions: 11.1
>Reporter: Jaroslav Tulach
>Assignee: Svatopluk Dedic
>Priority: Minor
> Labels: sd-candidate
>
> Looking at
> [https://bits.netbeans.org/11.1/javadoc/org-netbeans-api-progress/overview-summary.html]
> I see that the documentation hasn't been properly updated to reflect the
> split of Progress API and Progress Swing API. For example:
> {code:java}
> ProgressHandle handle = ProgressHandleFactory.creatHandle("My custom task");
> {code}
> there is a typo (consider using @codesnippet tag, at least in documentation
> inside of classes). Moreover the {{ProgressHandleFactory}} isn't even in the
> Progress API!
> Various other apichanges entries like {{showProgressDialogAndRun}} are also
> out of scope and belong to Progress Swing API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5339) Let's NetBeans Java Support work with --release X flag
[
https://issues.apache.org/jira/browse/NETBEANS-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17404976#comment-17404976
]
Jaroslav Tulach commented on NETBEANS-5339:
---
There is an attempt to reuse profiles support for releases:
[https://github.com/apache/netbeans/pull/2786] - however it is far from being
finished.
> Let's NetBeans Java Support work with --release X flag
> --
>
> Key: NETBEANS-5339
> URL: https://issues.apache.org/jira/browse/NETBEANS-5339
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Source
>Affects Versions: 12.0
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Critical
>
> Since JDK9 there is {{-release}} flag which can specify which JDK API one
> wishes to compile against. Time to use it in NetBeans!
> Historically NetBeans Java support tries to detect a JDK one is running on
> and decrease the requested {{--source}} level to the supported JDK. This is
> very annoying and in the context of {{--release}} flag, unnecessary.
> Modern {{javac}} compiler have snapshot JDK API for each version since JDK7
> to the latest JDK. Regardless on which version the NetBeans IDE is running,
> people should be able to select the right release/target JDK and get errors
> according to its API.
> By default a specified {{--source}} (by a SourceVersionQuery) should also
> imply appropriate {{--release}}. There might be other means how to control
> both source as well as release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5802) Gradle project wizard should use gradle init
[
https://issues.apache.org/jira/browse/NETBEANS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-5802.
---
Fix Version/s: 12.6
Resolution: Fixed
Fixed in https://github.com/apache/netbeans/pull/3084
> Gradle project wizard should use gradle init
>
>
> Key: NETBEANS-5802
> URL: https://issues.apache.org/jira/browse/NETBEANS-5802
> Project: NetBeans
> Issue Type: Improvement
> Components: projects - Gradle
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
> Fix For: 12.6
>
>
> Hello Laszlo. As soon as I implemented the [VSCode project
> wizard|https://github.com/apache/netbeans/pull/2999] I got following feedback:
> {quote}The New Java Project wizard uses an unusual Gradle template with an
> older deprecated plugins syntax and jacoco included for some reason.
> To make this feature maintainable we should instead use the existing "gradle
> init" functionality:
> {code:java}
> gradle init --type java-application --test-framework junit-jupiter --dsl
> groovy --package com.example --project-name example
> {code}
> {quote}
> Shall we switch the new project in NetBeans to use the above given command?
> Do you want to do it? Or shall I do it?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5201) Valid JS treated as invalid by editor
[
https://issues.apache.org/jira/browse/NETBEANS-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402605#comment-17402605
]
Jaroslav Tulach commented on NETBEANS-5201:
---
Upgrading to newest version of {{graal-js-parser.jar}} would be great! Put the
JAR in, run the test, fix those that are failing and we are done. CCing
[~sdedic] .
> Valid JS treated as invalid by editor
> -
>
> Key: NETBEANS-5201
> URL: https://issues.apache.org/jira/browse/NETBEANS-5201
> Project: NetBeans
> Issue Type: Bug
> Components: javascript - Editor
>Affects Versions: 12.1, 12.2
>Reporter: Marek Gremblewski
>Priority: Major
> Attachments: Screenshot 2021-08-20 at 18.23.22.png,
> image-2020-12-31-17-20-30-117.png
>
>
> !image-2020-12-31-17-20-30-117.png!
> Below is code snipped:
> {code:java}
> var fn = function () {
> var actions = new DSsysLibActionIndex.lib.ActionIndex();
> actions.registerAction('asyncModalUpdateModelList', function (modal,
> params) {
> import('./actions/asyncModalUpdateModelList.js').then(function
> (Module) {
> var action = new Module.AsyncModalUpdateModelListAction(modal,
> params);
> action.run();
> });
> });
> actions.registerAction('asyncModalUpdateAuthorityList', function (modal,
> params) {
> import('./actions/asyncModalUpdateAuthorityList.js').then(function
> (Module) {
> var action = new
> Module.AsyncModalUpdateAuthorityListAction(modal, params);
> action.run();
> });
> });
> };
> {code}
> What is more interesting error appears only on the very first occurrence.
> Next occurrence is treated as valid.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Assigned] (NETBEANS-5740) Netbeans 12.4 freezes AWT from Micronaut Support
[ https://issues.apache.org/jira/browse/NETBEANS-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach reassigned NETBEANS-5740: - Assignee: Dusan Balek > Netbeans 12.4 freezes AWT from Micronaut Support > > > Key: NETBEANS-5740 > URL: https://issues.apache.org/jira/browse/NETBEANS-5740 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.4 > Environment: Ubuntu 20.04 > Netbeans 12.4 > OpenJDK 11.0.11 >Reporter: Diego Díez >Assignee: Dusan Balek >Priority: Major > Attachments: nb-freeze-dump.txt > > > We have started experiencing random freezes after upgrading to Netbeans 12.3, > not responding any component to mouse or keyboard interactions. > We have also noticed that lombok-1.18.18 stopped working with the newer > nb-javac installed with the 12.4 version (java16 support). I can't confirm > whether this is related with the freezes or not. Using lombok-1.18.20 seems > to work well, though. > Any ideas? Is there any log to look for errors? > As a workaround we have downgraded to 12.3 as it is a blocking issue for us, > being forced to kill the process every time it gets stuck. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5740) Netbeans 12.4 freezes AWT from Micronaut Support
[ https://issues.apache.org/jira/browse/NETBEANS-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5740: -- Summary: Netbeans 12.4 freezes AWT from Micronaut Support (was: Netbeans 12.4 randomly freezes) > Netbeans 12.4 freezes AWT from Micronaut Support > > > Key: NETBEANS-5740 > URL: https://issues.apache.org/jira/browse/NETBEANS-5740 > Project: NetBeans > Issue Type: Bug >Affects Versions: 12.4 > Environment: Ubuntu 20.04 > Netbeans 12.4 > OpenJDK 11.0.11 >Reporter: Diego Díez >Priority: Major > Attachments: nb-freeze-dump.txt > > > We have started experiencing random freezes after upgrading to Netbeans 12.3, > not responding any component to mouse or keyboard interactions. > We have also noticed that lombok-1.18.18 stopped working with the newer > nb-javac installed with the 12.4 version (java16 support). I can't confirm > whether this is related with the freezes or not. Using lombok-1.18.20 seems > to work well, though. > Any ideas? Is there any log to look for errors? > As a workaround we have downgraded to 12.3 as it is a blocking issue for us, > being forced to kill the process every time it gets stuck. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5913) 12.5 beta1 freezes
[
https://issues.apache.org/jira/browse/NETBEANS-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400119#comment-17400119
]
Jaroslav Tulach commented on NETBEANS-5913:
---
In [^netbeans-12.5-beta1-thread-dump.txt] there is also a note about Micronaut:
{code:java}
at
org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
at
org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
at
org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.resolve(MicronautJavaHyperlinkProvider.java:122)
at
org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
at
org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
at
org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(HyperlinkOperation.java:266)
at
org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlinking(HyperlinkOperation.java:224)
{code}
> 12.5 beta1 freezes
> --
>
> Key: NETBEANS-5913
> URL: https://issues.apache.org/jira/browse/NETBEANS-5913
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.5
> Environment: Product Version: Apache NetBeans IDE 12.5-beta1
> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
> User directory: /home/chris/.netbeans/12.5-beta1
> Cache directory: /home/chris/.cache/netbeans/12.5-beta1
>Reporter: Chris Wareham
>Assignee: Jan Lahoda
>Priority: Blocker
> Attachments: netbeans-12.5-beta1-azul-messages.log,
> netbeans-12.5-beta1-azul-thread-dump.txt, netbeans-12.5-beta1-messages.log,
> netbeans-12.5-beta1-thread-dump.txt
>
>
> I'm getting occasional freezes. It can be after a few minutes or a few hours,
> and there doesn't seem to be any specific user interaction that causes it. A
> thread dump and log file is attached.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5914) NetBeans 12.4 freezes on startup
[
https://issues.apache.org/jira/browse/NETBEANS-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17397940#comment-17397940
]
Jaroslav Tulach commented on NETBEANS-5914:
---
The log [^210506 NetBeans Deadlock on Startup 2.txt] seems to indicate the
problem is at
{code:java}
at
org.netbeans.spi.project.support.DelegatingLookupImpl.doDelegate(DelegatingLookupImpl.java:168)
- locked <0x00061e869218> (a java.util.ArrayList)
at
org.netbeans.spi.project.support.DelegatingLookupImpl.resultChanged(DelegatingLookupImpl.java:84)
{code}
The {{org.netbeans.spi.project.support.DelegatingLookupImpl}} class holds a
lock and calls into unknown code. That's against NetBeans API threading policy.
> NetBeans 12.4 freezes on startup
>
>
> Key: NETBEANS-5914
> URL: https://issues.apache.org/jira/browse/NETBEANS-5914
> Project: NetBeans
> Issue Type: Bug
> Environment: NetBeans 12.4 on Zulu/OpenJDK 11 on Windows 10.
>Reporter: Eirik Bakke
>Assignee: Jaroslav Tulach
>Priority: Major
> Attachments: 210506 NetBeans Deadlock on Startup 2.txt, 210506
> NetBeans Deadlock on Startup.txt, 210516 Another NetBeans Deadlock.txt,
> 210526 NetBeans Deadlock again.txt
>
>
> On NetBeans 12.4, I was previously experiencing some intermittent freezes on
> startup, at the time when projects were being loaded and such. I did some
> thread dumps of the frozen IDE using VisualVM. I'm uploading these now in
> case they are related to NETBEANS-5913.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Assigned] (NETBEANS-5884) Jackpot doesn't work on JDK 17
[
https://issues.apache.org/jira/browse/NETBEANS-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach reassigned NETBEANS-5884:
-
Assignee: Jan Lahoda
Description:
{code:java}
java.lang.NoSuchMethodError: 'void
com.sun.tools.javac.util.Log.(com.sun.tools.javac.util.Context,
java.io.PrintWriter, java.io.PrintWriter, java.io.PrintWriter)'
at org.netbeans.lib.nbjavac.services.NBLog.(NBLog.java:55)
at org.netbeans.lib.nbjavac.services.NBLog.(NBLog.java:40)
at org.netbeans.lib.nbjavac.services.NBLog$1.make(NBLog.java:73)
at org.netbeans.lib.nbjavac.services.NBLog$1.make(NBLog.java:70) {code}
> Jackpot doesn't work on JDK 17
> --
>
> Key: NETBEANS-5884
> URL: https://issues.apache.org/jira/browse/NETBEANS-5884
> Project: NetBeans
> Issue Type: Bug
> Components: java - Compiler
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Major
>
> {code:java}
> java.lang.NoSuchMethodError: 'void
> com.sun.tools.javac.util.Log.(com.sun.tools.javac.util.Context,
> java.io.PrintWriter, java.io.PrintWriter, java.io.PrintWriter)'
> at org.netbeans.lib.nbjavac.services.NBLog.(NBLog.java:55)
> at org.netbeans.lib.nbjavac.services.NBLog.(NBLog.java:40)
> at org.netbeans.lib.nbjavac.services.NBLog$1.make(NBLog.java:73)
> at org.netbeans.lib.nbjavac.services.NBLog$1.make(NBLog.java:70) {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5884) Jackpot doesn't work on JDK 17
[ https://issues.apache.org/jira/browse/NETBEANS-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5884: -- Affects Version/s: 12.3 > Jackpot doesn't work on JDK 17 > -- > > Key: NETBEANS-5884 > URL: https://issues.apache.org/jira/browse/NETBEANS-5884 > Project: NetBeans > Issue Type: Bug > Components: java - Compiler >Affects Versions: 12.3 >Reporter: Jaroslav Tulach >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5884) Jackpot doesn't work on JDK 17
[ https://issues.apache.org/jira/browse/NETBEANS-5884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5884: -- Component/s: java - Compiler > Jackpot doesn't work on JDK 17 > -- > > Key: NETBEANS-5884 > URL: https://issues.apache.org/jira/browse/NETBEANS-5884 > Project: NetBeans > Issue Type: Bug > Components: java - Compiler >Reporter: Jaroslav Tulach >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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] [Created] (NETBEANS-5884) Jackpot doesn't work on JDK 17
Jaroslav Tulach created NETBEANS-5884: - Summary: Jackpot doesn't work on JDK 17 Key: NETBEANS-5884 URL: https://issues.apache.org/jira/browse/NETBEANS-5884 Project: NetBeans Issue Type: Bug Reporter: Jaroslav Tulach -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5847) Allow headless NewFromTemplate for Maven project types
[ https://issues.apache.org/jira/browse/NETBEANS-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach updated NETBEANS-5847: -- Summary: Allow headless NewFromTemplate for Maven project types (was: Allow headless NewFromTemplate) > Allow headless NewFromTemplate for Maven project types > -- > > Key: NETBEANS-5847 > URL: https://issues.apache.org/jira/browse/NETBEANS-5847 > Project: NetBeans > Issue Type: Bug > Components: projects - Maven >Affects Versions: 12.5 >Reporter: Svatopluk Dedic >Assignee: Svatopluk Dedic >Priority: Major > Fix For: Next > > > Gradle allows to use 'new from template' features in a headless environment, > i.e. when running as a LSP server. Maven *WizardIterators* in > *org.netbeans.modules.maven.newproject.idenative* could be turned into > *CreateFromTemplateHandlers* similar to how Gradle iterator was done in > [PR-2999|https://github.com/apache/netbeans/pull/2999] > -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5829) Incorrect "Text blocks aren't supported"
[
https://issues.apache.org/jira/browse/NETBEANS-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach updated NETBEANS-5829:
--
Description:
Get
[https://github.com/apache/netbeans-html4j/blob/release-1.7.2/json-tck/src/main/java/net/java/html/js/tests/AsyncJavaScriptAction.java#L36],
open it in most recent NetBeans IDE running on JDK8 (with nbjavac@16.0.0.0
installed) and try to convince the editor to not show errors about text blocks:
!image-2021-07-02-08-47-25-560.png!
Is there some way to do so? It is very annoying to have the source tree full of
useless errors related to text blocks, when everything compiles and runs fine.
The project's source level is set to 15 and Maven support shall report that to
{{java.source}}. Any help welcomed.
was:
Get
[https://github.com/apache/netbeans-html4j/blob/release-1.7.2/json-tck/src/main/java/net/java/html/js/tests/AsyncJavaScriptAction.java#L36],
open it in most recent NetBeans IDE running on JDK8 (with nbjavac@16.0.0.0
installed) and try to convince the editor to not show errors about text blocks:
!image-2021-07-02-08-47-25-560.png!
Is there some way to do so? It is very annoying to have the source tree full of
useless errors related to text blocks, when everything compiles and runs fine.
Any help welcomed.
> Incorrect "Text blocks aren't supported"
>
>
> Key: NETBEANS-5829
> URL: https://issues.apache.org/jira/browse/NETBEANS-5829
> Project: NetBeans
> Issue Type: Bug
> Components: java - Source
>Reporter: Jaroslav Tulach
>Assignee: Jan Lahoda
>Priority: Major
> Attachments: image-2021-07-02-08-47-25-560.png
>
>
> Get
> [https://github.com/apache/netbeans-html4j/blob/release-1.7.2/json-tck/src/main/java/net/java/html/js/tests/AsyncJavaScriptAction.java#L36],
> open it in most recent NetBeans IDE running on JDK8 (with nbjavac@16.0.0.0
> installed) and try to convince the editor to not show errors about text
> blocks:
> !image-2021-07-02-08-47-25-560.png!
> Is there some way to do so? It is very annoying to have the source tree full
> of useless errors related to text blocks, when everything compiles and runs
> fine. The project's source level is set to 15 and Maven support shall report
> that to {{java.source}}. Any help welcomed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Created] (NETBEANS-5829) Incorrect "Text blocks aren't supported"
Jaroslav Tulach created NETBEANS-5829: - Summary: Incorrect "Text blocks aren't supported" Key: NETBEANS-5829 URL: https://issues.apache.org/jira/browse/NETBEANS-5829 Project: NetBeans Issue Type: Bug Components: java - Source Reporter: Jaroslav Tulach Assignee: Jan Lahoda Attachments: image-2021-07-02-08-47-25-560.png Get [https://github.com/apache/netbeans-html4j/blob/release-1.7.2/json-tck/src/main/java/net/java/html/js/tests/AsyncJavaScriptAction.java#L36], open it in most recent NetBeans IDE running on JDK8 (with nbjavac@16.0.0.0 installed) and try to convince the editor to not show errors about text blocks: !image-2021-07-02-08-47-25-560.png! Is there some way to do so? It is very annoying to have the source tree full of useless errors related to text blocks, when everything compiles and runs fine. Any help welcomed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5768) Gradle projects with settings.gradle but not build.gradle are not recognized
[ https://issues.apache.org/jira/browse/NETBEANS-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach resolved NETBEANS-5768. --- Fix Version/s: 12.5 Resolution: Fixed The [PR-3028|https://github.com/apache/netbeans/pull/3028] has just been integrated. > Gradle projects with settings.gradle but not build.gradle are not recognized > > > Key: NETBEANS-5768 > URL: https://issues.apache.org/jira/browse/NETBEANS-5768 > Project: NetBeans > Issue Type: Improvement > Components: projects - Gradle >Affects Versions: 12.4 > Environment: Gradle 7.0.2 > NetBeans 12.4 > OpenJDK 16 >Reporter: Scott Palmer >Assignee: Jaroslav Tulach >Priority: Major > Labels: pull-request-available > Fix For: 12.5 > > Time Spent: 1h > Remaining Estimate: 0h > > Running "gradle init" to initialize a new Java application project will make > a project structure with a few sub projects (application and libraries), but > no build.gradle file in the root. It just has the settings.gradle file that > points to the sub-projects. > NetBeans project open dialog does not recognize the root folder as a project. > A simple work around is to make an empty build.gradle file in the root folder > of the project, but NetBeans should be able to handle this valid project > structure, particularly since it is the "default" structure coming from > "gradle init" -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5802) Gradle project wizard should use gradle init
[
https://issues.apache.org/jira/browse/NETBEANS-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17367344#comment-17367344
]
Jaroslav Tulach commented on NETBEANS-5802:
---
One problem discovered. The project generated by {{gradle init}} doesn't have
{{build.gradle}} in the root! There is only {{settings.gradle}}
{code:java}
settings.gradle
app/build.gradle
app/src/ {code}
which includes the {{app}} subproject. The IDE should be changed to recognize
{{settings.gradle}} as a Gradle project. That'd be simple. However I am not
sure what'd be the consequences of doing so.
> Gradle project wizard should use gradle init
>
>
> Key: NETBEANS-5802
> URL: https://issues.apache.org/jira/browse/NETBEANS-5802
> Project: NetBeans
> Issue Type: Improvement
> Components: projects - Gradle
>Affects Versions: 12.3
>Reporter: Jaroslav Tulach
>Assignee: Laszlo Kishalmi
>Priority: Major
>
> Hello Laszlo. As soon as I implemented the [VSCode project
> wizard|https://github.com/apache/netbeans/pull/2999] I got following feedback:
> {quote}The New Java Project wizard uses an unusual Gradle template with an
> older deprecated plugins syntax and jacoco included for some reason.
> To make this feature maintainable we should instead use the existing "gradle
> init" functionality:
> {code:java}
> gradle init --type java-application --test-framework junit-jupiter --dsl
> groovy --package com.example --project-name example
> {code}
> {quote}
> Shall we switch the new project in NetBeans to use the above given command?
> Do you want to do it? Or shall I do it?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Created] (NETBEANS-5802) Gradle project wizard should use gradle init
Jaroslav Tulach created NETBEANS-5802:
-
Summary: Gradle project wizard should use gradle init
Key: NETBEANS-5802
URL: https://issues.apache.org/jira/browse/NETBEANS-5802
Project: NetBeans
Issue Type: Improvement
Components: projects - Gradle
Affects Versions: 12.3
Reporter: Jaroslav Tulach
Assignee: Laszlo Kishalmi
Hello Laszlo. As soon as I implemented the [VSCode project
wizard|https://github.com/apache/netbeans/pull/2999] I got following feedback:
{quote}The New Java Project wizard uses an unusual Gradle template with an
older deprecated plugins syntax and jacoco included for some reason.
To make this feature maintainable we should instead use the existing "gradle
init" functionality:
{code:java}
gradle init --type java-application --test-framework junit-jupiter --dsl groovy
--package com.example --project-name example
{code}
{quote}
Shall we switch the new project in NetBeans to use the above given command? Do
you want to do it? Or shall I do it?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Created] (NETBEANS-5738) Cannot debug jtreg tests unless java.base project is open
Jaroslav Tulach created NETBEANS-5738:
-
Summary: Cannot debug jtreg tests unless java.base project is open
Key: NETBEANS-5738
URL: https://issues.apache.org/jira/browse/NETBEANS-5738
Project: NetBeans
Issue Type: Bug
Components: java - Project
Affects Versions: 12.4
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
I've tried it in VSNetBeans, but I assume similar problem will happen with
NetBeans IDE as well. Follow the instructions for scenario 3 - e.g. OpenJDK -
at [wiki
page|https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+extension+for+Visual+Studio+Code].
Make sure *jtreg* support is enabled.
Open for example
{{test/jdk/java/lang/annotation/AnnotationType/AnnotationTypeRuntimeAssumptionTest.java}}
and debug it. It doesn't work - first of all one has to open {{src/java.base}}
is project. That's unfortunate, and especially in VSNetBeans, not very
intuitive.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Created] (NETBEANS-5703) Can we pass in -Djava.security.manager=allow?
Jaroslav Tulach created NETBEANS-5703:
-
Summary: Can we pass in -Djava.security.manager=allow?
Key: NETBEANS-5703
URL: https://issues.apache.org/jira/browse/NETBEANS-5703
Project: NetBeans
Issue Type: Sub-task
Components: platform - Module System
Reporter: Jaroslav Tulach
Assignee: Jan Lahoda
[JEP-411|https://openjdk.java.net/jeps/411] suggests to pass enable security
manager on when launching the Java process via:
{quote}enabled on the command line, via {{java -Djava.security.manager}} or
{{java -Djava.security.manager=...}}, then issue a warning message at startup.
{quote}
Does that work? E.g. can NetBeans 12.4 be launched with such option?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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] [Assigned] (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 reassigned NETBEANS-5689:
-
Assignee: Jaroslav Tulach
> 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
>
> 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.3.4#803005)
-
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-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 updated NETBEANS-5689:
--
Description:
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}
was:
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:
$ ./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|system.java:394])
at
org.netbeans.TopSecurityManager.install([TopSecurityManager.java:525|topsecuritymanager.java:525])
at
org.netbeans.core.NbLifecycleManager.advancePolicy([NbLifecycleManager.java:69|nblifecyclemanager.java:69])
at
org.netbeans.core.GuiRunLevel.run([GuiRunLevel.java:84|guirunlevel.java:84])
at org.netbeans.core.startup.Main.start([Main.java:295|main.java:295])
at
org.netbeans.core.startup.TopThreadGroup.run([TopThreadGroup.java:98|topthreadgroup.java:98])
at java.base/java.lang.Thread.run([Thread.java:833|thread.java:833])
> 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
>Priority: Blocker
>
> 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.3.4#803005)
-
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-5680) Create ProjectActions API
[ https://issues.apache.org/jira/browse/NETBEANS-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17345927#comment-17345927 ] Jaroslav Tulach commented on NETBEANS-5680: --- I agree that the mixing of [API|http://wiki.apidesign.org/wiki/APIvsSPI] in *ActionProvider* is a real problem. Another thing that bothers me when working with *ActionProvider* is the difference between working with regular NetBeans actions and project actions. My preferred API for both would be [ContextAwareAction|https://bits.netbeans.org/12.3/javadoc/org-openide-util-ui/org/openide/util/ContextAwareAction.html] - e.g. have a way to obtain *BUILD*, *RUN*, *DEBUG* project actions as *ContextAwareAction* instances and then just prepare *Lookup* for them (including instance of ***Project*, *FileObject*, etc.) and invoke them. Consistency achieved. Helper methods possible. > Create ProjectActions API > - > > Key: NETBEANS-5680 > URL: https://issues.apache.org/jira/browse/NETBEANS-5680 > Project: NetBeans > Issue Type: Improvement > Components: projects - Generic Infrastructure >Affects Versions: 12.4 >Reporter: Svatopluk Dedic >Priority: Major > Labels: VSNetBeans > > In [https://github.com/apache/netbeans/pull/2948] surfaced a long-standing > issue, that clients are asked to use a SPI interface directly. This > complicates adding optional functionaliy to SPI as it requires *API clients* > to maneuver around old/new SPI impl differences. > A proper API counterpart for *ActionProvider*, *ActionProgress* (and maybe > *ProjectConfiguration*) should be created. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5674) Add mode disable project in tab projects.
[ https://issues.apache.org/jira/browse/NETBEANS-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach resolved NETBEANS-5674. --- Fix Version/s: 8.2 Resolution: Not A Problem Right click empty space in project tab: !image-2021-05-14-08-27-40-931.png! choose Project Groups. Then create/modify and switch between your groups as you need. > Add mode disable project in tab projects. > - > > Key: NETBEANS-5674 > URL: https://issues.apache.org/jira/browse/NETBEANS-5674 > Project: NetBeans > Issue Type: New Feature > Components: apisupport - Project, projects - Generic Infrastructure, > projects - Generic Projects UI >Affects Versions: 12.4, 12.5 >Reporter: Sergei Korenevkiy >Assignee: Sergei Korenevkiy >Priority: Major > Labels: disable, project-explorer, project-options, projectmgr > Fix For: 8.2 > > Attachments: NetBeans_VisualStudio.png, NetBeans_VisualStudio3.png > > Original Estimate: 672h > Remaining Estimate: 672h > > Welcome. > Please add the option to deactivate the project or disable the project. Just > like it works in Visual Studio. There is an option to turn off the project. > I have a lot of projects in NetBeans. Periodically, I conduct work with 6 > work projects. Each project has open files. > Add the ability to disable and enable projects, so that after enabling them, > the working files of each project are automatically opened for editing. > !NetBeans_VisualStudio.png! > . > !NetBeans_VisualStudio3.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-5629) Gradle project Lookups ordering not defined well
[
https://issues.apache.org/jira/browse/NETBEANS-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17338403#comment-17338403
]
Jaroslav Tulach commented on NETBEANS-5629:
---
No, not yet. {{position}} has always been internal to individual lookup
implementations. But it could be conditionally exposed, I think.
> Gradle project Lookups ordering not defined well
>
>
> Key: NETBEANS-5629
> URL: https://issues.apache.org/jira/browse/NETBEANS-5629
> Project: NetBeans
> Issue Type: Bug
>Reporter: Svatopluk Dedic
>Priority: Major
>
> Individual Plugins can contribute to project Lookup. In my testcase, which
> uses java/java-base plugins, the Lookups loaded from
> *Projects/org-netbeans-modules-gradle/*** were loaded in the following order:
> {code:java}
> [java, , root, java-base, base]
> {code}
> When Groovy was also present, the order was
> {code:java}
> [java, groovy, , root, groovy-base, java-base, base]
> {code}
> (note - groovy after java, groovy-base before java-base). But with scala, the
> order is:
> {code:java}
> [java, scala, , root, java-base, scala-base, base]
> {code}
> (note - scala-base AFTER java-base).
> When opening a project with
> {code:java}
> apply plugin: 'groovy'
> {code}
> the order is yet different:
> {code:java}
> [groovy, java, , root, groovy-base, java-base, base]{code}
> The order is unreliable and I guess under some circumstances even the
> , xxx-base and xxx could be reordered as plugin names go through
> series of hashmaps.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5629) Gradle project Lookups ordering not defined well
[
https://issues.apache.org/jira/browse/NETBEANS-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337941#comment-17337941
]
Jaroslav Tulach commented on NETBEANS-5629:
---
{quote}[~jtulach] - what do you think: shouldn't we use the MimeLookup-like
composition for plugin-implied services ?
{quote}
Sure, if existing implementation works for your case, then use it! MimeLookup
implementation is in the platform already. It is no longer tight to editor and
it doesn't have to be tight to MIME types.
You can also enhance {{ProxyLookup}} to honor {{position}} value of the
{{Lookup.Item }} instances it delegates to, if you think it would fix your
problem.
> Gradle project Lookups ordering not defined well
>
>
> Key: NETBEANS-5629
> URL: https://issues.apache.org/jira/browse/NETBEANS-5629
> Project: NetBeans
> Issue Type: Bug
>Reporter: Svatopluk Dedic
>Priority: Major
>
> Individual Plugins can contribute to project Lookup. In my testcase, which
> uses java/java-base plugins, the Lookups loaded from
> *Projects/org-netbeans-modules-gradle/*** were loaded in the following order:
> {code:java}
> [java, , root, java-base, base]
> {code}
> When Groovy was also present, the order was
> {code:java}
> [java, groovy, , root, groovy-base, java-base, base]
> {code}
> (note - groovy after java, groovy-base before java-base). But with scala, the
> order is:
> {code:java}
> [java, scala, , root, java-base, scala-base, base]
> {code}
> (note - scala-base AFTER java-base).
> When opening a project with
> {code:java}
> apply plugin: 'groovy'
> {code}
> the order is yet different:
> {code:java}
> [groovy, java, , root, groovy-base, java-base, base]{code}
> The order is unreliable and I guess under some circumstances even the
> , xxx-base and xxx could be reordered as plugin names go through
> series of hashmaps.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5638) NbTestCase.assertGC fails with SecurityException
[
https://issues.apache.org/jira/browse/NETBEANS-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337102#comment-17337102
]
Jaroslav Tulach commented on NETBEANS-5638:
---
Ignoring {{SecurityException}} in Insane seems to be the cheapest fix.
> NbTestCase.assertGC fails with SecurityException
>
>
> Key: NETBEANS-5638
> URL: https://issues.apache.org/jira/browse/NETBEANS-5638
> Project: NetBeans
> Issue Type: Bug
> Components: apisupport - Harness
>Affects Versions: 12.4
>Reporter: Svatopluk Dedic
>Assignee: Svatopluk Dedic
>Priority: Major
> Labels: Testing, pull-request-available
> Fix For: 12.5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During testing, I've found out that *assertGC* paths to root analysis fails
> with *SecurityException* and does not provide any reasonable results:
> {code:java}
> java.lang.SecurityException: Prohibited package name: java.lang
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:655)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:754)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.getDeclaredMethods(Class.java:1975)
> at
> org.netbeans.insane.impl.InsaneEngine.recognizeClass(InsaneEngine.java:123)
> {code}
> The exception was thrown, because Insane library queries
> *getDeclaredMethods()* on *org.netbeans.NbInstrumentation* - the whole heap
> traversal then fails, since on JDK8 Module is not loaded from runtime, and an
> attempt to load it from boot.jar fails.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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-5613) Support for OSGi modules on Classpath (tests primarily)
[
https://issues.apache.org/jira/browse/NETBEANS-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17331184#comment-17331184
]
Jaroslav Tulach commented on NETBEANS-5613:
---
The NetBeans module system handles classloaders and "other things". The module
system understands OSGi bundles, but leaves the semantic to some OSGi container
(Felix or Equinox/NetBinox). When loading (so called "fixed" modules) from
classpath, the module system handles only the "other things".
It is the responsibility of the application writer to setup classpath
correctly. E.g. modules on classpath should thus be processed only due to
"other things" - classloading, "wiring", etc. should be left out.
Treat the OSGI bundles on classpath as regular JARs without talking to OSGi
container at all.
> Support for OSGi modules on Classpath (tests primarily)
> ---
>
> Key: NETBEANS-5613
> URL: https://issues.apache.org/jira/browse/NETBEANS-5613
> Project: NetBeans
> Issue Type: Improvement
> Components: platform - Module System
>Reporter: Svatopluk Dedic
>Assignee: Jaroslav Tulach
>Priority: Major
>
> Tests compose their execution environment on the classpath; if module system
> is triggered (i.e. by a Lookup for Module or ModuleInfo, core loads happily
> NB modules from the classpath. But does not load OSGi modules.
> Subsequently, NB modules that depends on those won't be 'initialized'
> although they are well part of and their code can be
> actually executed.
> Modules tha are OSGi in the current distribution are:
>
> {code:java}
> Bundle-SymbolicName: com.fasterxml.jackson.core.jackson-annotations
> Bundle-SymbolicName: com.fasterxml.jackson.core.jackson-core
> Bundle-SymbolicName: com.fasterxml.jackson.core.jackson-databind
> Bundle-SymbolicName: com.fasterxml.jackson.dataformat.jackson-dataformat
> Bundle-SymbolicName: com.googlecode.javaewah.JavaEWAH
> Bundle-SymbolicName: com.google.guava
> Bundle-SymbolicName: com.jcraft.jzlib
> Bundle-SymbolicName: com.sun.jersey.core
> Bundle-SymbolicName: com.sun.jna
> Bundle-SymbolicName: com.sun.jna.platform
> Bundle-SymbolicName: groovy
> Bundle-SymbolicName: groovy-ant
> Bundle-SymbolicName: javax.annotation-api
> Bundle-SymbolicName: javax.servlet-api
> Bundle-SymbolicName: javax.servlet.jsp.jstl-api
> Bundle-SymbolicName: javax.validation.api
> Bundle-SymbolicName: javax.ws.rs-api
> Bundle-SymbolicName: javax.xml
> Bundle-SymbolicName: javax.xml.soap-api
> Bundle-SymbolicName: jaxb-api
> Bundle-SymbolicName: jaxb-api
> Bundle-SymbolicName: joda-time
> Bundle-SymbolicName: junit-jupiter-api
> Bundle-SymbolicName: junit-jupiter-engine
> Bundle-SymbolicName: junit-jupiter-params
> Bundle-SymbolicName: net.java.html
> Bundle-SymbolicName: net.java.html.boot
> Bundle-SymbolicName: net.java.html.boot.fx
> Bundle-SymbolicName: net.java.html.boot.script
> Bundle-SymbolicName: net.java.html.geo
> Bundle-SymbolicName: net.java.html.json
> Bundle-SymbolicName: net.java.html.sound
> Bundle-SymbolicName: org.apache.commons.beanutils
> Bundle-SymbolicName: org.apache.commons.chain
> Bundle-SymbolicName: org.apache.commons.codec
> Bundle-SymbolicName: org.apache.commons.commons-fileupload
> Bundle-SymbolicName: org.apache.commons.io
> Bundle-SymbolicName: org.apache.commons.logging
> Bundle-SymbolicName: org.apache.felix.main
> Bundle-SymbolicName: org.apache.xmlrpc
> Bundle-SymbolicName: org.eclipse.core.jobs; singleton:=true
> Bundle-SymbolicName: org.eclipse.core.runtime.compatibility.auth
> Bundle-SymbolicName: org.eclipse.core.runtime; singleton:=true
> Bundle-SymbolicName: org.eclipse.equinox.common; singleton:=true
> Bundle-SymbolicName: org.eclipse.equinox.registry;singleton:=true
> Bundle-SymbolicName: org.eclipse.equinox.security;singleton:=true
> Bundle-SymbolicName: org.eclipse.mylyn.bugzilla.core;singleton:=true
> Bundle-SymbolicName: org.eclipse.mylyn.tasks.core;singleton:=true
> Bundle-SymbolicName: org.eclipse.mylyn.wikitext.confluence.core;single
> Bundle-SymbolicName: org.eclipse.mylyn.wikitext.markdown.core;singleto
> Bundle-SymbolicName: org.eclipse.osgi; singleton:=true
> Bundle-SymbolicName: org.glassfish.hk2.api
> Bundle-SymbolicName: org.glassfish.hk2.external.asm-all-repackaged
> Bundle-SymbolicName: org.glassfish.hk2.external.cglib
> Bundle-SymbolicName: org.glassfish.hk2.external.javax.inject
> Bundle-SymbolicName: org.glassfish.hk2.locator
> Bundle-SymbolicName: org.glassfish.hk2.osgi-resource-locator
> Bundle-SymbolicName: org.glassfish.hk2.utils
> Bundle-SymbolicName: org.glassfish.javax.el
> Bundle-SymbolicName: org.glassfish.javax.faces
> Bundle-SymbolicName: org.glassfish.jersey.containers.jersey-container-se
> Bundle-SymbolicName: org.glassfish.jersey.core.jersey-client
> Bundle-SymbolicName: org.glassfish.jersey.core.jersey-common
[jira] [Commented] (NETBEANS-5598) IllegalAccessException on running Netbeans Platform Application in JDK 16
[
https://issues.apache.org/jira/browse/NETBEANS-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325865#comment-17325865
]
Jaroslav Tulach commented on NETBEANS-5598:
---
It would be great to have a .travis build testing on JDK16 - looks like the
16th JDK is significantly different to previous ones and many unit tests are
likely to fail.
> IllegalAccessException on running Netbeans Platform Application in JDK 16
> -
>
> Key: NETBEANS-5598
> URL: https://issues.apache.org/jira/browse/NETBEANS-5598
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 12.3, 12.4
>Reporter: Sandeep Mishra
>Priority: Major
>
> Create or Open an existing Netbeans Platform Application.
> Run the application with Java Platform set to JDK 16.
> The following exception occurs:
> {code:java}
> java.lang.IllegalAccessException: class org.netbeans.Module cannot access a
> member of class java.lang.ClassLoader (in module java.base) with modifiers
> "protected"
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:385)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:687)
> at java.base/java.lang.reflect.Method.invoke(Method.java:559) [catch] at
> org.netbeans.Module.findResources(Module.java:571) at
> org.netbeans.core.startup.NbInstaller.loadLayers(NbInstaller.java:605) at
> org.netbeans.core.startup.NbInstaller.loadImpl(NbInstaller.java:332) at
> org.netbeans.core.startup.NbInstaller.access$000(NbInstaller.java:77) at
> org.netbeans.core.startup.NbInstaller$1.run(NbInstaller.java:322) at
> org.openide.filesystems.FileUtil$2.run(FileUtil.java:413) at
> org.openide.filesystems.EventControl.runAtomicAction(EventControl.java:102)
> at org.openide.filesystems.FileSystem.runAtomicAction(FileSystem.java:494) at
> org.openide.filesystems.FileUtil.runAtomicAction(FileUtil.java:397) at
> org.openide.filesystems.FileUtil.runAtomicAction(FileUtil.java:417) at
> org.netbeans.core.startup.NbInstaller.load(NbInstaller.java:319) at
> org.netbeans.ModuleManager.enable(ModuleManager.java:1453) at
> org.netbeans.ModuleManager.enable(ModuleManager.java:1254) at
> org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:315) at
> org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:251) at
> org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:298) at
> org.netbeans.core.startup.Main.getModuleSystem(Main.java:156) at
> org.netbeans.core.startup.Main.getModuleSystem(Main.java:125) at
> org.netbeans.core.startup.Main.start(Main.java:282) at
> org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98) at
> java.base/java.lang.Thread.run(Thread.java:831) {code}
> This is happening because access to JDK Internals has been disallowed from
> JDK 16 onwards.
> https://openjdk.java.net/jeps/396
> It used to show a warning in earlier JDK versions.
> There are few other places where the Netbeans Platform is hacking into JDK
> internals:
>
> {code:java}
> WARNING: Illegal reflective access by
> org.netbeans.modules.debugger.ui.views.debugging.DebugTreeView
>
> (jar:file:/Users/albatem/netbeans-12.3/ide/modules/org-netbeans-spi-debugger-ui.jar!/)
>
> to field javax.swing.tree.FixedHeightLayoutCache.info
> at
>
> org.netbeans.modules.debugger.ui.views.debugging.DebugTreeView.clearSelectionCache(DebugTreeView.java:150)
> at
>
> org.netbeans.modules.debugger.ui.views.debugging.DebugTreeView.resetSelection(DebugTreeView.java:140)
> at
>
> org.netbeans.modules.debugger.ui.views.debugging.DebuggingViewComponent.releaseTreeView(DebuggingViewComponent.java:661)
> at
>
> org.netbeans.modules.debugger.ui.views.debugging.DebuggingViewComponent.access$600(DebuggingViewComponent.java:104)
> at
>
> org.netbeans.modules.debugger.ui.views.debugging.DebuggingViewComponent$4.run(DebuggingViewComponent.java:423)
>
> WARNING: Illegal reflective access by org.openide.text.QuietEditorPane$1
>
> (jar:file:/Users/albatem/netbeans-12.3/platform/modules/org-openide-text.jar!/)
>
> to field sun.awt.im.InputContext.inputMethodWindowContext
> at org.openide.text.QuietEditorPane$1.run(QuietEditorPane.java:268)
> at
> org.openide.text.QuietEditorPane.removeNotify(QuietEditorPane.java:308)
>
>
> WARNING: Illegal reflective access by
> org.netbeans.modules.debugger.ui.views.debugging.DebugTreeView
>
> (jar:file:/Users/albatem/netbeans-12.3/ide/modules/org-netbeans-spi-debugger-ui.jar!/)
>
> to field javax.swing.tree.FixedHeightLayoutCache.info
> at
>
> org.netbeans.modules.debugger.ui.views.debugging.DebugTreeView.clearSelectionCache(DebugTreeView.java:150)
> at
>
>
[jira] [Closed] (NETBEANS-2847) PHP feature is not activated after Oracle JS Parser Implementation is installed
[ https://issues.apache.org/jira/browse/NETBEANS-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaroslav Tulach closed NETBEANS-2847. - Fix Version/s: 12.0 Resolution: Fixed I believe this is related to downloading the JS parser. However at least since 12.0 the UPL licensed parser is normally present in the download of NetBeans and there shall be no problem activating it. > PHP feature is not activated after Oracle JS Parser Implementation is > installed > --- > > Key: NETBEANS-2847 > URL: https://issues.apache.org/jira/browse/NETBEANS-2847 > Project: NetBeans > Issue Type: Bug > Components: ide - UI >Affects Versions: 11.1 > Environment: NAME="Ubuntu" > VERSION="18.04.2 LTS (Bionic Beaver)" > ID=ubuntu > ID_LIKE=debian > PRETTY_NAME="Ubuntu 18.04.2 LTS" > VERSION_ID="18.04" > HOME_URL="https://www.ubuntu.com/; > SUPPORT_URL="https://help.ubuntu.com/; > BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; > PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; > VERSION_CODENAME=bionic > UBUNTU_CODENAME=bionic >Reporter: Jack J. Woehr >Assignee: Svatopluk Dedic >Priority: Major > Fix For: 12.0 > > Attachments: NETBEANS-2847.zip, log.txt, > netbeans-2847-screenshot-1.png > > > While re-opening a project that had been imported from previous version and > was marked "Broken". It re-opened and was no longer marked "broken", but then > this exception occurred. -- This message was sent by Atlassian Jira (v8.3.4#803005) - 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-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 resolved NETBEANS-3104. --- Fix Version/s: 12.2 Resolution: Fixed PR [https://github.com/openjfx/javafx-maven-archetypes/pull/8] is integrated. All good? > 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.3.4#803005) - 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-3101) Can't launch (and connect) NetBeans from node
[
https://issues.apache.org/jira/browse/NETBEANS-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaroslav Tulach resolved NETBEANS-3101.
---
Fix Version/s: 12.2
Resolution: Fixed
> Can't launch (and connect) NetBeans from node
> -
>
> Key: NETBEANS-3101
> URL: https://issues.apache.org/jira/browse/NETBEANS-3101
> Project: NetBeans
> Issue Type: Bug
> Components: platform - LaunchersCLI
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Minor
> Fix For: 12.2
>
>
>
> I am trying to connect to a *NetBeans* based application from _Visual Studio_
> - aka _Electron_ - aka *node*. Somehow the *node* mangles network setup and
> the InetAddress.getHostAddress() isn't the same. To reproduce create
> following structure of files:
> {code:java}
> $ ls -l | cut -c50-
> dump.hprof
> nb.js
> nb.sh
> netbeans -> /home/devel/bin/netbeans/bin/netbeans
> $ cat nb.sh
> ./netbeans 'dump.hprof'
> $ cat nb.js
> var exec = require("child_process").execFile;
> let path = './netbeans';let vvm = exec(path, [ 'dump.hprof' ]){code}
> Then start *./netbeans* on background and wait for the GUI to launch. Then do
> following from command line:
> {code:java}
> ./jvm.sh
> {code}
> The dump.hprof file opens in the the GUI. Close it and try the same via
> *node.js*:
> {code:java}
> node ./jvm.js
> {code}
> The heap dump isn't shown (on my computer), rather a warning dialog appears.
> Result of node and shell script disagreeing on what is local host address.
> One is using IPv6 and one IPv4.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
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
