title: Maven project imported to eclipse from git is missing "Maven Dependencies" library
body: <p>Using latest Oxygen.</p>
  
  <p>I started working on a new Maven project that was initialized from a template.  I cloned the git repo in Eclipse and built it successfully from the command line (outside of eclipse).</p>
  
  <p>I then right-clicked on the repo and selected "Import Projects" and let it import the one project.  When it finished, it definitely knew it was a Java project, and a Maven project. The "M" and "J" are in the icon.  It set my existing src/main/java and src/test/java trees as source directories.  The project context menu has a "Maven" menu with expected menu items.</p>
  
  <p>However, even after Eclipse finished building, there were many errors in the project.  I noticed that in the Package Explorer, the lines in the project that represent "library" entries had the "JRE System Library" and "Referenced Libraries", but it didn't have the "Maven Dependencies" entry that I see in other Maven projects that don't have this problem.</p>
  
  <p>Confirming this, in the "Java Build Path" section of the project properties, the "Libraries" tab just has the "JRE System Library", but not the "Maven Dependencies" entry.</p>
  
  <p>Looking in the .classpath file, I don't see any mention of Maven at all.  In working Maven projects, I see the "maven.pomderived" property throughout that file.</p>
  
  <p>Also note that when I saw these symptoms after the first import, I then deleted the project and then reimported it a different way, from the main "Import" menu and selecting "Existing Maven Projects".  The result was the same.</p>
  
  <p>What can I do here?</p>
  
  <p><strong>Update</strong>:</p>
  
  <p>I tried deleting the project, not the contents, and then manually deleting the .classpath, .project, and .settings, then reimporting as "Existing Maven Projects".</p>
  
  <p>The result is a Maven project, not a Java project.  The icon has the "M", not the "J", and it doesn't have a Java builder.</p>
  
  <p>I tried doing "Update Project".  No change.</p>
  
  <p>I've imported many Maven projects, even in this same Eclipse instance and workspace, using the same strategy, and I've never seen this problem.</p>
  
  <p><strong>Update</strong>:</p>
  
  <p>Technically, I've solved the problem, but not in the way I really wanted.</p>
  
  <p>I simply compared the .project and .classpath files with a working Maven project, and I hand-edited the files to reflect what the working project was doing.  It's now all working fine.  I hope I don't have to do this again.</p>