That could potentially be the case - last time I used m2eclipse it was way too brittle and undependable, so I canned it.. Maven itself has a lot of classpath issues, and m2eclipse tends to aggrevate them by mixing it with the Eclipse classpath..
count.negative wrote:
ok, here in my office, everything works. I don't know why but it does. Maybe it's the m2eclipse plugin I've used. I'll try to reproduce it here.