If project B depends on project A and project A gets moved/renamed outside of
the IDE, upon reload project B is marked as having broken references
and the Fix References(?) action and dialog aids in resolving these.

However, the same doesn't extend to suite projects. 
And sometimes even B's broken references don't manifest themselves in the UI.

For example, create a suite and two NB module projects under it, A and B.
Create a couple of dummy classes.
Make B depend on A and call A from B to make the dependency real.
Now exit the IDE. 
'mv' (rename) A to C.
Restart IDE. 

It will load the suite and B but naturally won't load A.
Now, often B will be marked as having problems with references
and you will get a popup telling you to use the project action
ResolveReferences.

I started filing this bug initially because the suite
wouldn't get marked as having reference problems, even though it's
nproject/project.properties has a reference to A. An attempt
to build the suite just gives an obscure build error.

But as I played with a trivial testcase (attached) I noticed that
even B isn't always marked as a project with broken references, even
though it's nbproject/project.xml still refers to A. So
building it also gives obscure error messages.

So whether a project, regular or suite, is marked as having broken references
seems rather unpredictable.

I've attached a directory, SuiteRefBugSuite. It's a suite with two
sub-projects A and B. Load it as is, get it to build.
Then exit the IDE, and rename A to C. Restart the IDE and
witness what I described above.