You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Matthew Phillips (Jira)" <ji...@apache.org> on 2020/12/17 11:04:00 UTC

[jira] [Created] (NETBEANS-5165) Project dependencies are not found

Matthew Phillips created NETBEANS-5165:
------------------------------------------

             Summary: Project dependencies are not found
                 Key: NETBEANS-5165
                 URL: https://issues.apache.org/jira/browse/NETBEANS-5165
             Project: NetBeans
          Issue Type: Bug
          Components: java - Compiler
    Affects Versions: 12.0
         Environment: Windows 10 (Home, build 10.0.18363 Build 18363)
            Reporter: Matthew Phillips


This is a tough one to reproduce (cannot seem to reset the system to what it was prior to a Netbeans install - more about that later), but happens in situations where there are multiple projects each with multiple modules. Essentially when importing a Maven (POM) based Java project, then selecting all the modules in each project and opening them (so that types show up when pressing CTRL-O), there are dependency issues.

These dependency issues occur even between two different modules within the same project. Basically imports cannot be found. Clearing the cache does not help. Reinstalling the Netbeans application does not help (along with clearing the cache). In fact in this latter scenario (uninstalling and clearing cache), it seems that Netbeans already knows about my project when reinstalled. How can that be if everything has been cleared / uninstalled? Where does Netbeans keep its internal / system files if not in the cache or project?

Sharing code here will not really illustrate the problem, but would be happy to do an interactive screen share session with one of your developers if required to demonstrate the issue.

All these dependency issues happen between different source code packages / directories (as opposed to JAR files or other external libraries). Another example of where this happens is where I have a test class in the same package, but different directory, as the class that's being tested (i.e. no import statement should be required in the test class). The test class cannot see the class it's supposed to be testing.

Also, I see no Netbeans specific project files (eg. nbbuild). Can I assume that, for Maven based project, Netbeans relies on solely on POM files to define the project?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists