Hi Eugene, 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 Regards Jit Eugene Kuleshov wrote: > > jitv 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 > > > > -- View this message in context: http://www.nabble.com/Update-Source-Folders-won%27t-use-workspace-resolution-tp16335325s177p16349656.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
