title: EasyMock / PowerMock import question
body: <p>I'm experiencing some problems I can't quite figure out, and one site I found suggested a problem with incompatibilities with verify() if the mocks were created with PowerMock.</p>
  
  <p>When I type a line to create a mock, Eclipse is telling me the method is ambiguous, and I end up having to specify it as EasyMock.createMock or PowerMock.createMock.</p>
  
  <p>I had originally just started with EasyMock and then switched to PowerMock. Does the order of import statements matter, and if you're using PowerMock is it important not to include certain EasyMock stuff?</p>
  
  <p>Here's what I've got:</p>
  
  <pre><code>import org.easymock.EasyMock;  
  import org.junit.*;  
  import org.junit.runner.RunWith;  
  
  import static org.easymock.EasyMock.*;  
  import static org.powermock.api.easymock.PowerMock.*;  
  import org.powermock.reflect.Whitebox;  
  import org.powermock.api.easymock.*;  
  import org.powermock.api.easymock.PowerMock.*;  
  import org.powermock.api.mockito.expectation.*;  
  import org.powermock.api.mockito.*;  
  import org.powermock.api.support.membermodification.*;  
  import org.powermock.api.support.membermodification.MemberMatcher.*;  
  import org.powermock.core.classloader.annotations.*;  
  import org.powermock.modules.junit4.*;  
  </code></pre>
  
  <p>There may be some redundancies there. Is a conflict possible? And is the order important in order to eliminate the ambiguity?</p>
  
  <p>Thanks.</p>
  
  <p>Craig</p>