title: Preventing m2e from un-exporting Maven dependencies on project update
body: <p>I am looking at using Maven projects in Eclipse 4.2 to allow non-Maven Java projects in my workspace to use external libraries with less maintenance effort. To achieve this effect, I enable the <code>Maven Dependencies</code> check-box under the <code>Java Build Path -&gt; Order and Export</code> tab.</p>
  
  <p>I have noticed, however, that updating the Maven project changes that setting back. More specifically, in <code>.classpath</code> this:</p>
  
  <pre><code>&lt;classpathentry exported="true" kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER"&gt;
  </code></pre>
  
  <p>turns into this:</p>
  
  <pre><code>&lt;classpathentry kind="con" path="org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER"&gt;
  </code></pre>
  
  <p>Is there a way to prevent this from happening? The whole point of having Maven projects in my case is that their dependencies would be exported.</p>
  
  <p>Is there a better way to do this, except for converting all other projects to Maven?</p>