konkere wrote:
i'm not stupid you know (and have you actually read the post?) ;). i've set my maven to be the default one (instead of embedded) right after i've installed m2eclipse.
Sorry, I read your email again and don't see where you say that you
did set external Maven as default. So, I don't really have any way to
guess if you did.
so that has nothing to do with the problem.
Good. We can isolate that one then.
The next suspect is workspace dependency resolution. For example, the
Maven ear plugin can't handle dependencies resolved from workspace. You
could try to create custom launch configuration and explicitly disable
workspace dependency resolution, that of course would require to have
all dependencies installed to the local Maven repository.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
