source analysis misses dependencies between libraries? (build 3431)

I think something has changed(broken) in resolving inter-library
dependencies.
If browse through the sources of a library (Spring, in this case),
references to other libraries (commons-logging) are not resolved (i.e.,
red). commons-logging is present in my module library list.

I stumbled across this because I extended one of the Spring classes.
This class has a protected field 'log'. If I access this field in my
subclass, it shows up 'red'. (Compiling does work correctly, though).
If I open the source for the Spring-class I'm extending, it shows up red
as well.

I've thrown away caches etc. but rescanning libraries doesn't make a
difference.

Should I file an issue?

regards,
Edwin

2 comments
Comment actions Permalink

Edwin,
Nothing has changed in recent builds. The reason for this bug could come
from other module which
references Spring, but does not reference common-logging.
This is indeed rather ancient bug with multimodule projects, that to be
fixed requires significant architecture changes.

Eugene.

"Edwin van Ouwerkerk Moria" <edwin@cadwal.org> wrote in message
news:dci9p7$pra$1@is.intellij.net...
>I think something has changed(broken) in resolving inter-library
>dependencies.

If browse through the sources of a library (Spring, in this case),
references to other libraries (commons-logging) are not resolved (i.e.,
red). commons-logging is present in my module library list.

>

I stumbled across this because I extended one of the Spring classes. This
class has a protected field 'log'. If I access this field in my subclass,
it shows up 'red'. (Compiling does work correctly, though). If I open
the source for the Spring-class I'm extending, it shows up red as well.

>

I've thrown away caches etc. but rescanning libraries doesn't make a
difference.

>

Should I file an issue?

>

regards,
Edwin



0
Comment actions Permalink

Eugene Vigdorchik (JetBrains) wrote:

Nothing has changed in recent builds. The reason for this bug could come
from other module which
references Spring, but does not reference common-logging.


Yup - that solved it! Wasn't sure what had changed - my library
definitions, my project definitions, or IDEA.

This is indeed rather ancient bug with multimodule projects, that to be
fixed requires significant architecture changes.


I see - well, actually, not having commons-logging in the other module
was an error anyway, and checking the 'library-exports' correctly also
solves this.

Maybe this issue could go in some sort of 'known problems/gotcha's and
solutions' document?

Regards,
Edwin

0

Please sign in to leave a comment.