> When you work on a multi module project or when developing
> Maven plugins you really don't want to resolve cross-project
> dependencies from the local Maven repository. Otherwise you
> will have to run Maven / install action before any chances
> will be picked up and you won't be able to edit code directly
> when stopped in the debugger.
Understood. With the ability to install the source and javadoc to the
local repo, I didn't think this would of been too big of a deal. I agree
that it isn't as "nice" but I think it would of saved you and the m2e
team a lot of headaches and would of gotten the plugin to a 1.0 release
much more quickly. Once a stable release was achieved, this feature
could of been added to say 1.1.
Just my thoughts on how I may have approached it. Not meant to
discourage. I love the plugin ;-).
> I have to admit that it was a bold move from me to make the
> default shortcuts to inherit workspace resolution flag from
> the project settings, but for my defense some users actually
> requested that in jira.
> Perhaps we should revert that feature to the old behavior and
> maybe provide an additional configuration UI to allow to turn
> it on and off on the project level.
I think this would be wise. While your at it, add the ability to turn
workspace resoltion on/off globally and not just per project.
Thanks Eugene. Great work on this stuff.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
