[jira] [Comment Edited] (NETBEANS-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193999#comment-17193999
]
Jaroslav Tulach edited comment on NETBEANS-4765 at 9/11/20, 5:40 AM:
-
Right, you can only eliminate the duplicities by introducing an API, CCing
Tomáš Zezula.
was (Author: jtulach):
Right you can only eliminate the duplicities by introducing an API, CCing Tomáš
Zezula.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193999#comment-17193999
]
Jaroslav Tulach commented on NETBEANS-4765:
---
Right you can only eliminate the duplicities by introducing an API, CCing Tomáš
Zezula.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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] [Created] (NETBEANS-4792) Opening a javafx project does not enable "JavaFX 2" plugin/feature.
Ernie Rael created NETBEANS-4792: Summary: Opening a javafx project does not enable "JavaFX 2" plugin/feature. Key: NETBEANS-4792 URL: https://issues.apache.org/jira/browse/NETBEANS-4792 Project: NetBeans Issue Type: Bug Components: javafx - Project Reporter: Ernie Rael Some javafx project related menu items, for example "NewFile>JavaFX>..." are not available unless the NetBeans standard "JavaFX 2" plugin is enabled. Shouldn't this be done automatically? Ergonomics? -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4790: - Description: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated * Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate [NETBEANS-4765] is loosly related. was: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate [NETBEANS-4765] is loosly related. > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > * Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4791) error badges for xxx.fxml file do not propogate to tabs or project window
Ernie Rael created NETBEANS-4791: Summary: error badges for xxx.fxml file do not propogate to tabs or project window Key: NETBEANS-4791 URL: https://issues.apache.org/jira/browse/NETBEANS-4791 Project: NetBeans Issue Type: Bug Components: javafx - Editor Reporter: Ernie Rael To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Edit primary.fxml (If there are no error badges, create an error. For example change the controller name) * Observe the editor shows an error, neither the tab nor the file in project window shows an error This can be particularly important for finding errors that will show up at runtime, since flaws elsewhere in NetBeans can cause errors in this file when doing seemingly unrelated actions. See NETBEANS-4789, NETBEANS-4790. -- 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-3147) design view fails to load
[ https://issues.apache.org/jira/browse/NETBEANS-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193909#comment-17193909 ] Junichi Yamamoto commented on NETBEANS-3147: Could someone please provide an _example_ project to reproduce it with details(steps to reproduce it)? > design view fails to load > - > > Key: NETBEANS-3147 > URL: https://issues.apache.org/jira/browse/NETBEANS-3147 > Project: NetBeans > Issue Type: Bug > Components: java - Source >Affects Versions: 11.0 >Reporter: Larry Ashworth >Priority: Minor > Attachments: ide.log > > > This project worked properly in 8.2 > This issue only occurred on the first attempt to install 11.0 > The second attempt worked. Difficult for newbies to 11.0 > -- 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-3147) design view fails to load
[ https://issues.apache.org/jira/browse/NETBEANS-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junichi Yamamoto updated NETBEANS-3147: --- Component/s: (was: apisupport - Project) java - Source > design view fails to load > - > > Key: NETBEANS-3147 > URL: https://issues.apache.org/jira/browse/NETBEANS-3147 > Project: NetBeans > Issue Type: Bug > Components: java - Source >Affects Versions: 11.0 >Reporter: Larry Ashworth >Priority: Minor > Attachments: ide.log > > > This project worked properly in 8.2 > This issue only occurred on the first attempt to install 11.0 > The second attempt worked. Difficult for newbies to 11.0 > -- 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-4765) module-info utilities for common usage
[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193904#comment-17193904
]
Ernie Rael commented on NETBEANS-4765:
--
[~jtulach] I guess this is an API issue.
> module-info utilities for common usage
> --
>
> Key: NETBEANS-4765
> URL: https://issues.apache.org/jira/browse/NETBEANS-4765
> Project: NetBeans
> Issue Type: Improvement
> Components: java - Platform
>Reporter: Ernie Rael
>Priority: Major
>
> The only common api I've seen for working with module-info is
> {code:java}
> org.netbeans.api.java.source.SourceUtils{.parseModuleName,.getModuleName*}
> {code}
> There are several other things that need to be done with module-info. For
> example, adding a package for fxml access, or for refactoring when moving an
> exported java class to a different package.
> There are module-info utilities scattered throughout the netbeans codebase.
> For example
> {code:java}
> ./maven/src/org/netbeans/modules/maven/api/ModuleInfoUtils.java
> ./maven/src/org/netbeans/modules/maven/ModuleInfoSupport.java
> {code}
> and there's a pending fix for NETBEANS-4718 which adds a local
> "hasModuleInfo".
> And notice sitting in .../netbeans/java there are 64 files given by
> {code}
> srcgrep -l module-info | grep -E -v '/test/|/build/'
> {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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193903#comment-17193903 ] Ernie Rael commented on NETBEANS-4790: -- This issue only addresses refactor>move. Are there other refactoring issues related to maintaining module-info.java? > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193901#comment-17193901 ] Ernie Rael commented on NETBEANS-4790: -- [~jlahoda] any thoughts on how this might be addressed? > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4790: - Description: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate [NETBEANS-4765] is loosly related. was: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate > [NETBEANS-4765] is loosly related. -- 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-4790) refactor move class to new package doesn't update module-info.java
[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernie Rael updated NETBEANS-4790: - Description: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate was: This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate > refactor move class to new package doesn't update module-info.java > -- > > Key: NETBEANS-4790 > URL: https://issues.apache.org/jira/browse/NETBEANS-4790 > Project: NetBeans > Issue Type: Bug > Components: java - Refactoring >Reporter: Ernie Rael >Priority: Major > Labels: modularization > > This requires a java version supporting java modules. This is *not* a javafx > only problem, but javafx provides a convenient example. Note that controllers > in javafx that are referenced from xxx.fxml files must be export for > reflection > To recreate > * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) > * Open module-info.java > Observe the package containing the controller is exported to javafx.fxml > * PrimaryController.java Refactor>Move to another package > (May make App.java's setRoot public) > Observe no warning that PrimaryController is no longer acessible and/or that > module-info.java has not been updated > *Before the move, PrimaryController was available for reflection from > javafx.fxml, after the move it is not. > A warning and/or checkbox to update module-info.java so the class may still > be accessed through reflection seems appropriate -- 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-4790) refactor move class to new package doesn't update module-info.java
Ernie Rael created NETBEANS-4790: Summary: refactor move class to new package doesn't update module-info.java Key: NETBEANS-4790 URL: https://issues.apache.org/jira/browse/NETBEANS-4790 Project: NetBeans Issue Type: Bug Components: java - Refactoring Reporter: Ernie Rael This requires a java version supporting java modules. This is *not* a javafx only problem, but javafx provides a convenient example. Note that controllers in javafx that are referenced from xxx.fxml files must be export for reflection To recreate * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon) * Open module-info.java Observe the package containing the controller is exported to javafx.fxml * PrimaryController.java Refactor>Move to another package (May make App.java's setRoot public) Observe no warning that PrimaryController is no longer acessible and/or that module-info.java has not been updated *Before the move, PrimaryController was available for reflection from javafx.fxml, after the move it is not. A warning and/or checkbox to update module-info.java so the class may still be accessed through reflection seems appropriate -- 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-4789) fxml controller rename does not update reference in xxx.fxml
[
https://issues.apache.org/jira/browse/NETBEANS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4789:
-
Labels: (was: modular)
> fxml controller rename does not update reference in xxx.fxml
>
>
> Key: NETBEANS-4789
> URL: https://issues.apache.org/jira/browse/NETBEANS-4789
> Project: NetBeans
> Issue Type: Bug
> Components: java - Refactoring, javafx - Project
>Reporter: Ernie Rael
>Priority: Major
>
> To recreate
> * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> * Open PrimaryController.java and primary.fxml
> Observe in primary.fxml the reference, note that line is without error
> {code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
> * In PrimaryController.java, Refactor>Rename the class (stay in same package)
> Observe in primary.fxml that the reference is not updated
> (Also notice that the editor now flags that line as an error)
--
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-4789) fxml controller rename does not update reference in xxx.fxml
[
https://issues.apache.org/jira/browse/NETBEANS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ernie Rael updated NETBEANS-4789:
-
Labels: modular (was: )
> fxml controller rename does not update reference in xxx.fxml
>
>
> Key: NETBEANS-4789
> URL: https://issues.apache.org/jira/browse/NETBEANS-4789
> Project: NetBeans
> Issue Type: Bug
> Components: java - Refactoring, javafx - Project
>Reporter: Ernie Rael
>Priority: Major
> Labels: modular
>
> To recreate
> * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> * Open PrimaryController.java and primary.fxml
> Observe in primary.fxml the reference, note that line is without error
> {code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
> * In PrimaryController.java, Refactor>Rename the class (stay in same package)
> Observe in primary.fxml that the reference is not updated
> (Also notice that the editor now flags that line as an error)
--
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-4789) fxml controller rename does not update reference in xxx.fxml
[
https://issues.apache.org/jira/browse/NETBEANS-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193881#comment-17193881
]
Ernie Rael commented on NETBEANS-4789:
--
[~jlahoda] Perhaps you have some idea on how this might be addressed?
> fxml controller rename does not update reference in xxx.fxml
>
>
> Key: NETBEANS-4789
> URL: https://issues.apache.org/jira/browse/NETBEANS-4789
> Project: NetBeans
> Issue Type: Bug
> Components: java - Refactoring, javafx - Project
>Reporter: Ernie Rael
>Priority: Major
>
> To recreate
> * NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
> * Open PrimaryController.java and primary.fxml
> Observe in primary.fxml the reference, note that line is without error
> {code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
> * In PrimaryController.java, Refactor>Rename the class (stay in same package)
> Observe in primary.fxml that the reference is not updated
> (Also notice that the editor now flags that line as an error)
--
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-4789) fxml controller rename does not update reference in xxx.fxml
Ernie Rael created NETBEANS-4789:
Summary: fxml controller rename does not update reference in
xxx.fxml
Key: NETBEANS-4789
URL: https://issues.apache.org/jira/browse/NETBEANS-4789
Project: NetBeans
Issue Type: Bug
Components: java - Refactoring, javafx - Project
Reporter: Ernie Rael
To recreate
* NewProject > JavaWithMaven > FXML JavaFX Maven Archetype (Gluon)
* Open PrimaryController.java and primary.fxml
Observe in primary.fxml the reference, note that line is without error
{code}fx:controller="com.raelity.play.jfx.fxml1.PrimaryController"{code}
* In PrimaryController.java, Refactor>Rename the class (stay in same package)
Observe in primary.fxml that the reference is not updated
(Also notice that the editor now flags that line as an error)
--
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-4773) NPE on GradleCompilerOptionsQuery
[ https://issues.apache.org/jira/browse/NETBEANS-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi resolved NETBEANS-4773. --- Fix Version/s: 12.2 Resolution: Fixed > NPE on GradleCompilerOptionsQuery > - > > Key: NETBEANS-4773 > URL: https://issues.apache.org/jira/browse/NETBEANS-4773 > Project: NetBeans > Issue Type: Bug >Reporter: Laszlo Kishalmi >Assignee: Laszlo Kishalmi >Priority: Major > Fix For: 12.2 > > Time Spent: 20m > Remaining Estimate: 0h > > On strange occasions GradleCompilerOptionsQuery can throw an NPE on > missing/renamed SourceSets -- 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-4788) NPE on editing code out of gradle project scope
[ https://issues.apache.org/jira/browse/NETBEANS-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi resolved NETBEANS-4788. --- Resolution: Duplicate Well the fix for NETBEANS-4773 just has been merged. > NPE on editing code out of gradle project scope > --- > > Key: NETBEANS-4788 > URL: https://issues.apache.org/jira/browse/NETBEANS-4788 > Project: NetBeans > Issue Type: Bug > Components: projects - Gradle > Environment: Product Version: Apache NetBeans IDE DEV (Build > dev-12d0e2d43f10e70cdc90c26e3b65d0aa946282e3) > Java: 13.0.1; Java HotSpot(TM) 64-Bit Server VM 13.0.1+9 >Reporter: mkhramov >Assignee: Laszlo Kishalmi >Priority: Major > > Steps to reproduce: > Open gradle project > Perform some Usages search in project so Usages View is opened with some > contents > Close project (all opened classes are closed) > Now open file from usages View and try to edit it > the NPE is thrown: > java.lang.NullPointerException > at > org.netbeans.modules.gradle.java.queries.GradleCompilerOptionsQuery.getOptions(GradleCompilerOptionsQuery.java:68) > at > org.netbeans.modules.java.project.ProjectCompilerOptionsQueryImplementation.lambda$getOptions$1(ProjectCompilerOptionsQueryImplementation.java:38) > at java.base/java.util.Optional.map(Optional.java:258) > at > org.netbeans.modules.java.project.ProjectCompilerOptionsQueryImplementation.getOptions(ProjectCompilerOptionsQueryImplementation.java:38) > at > org.netbeans.api.java.queries.CompilerOptionsQuery.getOptions(CompilerOptionsQuery.java:58) > at > org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:795) > at > org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:409) > at > org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:391) > at > org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:492) > at > org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:145) > at > org.netbeans.modules.parsing.impl.TaskProcessor.callGetResult(TaskProcessor.java:608) > at > org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:239) > 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] [Created] (NETBEANS-4788) NPE on editing code out of gradle project scope
mkhramov created NETBEANS-4788: -- Summary: NPE on editing code out of gradle project scope Key: NETBEANS-4788 URL: https://issues.apache.org/jira/browse/NETBEANS-4788 Project: NetBeans Issue Type: Bug Components: projects - Gradle Environment: Product Version: Apache NetBeans IDE DEV (Build dev-12d0e2d43f10e70cdc90c26e3b65d0aa946282e3) Java: 13.0.1; Java HotSpot(TM) 64-Bit Server VM 13.0.1+9 Reporter: mkhramov Assignee: Laszlo Kishalmi Steps to reproduce: Open gradle project Perform some Usages search in project so Usages View is opened with some contents Close project (all opened classes are closed) Now open file from usages View and try to edit it the NPE is thrown: java.lang.NullPointerException at org.netbeans.modules.gradle.java.queries.GradleCompilerOptionsQuery.getOptions(GradleCompilerOptionsQuery.java:68) at org.netbeans.modules.java.project.ProjectCompilerOptionsQueryImplementation.lambda$getOptions$1(ProjectCompilerOptionsQueryImplementation.java:38) at java.base/java.util.Optional.map(Optional.java:258) at org.netbeans.modules.java.project.ProjectCompilerOptionsQueryImplementation.getOptions(ProjectCompilerOptionsQueryImplementation.java:38) at org.netbeans.api.java.queries.CompilerOptionsQuery.getOptions(CompilerOptionsQuery.java:58) at org.netbeans.modules.java.source.parsing.JavacParser.createJavacTask(JavacParser.java:795) at org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:409) at org.netbeans.modules.java.source.parsing.CompilationInfoImpl.getJavacTask(CompilationInfoImpl.java:391) at org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:492) at org.netbeans.modules.java.source.parsing.JavacParser.getResult(JavacParser.java:145) at org.netbeans.modules.parsing.impl.TaskProcessor.callGetResult(TaskProcessor.java:608) at org.netbeans.modules.parsing.impl.SourceCache.getResult(SourceCache.java:239) 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] [Created] (NETBEANS-4787) Manual FTP Upload/Download Not Working from Projects Panel
Robert Peters created NETBEANS-4787: --- Summary: Manual FTP Upload/Download Not Working from Projects Panel Key: NETBEANS-4787 URL: https://issues.apache.org/jira/browse/NETBEANS-4787 Project: NetBeans Issue Type: Bug Affects Versions: 12.0 Environment: Windows 10 Reporter: Robert Peters Just today the Upload and Download menu items in the context menu for Projects window stopped being available options. They are grayed out as though unavailable. Manually testing the configuration is successful as is the automatic upload on save. However, this retards the ability to download fresh versions from the server. -- 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-3147) design view fails to load
[ https://issues.apache.org/jira/browse/NETBEANS-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193711#comment-17193711 ] Louis Shankle commented on NETBEANS-3147: - The issue continues in releases 11.1, 11.2, and 11.3. I did not look at 12.0. > design view fails to load > - > > Key: NETBEANS-3147 > URL: https://issues.apache.org/jira/browse/NETBEANS-3147 > Project: NetBeans > Issue Type: Bug > Components: apisupport - Project >Affects Versions: 11.0 >Reporter: Larry Ashworth >Priority: Minor > Attachments: ide.log > > > This project worked properly in 8.2 > This issue only occurred on the first attempt to install 11.0 > The second attempt worked. Difficult for newbies to 11.0 > -- 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-3194) Fxml autocomplete doesnt work
[ https://issues.apache.org/jira/browse/NETBEANS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193669#comment-17193669 ] David Kopp edited comment on NETBEANS-3194 at 9/10/20, 3:11 PM: The editor will also work if you set the compiler source level to 8 in your maven POM. Setting source level to 9 or higher causes this error. So, a workaround, at least for maven projects, is to temporarily set the source level to 8, work on your .fxml file, and then set the source level back to what it is supposed to be. You might have to restart NetBeans somewhere in there. It would be better for this to be fixed. was (Author: koppdk): The editor will also work if you set the compiler source level to 8 in your maven POM. Setting source level to 9 or higher causes this error. > Fxml autocomplete doesnt work > - > > Key: NETBEANS-3194 > URL: https://issues.apache.org/jira/browse/NETBEANS-3194 > Project: NetBeans > Issue Type: Bug > Components: cnd - Code Completion >Affects Versions: 11.1 >Reporter: sebo Zoltan >Priority: Minor > Attachments: FXMLDocument.fxml, messages.log > > > Fxml code completation is not working is giving an error (used jdk 10.0.2) > java.lang.AssertionError > at com.sun.tools.javac.util.Assert.error(Assert.java:155) > at com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) > at com.sun.tools.javac.comp.Modules.allModules(Modules.java:1254) > at > com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126) > at > org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:48) > at > org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:640) > at > org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:144) > at org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:120) > at > org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.(PropertyCompleter.java:57) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.createCompleter(PropertyCompleter.java:232) > at > org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.createCompleter(InstanceCompleter.java:92) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.createCompleter(PropertyCompleter.java:46) > at > org.netbeans.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:185) > 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.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:159) > 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
[jira] [Commented] (NETBEANS-3194) Fxml autocomplete doesnt work
[ https://issues.apache.org/jira/browse/NETBEANS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193669#comment-17193669 ] David Kopp commented on NETBEANS-3194: -- The editor will also work if you set the compiler source level to 8 in your maven POM. Setting source level to 9 or higher causes this error. > Fxml autocomplete doesnt work > - > > Key: NETBEANS-3194 > URL: https://issues.apache.org/jira/browse/NETBEANS-3194 > Project: NetBeans > Issue Type: Bug > Components: cnd - Code Completion >Affects Versions: 11.1 >Reporter: sebo Zoltan >Priority: Minor > Attachments: FXMLDocument.fxml, messages.log > > > Fxml code completation is not working is giving an error (used jdk 10.0.2) > java.lang.AssertionError > at com.sun.tools.javac.util.Assert.error(Assert.java:155) > at com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) > at com.sun.tools.javac.comp.Modules.allModules(Modules.java:1254) > at > com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126) > at > org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:48) > at > org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:640) > at > org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:144) > at org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:120) > at > org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.(PropertyCompleter.java:57) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.createCompleter(PropertyCompleter.java:232) > at > org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.createCompleter(InstanceCompleter.java:92) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.createCompleter(PropertyCompleter.java:46) > at > org.netbeans.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:185) > 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.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:159) > 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.modules.javafx2.editor.FXMLCompletion2$Q.query(FXMLCompletion2.java:106) > at > org.netbeans.spi.editor.completion.support.AsyncCompletionTask.run(AsyncCompletionTask.java:198) > at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418) > at > org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45) > at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278) > [catch] at >
[jira] [Commented] (NETBEANS-3194) Fxml autocomplete doesnt work
[ https://issues.apache.org/jira/browse/NETBEANS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193665#comment-17193665 ] David Kopp commented on NETBEANS-3194: -- This bug is being caused by the module system. I can open a Maven project in Netbeans 12, which is running on JDK 11, and the editor will work if the project is set to compile with JDK 8. Please fix this, because I really need to edit FXML files directly, and this bug is making it impossible. > Fxml autocomplete doesnt work > - > > Key: NETBEANS-3194 > URL: https://issues.apache.org/jira/browse/NETBEANS-3194 > Project: NetBeans > Issue Type: Bug > Components: cnd - Code Completion >Affects Versions: 11.1 >Reporter: sebo Zoltan >Priority: Minor > Attachments: FXMLDocument.fxml, messages.log > > > Fxml code completation is not working is giving an error (used jdk 10.0.2) > java.lang.AssertionError > at com.sun.tools.javac.util.Assert.error(Assert.java:155) > at com.sun.tools.javac.util.Assert.checkNonNull(Assert.java:62) > at com.sun.tools.javac.comp.Modules.allModules(Modules.java:1254) > at > com.sun.tools.javac.model.JavacElements.getAllModuleElements(JavacElements.java:126) > at > org.netbeans.modules.java.source.ElementUtils.getTypeElementByBinaryName(ElementUtils.java:48) > at > org.netbeans.api.java.source.ElementHandle.getTypeElementByBinaryName(ElementHandle.java:640) > at > org.netbeans.api.java.source.ElementHandle.resolveImpl(ElementHandle.java:144) > at org.netbeans.api.java.source.ElementHandle.resolve(ElementHandle.java:120) > at > org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.(InstanceCompleter.java:54) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.(PropertyCompleter.java:57) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.createCompleter(PropertyCompleter.java:232) > at > org.netbeans.modules.javafx2.editor.completion.impl.InstanceCompleter.createCompleter(InstanceCompleter.java:92) > at > org.netbeans.modules.javafx2.editor.completion.impl.PropertyCompleter.createCompleter(PropertyCompleter.java:46) > at > org.netbeans.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:185) > 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.modules.javafx2.editor.FXMLCompletion2$Q$Task.run(FXMLCompletion2.java:159) > 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.modules.javafx2.editor.FXMLCompletion2$Q.query(FXMLCompletion2.java:106) > at > org.netbeans.spi.editor.completion.support.AsyncCompletionTask.run(AsyncCompletionTask.java:198) > at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418) > at >
[jira] [Updated] (NETBEANS-4786) unable to install Hibernate in Netbeans 12
[ https://issues.apache.org/jira/browse/NETBEANS-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chellappa updated NETBEANS-4786: Component/s: javaee - Hibernate > unable to install Hibernate in Netbeans 12 > -- > > Key: NETBEANS-4786 > URL: https://issues.apache.org/jira/browse/NETBEANS-4786 > Project: NetBeans > Issue Type: Bug > Components: javaee - Hibernate >Affects Versions: 12.0 >Reporter: Chellappa >Priority: Major > Attachments: rsz_screenshot_from_2020-09-10_16-57-12.png > > > I unable to install Hibernate plugin . I already install freeMaker plugin . > please fix this bug -- 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-4786) unable to install Hibernate in Netbeans 12
Chellappa created NETBEANS-4786: --- Summary: unable to install Hibernate in Netbeans 12 Key: NETBEANS-4786 URL: https://issues.apache.org/jira/browse/NETBEANS-4786 Project: NetBeans Issue Type: Bug Affects Versions: 12.0 Reporter: Chellappa Attachments: rsz_screenshot_from_2020-09-10_16-57-12.png I unable to install Hibernate plugin . I already install freeMaker plugin . please fix this bug -- 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-4785) ParserManager.parseWhenScanFinished asserts on missing parser
Svatopluk Dedic created NETBEANS-4785:
-
Summary: ParserManager.parseWhenScanFinished asserts on missing
parser
Key: NETBEANS-4785
URL: https://issues.apache.org/jira/browse/NETBEANS-4785
Project: NetBeans
Issue Type: Bug
Components: editor - Parsing Indexing
Affects Versions: 11.3
Reporter: Svatopluk Dedic
I happened to forget install nb-javac in testing installation. When I run some
actions the following error was thrown in the output window:
{code:java}
java.lang.AssertionErrorjava.lang.AssertionError at
org.netbeans.modules.parsing.api.ParserManager$MimeTaskAction.(ParserManager.java:347)
at
org.netbeans.modules.parsing.api.ParserManager.parseWhenScanFinished(ParserManager.java:334)
at
org.netbeans.api.java.source.SourceUtils.waitScanFinished(SourceUtils.java:787)
at
org.netbeans.modules.java.source.usages.BuildArtifactMapperImpl$DefaultCompileOnSaveAction.performSync(BuildArtifactMapperImpl.java:732)
at
org.netbeans.modules.java.source.usages.BuildArtifactMapperImpl$DefaultCompileOnSaveAction.performAction(BuildArtifactMapperImpl.java:649)
at
org.netbeans.modules.java.preprocessorbridge.api.CompileOnSaveActionQuery$ProxyAction.lambda$performAction$3(CompileOnSaveActionQuery.java:130)
at java.util.Optional.map(Optional.java:215) at
org.netbeans.modules.java.preprocessorbridge.api.CompileOnSaveActionQuery$ProxyAction.performAction(CompileOnSaveActionQuery.java:128)
at
org.netbeans.modules.java.source.usages.BuildArtifactMapperImpl.ensureBuilt(BuildArtifactMapperImpl.java:166)
at
org.netbeans.modules.java.source.ant.TranslateClassPath.translateEntry(TranslateClassPath.java:130)
at
org.netbeans.modules.java.source.ant.TranslateClassPath.translate(TranslateClassPath.java:91)
at
org.netbeans.modules.java.source.ant.TranslateClassPath.execute(TranslateClassPath.java:80)
{code}
{{ParserManager.findParser() returned null for }}{{text/x-java}} and MimeTask
asserted in its constructor.
[~tzezula] please suggest on the desired behaviour on missing parser:
* behave as if scanning finished, run the task immediately, or
* throw a ParseException (what to wrap inside)
Thanks
--
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
