jitv wrote:
Thanks for the workaround. It would be great if you could add workspace
resolution to the 'Update Source Folders' process. I've created a Jira issue
for you to track this enhancement.
http://jira.codehaus.org/browse/MNGECLIPSE-508
Appreciate that. It would also help us to save some time at the
acceptance testing if you'd also provide simple project for this issue.
If anyone is interested to look at this issue, please let me know. I'd
be happy to give some pointers. Otherwise it won't be the highest priority.
Thanks
regards,
Eugene
Eugene Kuleshov wrote:
I have two maven projects in eclipse:
Project A -> A standalone project.
Project B -> refers to 'Project A' as a dependency.
Within Eclipse everything seems to work fine: 'Project B' correctly
resolves
its reference to 'Project A' without having to build/install 'Project A'
into my local repo. However when I make use of the 'Update Source
Folders'
option in the Maven context menu, I always get an error stating that
'Project A' cannot be found in the local repo - is there any way to get
this
to work with the workspace resolution
Jit, please open a jira issue for this.
As a workaround you could run Maven install on Project A, so update
source folders on Project B will pass.
Thanks
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
