Hi Eugene, Thanks for your response. Could you tell me if you have any plans to add this feature? It would be great if the 'Update Source Folders' option could make use of other projects in the workspace. I have soem code generation taking place which forms part of my build process. Therefore everytime some configuration files are changed I'm required to re-run the code generation -> it would be great if I could just click on the 'Update Source Folders' option and have that triggered as part of the standard Maven lifecycle without having to (re)install any other projects that may have changed.
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-tp16335325s177p16349037.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
