[
https://issues.apache.org/jira/browse/NETBEANS-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194363#comment-17194363
]
Ernie Rael commented on NETBEANS-4765:
--------------------------------------
I see at least two goals
# Provide common API for new development
# Refactor code to use common API
I guess I was thinking of 1, but since probably the best way to do 1, is first
do 2. As "eliminate the duplicities" points out.
> 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: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
