title: How to (safely) remove unnecessary Maven dependencies in Eclipse?
body: <p>I'm working on a Java project in Eclipse, using Maven to build and manage dependencies. The project is spread across 5 Eclipse projects, one of those being the parent POM. I'm working on a server implementation that is based off of a much more complicated server that another team implemented. So I based my work off of their pre-existing code and POM files, and now have many unnecessary dependencies in the POMs across these Eclipse projects.</p>
  
  <p>Relatively speaking, I'm a Maven beginner, but I am familiar with this command:</p>
  
  <pre><code>mvn dependency:analyze
  </code></pre>
  
  <p>When I run this command using the Eclipse Maven plugin, I will get a long list of "Unused declared dependencies," but when I attempt to remove a few of them, my program will break, sometimes in mysterious ways.</p>
  
  <p>Is there a generally accepted, best-practices way to deal with this problem? Or am I resigned to removing these (probably) unused dependencies one-by-one, making sure nothing is broken after each one is removed?</p>