I have the following project structure:
myproj
+---myproj-parent
+---myproj-data (war)
+---myproj-util
+---myproj-report (dependency on myproj-data)
I am able to "mvn clean install" the "myproj-data" and "myproj-util" projects and verify they are in my local repo by viewing the directories. In eclipse for the myproj-report pom.xml, I can also "right-click --> Maven --> Add Dependency", select both of them (e.g. "myproj-data-0.0.1-SNAPSHOT.war" and "myproj-util-0.0.1-SNAPSHOT.jar"), and everything up to this point seems is good.
The problem is that none of the classes in the myproj-data are available in myproj-report. That is, they all show the " cannot be resolved to a type" in eclipse, and produce the "package myproj.data.model.entity does not exist" and "cannot find symbol" errors when building from the command line. As best I can tell, the "myproj-data" and "myproj-util" projects are very similarly structured, with the only major differences being packaging type and several additional dependencies in myproj-data (for jpa and REST).
I have tried:
- clearing and rebuilding my local repo
- rebuilding and reinstalling the myprojc-data project (mvn clean install -U)
- removing and readding the myproj-data dependency
- deleting and recreating workspace
- removing and reimporting all projects (deleting .settings, target, .classpath, .project)
- triple checking versions, names, and everything else I can think of, etc..
...but I cannot figure out why the myproj-util dependencies are being recognized when the myproj-data are not.
How can I troubleshoot this?