Todd Thiessen wrote:
Is there a way to disable workspace resolution globally instead of one
project at a time? This is related to
http://jira.codehaus.org/browse/MNGECLIPSE-1224. I would like to turn
this off completely so this error no longer occurs.
Further, is this feature a good idea? The reason why I question it is
because it makes the IDE work differently than the command line. For
instance, you can run a maven command from the IDE and it could resolve
some dependencies via a project imported into your workspace. However,
this command would fail from the command line since these dependencies
wouldn't be resovled.
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.
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.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
