Description Auke van Leeuwen 2010-10-12 03:41:09 EDT

Build Identifier: 20100617-1415

I often have a maven multi-project structure as follows:

trunk
 + module-1
 + module-2

In the trunk there are usually files that are not part of the module but are under source control: pom.xml for example, but also non-project directories. I use some maven plugin to import my projects, however the root project is never included as a project.

Therefore I usually import the 'trunk' as a project into Eclipse as well (but that will not be a Java project, but just a bunch of files) so I have easy access to those source-controlled files as well.

Okay so basically what happens is that I have a bunch of files that are referenced twice: once under <trunk-project>/module-1/file.ext and once under <module-1-project>/file.ext. Sometimes however i have <module-1-project> closed and I still do a Team Synchronize on <trunk-project>. I get the correct changeset, but when I try to review changes by opening a file in a compare editor I sometimes - not always - get this error:

---
An internal error occurred during: "Initializing Compare Editor".
0x0000000a: Project 'module-1' is not connected to source control.
---

I can sort of understand why this happens. If I open 'module-1' and do it again it works, however since I'm 'Team Synchronizing' on the trunk project why does it not know that it's in an open project somewhere else?




Extra: 
* SVN Connector version: 2.2.2.I20100512-1900
* SVN Team Provider version: 0.7.9-I20100512-1900


Reproducible: Sometimes

Steps to Reproduce:
1. Create multi-module maven project
2. Import modules into Eclipse (some maven plugin)
3. Import the parent project (as a General project)
4. Close one or more of the modules
5. Team Synchronize on parent project

It does not *always* happen, not for every file. I guess it has something to do with the reference to the actual file that is last kept or something... not sure.