title: how to get over these maven/m2eclipse issues
body: <p>(first, I admit, I have no love for maven/m2eclipse, but it wouldn't be that bad if I could figure out how to overcome these issues)</p>
  
  <p>I am using maven/m2eclipse.  m2eclipse is the only good way I know of to suck in the maven jars.  Some of these may not have solutions(but I am hoping to be surprised).  Maybe solving #9 solves them all?</p>
  
  <p>ISSUES</p>
  
  <ol>
  <li><p>When I run "mvn clean package", I am dead in the water as far as running a unit test in eclipse while maven is building as I LOVE to multitask but maven prevents me here.  How to get around this?</p></li>
  <li><p>I move eclipse to point to eclipsegen/classes but then the unit tests are still using the classes in target/classes so it's not using my latest code that I just edited in eclipse and debugging is not lining up and it's stepping on blank lines that don't have code.</p></li>
  <li><p>If I just slightly touch the pom.xml, bam, it builds when I don't really want it to and turning of automatic builds did not seem to help.  </p></li>
  <li><p>On top of #3, I get random pom builds downloading jars which just freezes eclipse from doing anything why the jars are being downloaded(I am a bit multitasker so this frustrates me to no end)</p></li>
  <li><p>If I want to modify or do something really custom I need, the answer is usually create a java plugin but this then would require me to create another source control project with another automated build making sure the build tags all versions so we can reproduce issues with certain versions.  (in ant, I just modify the xml to do custom stuff).</p></li>
  <li><p>(I hear there is a bug open for 5 years on this one).  global exclusions because people on our project keep breaking stuff when they include new things that depend on log4j and sucking that library in breaks us so we want to globally exclude it so people stop breaking the project when adding new things (IVY has global exclusions, why doesn't maven!!!!)</p></li>
  <li><p>The xml code for generation from an xsd in maven is about 2-3 times the code of doing it in ant.  Why is this?  That really shouldn't be the case I think.</p></li>
  <li><p>Running my unit test says xxxx-12.0.8-SNAPSHOT is missing but in my pom.xml it clearly says 12.0.9-SNAPSHOT not .8.  ie. m2eclipse gets into some weird state and I get screwed wasting yet more time because someone selected maven</p></li>
  <li><p>(I don't like IvyDE for the same reasons I don't like m2eclipse).  In maven, is there any way like in Ivy to say on a build MOVE ALL jars into target/lib so that I can uninstall m2eclipse(if maven had this one feature, I think all my problems might go away)....That IS AN Ivy feature that rocks by the way!!!!
  NOTE: I just realized that uninstalling m2eclipse and running "mvn eclipse:clean eclipse:eclipse" is not really an option since on this project I had to import 30 projects.  I think on single projects, that is a great solution.</p></li>
  <li><p>Is there no way like ant to log the command that was run for debugging purposes? ( <a href="https://stackoverflow.com/questions/10259918/in-maven-how-to-log-the-command-that-was-run">in maven how to log the command that was run?</a> )</p></li>
  </ol>
  
  <p>I should really look into gradle(I hear it's best of maven and ant) as the theory of maven sounded great but you can tell there was a lot of controversy over it(which usually indicates a bad tool).  Good tools that really help typically do have some controversy, but not as much as maven has had so it makes me think twice as I don't want to screw the guy who takes over my project(and I know ant will work).  Many people I think don't even consider that.  They think "I am fine, so why won't the next guy be fine".</p>
  
  <p>Any ideas on how to fix the above issues?</p>