| Issue 169: | Allow the user to control which dependencies can be resolved from the workspace | |
| 7 people starred this issue and may be notified of changes. | Back to list |
For some use cases, it is not desirable to resolve every project from the workspace. It should be possible to disable this. Ideally it would be possible to set this globally (never resolve from workspace) and locally (for this project, don't resolve this dependency from the workspace). This information can be also read from the <useProjectReferences>false</ useProjectReferences> configuration of the maven-eclipse-plugin. |
|
,
May 16, 2008
that's a very good idea. instead, I think it could be better to disable the workspace dependencies resolution by default, what i think is the normal state of a maven project (that's we expect in most cases), and if u want to refer to any workspace project, simply be able to do it through project configuration. |
|
,
May 16, 2008
Could you bring this topic to the mailing list? Workspace dependency resolution is the "core" of all eclipse-maven integration efforts, so it's quite surprising to hear that. |
|
,
May 16, 2008
i sent a post: http://groups.google.com/group/q4e-users/browse_thread/thread/935e65e06ee8b848# |
|
,
Jun 12, 2008
I think marco.madrid gets the point. usually you are working in a enterprise project where many developers participate. You don't want to be working with your local version of other modules of the project that other developers could have updated previously. It's desirable to work with all latest module versions. If anyone wants the other functionality, maybe can be selected by a check in project maven plugin options, but not as a default behaviour (this can drive into errors) |
|
 Sign in to add a comment
|
