Eugene Vigdorchik - 09 Feb 06 19:47 We have never encouraged this kind of setup with library to source dependencies. However for backward compatibility the problem will be fixed in 5.1.1

Gilles Philippart - 10 Feb 06 18:55 In fact, when dealing with very large application, this can happen quite often : Our team is responsible for 2 components : ComponentA and ComponentB. (say about 500 classes each) Our ComponentA uses our ComponentB (set up as 2 modules in Intellij with a A-> B dependency, and it works great) And another team developping ComponentC uses ComponentB too. But we don't have access to their source repository directly, instead they "publish" a jar and the corresponding sources on a regular basis... That's the kind of setup that I reproduced in the attached ipr and with only 1 class per component, but you get the picture... Gilles

Venkat Sonnathi - 16 Feb 06 06:19 I agree with Giles. This is a case we are also running into. Please make this change permanent. Regards, --Venkat.

Henri Ropponen - 17 Feb 06 10:34 We have a similar case. I would like to add that this error also prevents one from using the "smart" functions like SHIFT + SPACE etc. and listing usages. BR, Henri