[ https://issues.apache.org/jira/browse/NETBEANS-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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