>
> The version must also match. If you refer to a project and the version
> doesn't match the version in your workspace then m2eclipse will use
> normal Maven resolution which is checking your local and then remote
> versions.
>
Yeah the versions match :)
>
> Maven is not m2eclipse. The Maven CLI is not going to be able to build
> anything if you don't have it installed. The CLI and m2eclipse's
> operation inside Eclipse are two separate things.
So when, in Eclipse, I do:
Run As -> Maven Build
Is that invoking the CLI or is m2eclipse doing the work? If it's
actually invoking the CLI, then that's the reason, but if m2eclipse is
doing the work, I would expect it to find my workspace dependencies
during the build. (Which it's not)
Does that make sense?
Thanks again,
Lincoln
