Product Version = NetBeans IDE 8.1 RC2 (Build 201510122201)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0_60
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.60-b23

Reproducibility: Happens sometimes, but not always

STEPS:
  * I have a Maven project, one module of many.  This module depends on other modules that *have not been built yet*
  * Earlier versions of siblings may have been built.  This usually happens when someone else does a maven release and I pull in the changes that have bumped the version numbers in the POMs
  * On the package declaration line it is highlighted in yellow with the hint indicating: "Missing mandatory Classpath entries. Resolve Project Problems."
  * Activating the hint brings up a "Resolve Project Problems" dialog where there are no problems listed.

ACTUAL:
    The project builds fine when building from the parent POM and does not actually have any problems.  NetBeans appears to be confused because sibling projects are not built yet.
   After running mvn install on the parent POM so all the modules are built, the warning/hint goes away.

EXPECTED:
  The Hint/Warning from NetBeans is wrong.  It should be smart enough to know that the missing dependencies are sibling projects as referenced in the modules section of the parent pom.  The hint should say to build the other modules.