Eclipse IAM and Maven resolving dependency not listed in pom.xml
===

I have two Java projects:  Child and Parent with Child depending on Parent. 
 
I used [Eclipse Integration for Apache Maven plugin (IAM)][1] to convert these Java projects to Maven projects.  I ran Maven Build using "clean install" goals on both projects, starting with the Parent and I see artifacts being deployed to my local repository.  Great.

Then, I opened pom.xml of Child and expected to find the dependency to Parent listed in there but is not, yet Child project builds successfully, as indicated in the output console.  So, how did this happen ... how did Maven find this dependency without an explicit entry in pom.xml, even after it removed the classpathentry to Parent in .classpath  do this?  Does it just quietly look in my local repository as a last resort?

Also, if I open the code editor to edit a class in Child that depends on Parent, I get resolution errors, which will probably be fixed if I add this dependency into the child's pom.  Is this not what IAM should have done? 

  [1]: http://maven.apache.org/eclipse-plugin.html