I have discovered odd problems with transitive dependencies, in particular
with workspace resolution and with snapshot dependencies.
For instance, lets say I have the following setup:
 myproject 1.0 depends on mymodule 1.1-SNAPSHOT, which in turn depends on
mylib 1.1-SNAPSHOT
(all projects checked out in the workspace)

Now, eclipse complains about compilation error in myproject, referring to
classes were that changed/moved/renamed between mylib 1.0 and 1.1-SNAPSHOT
which indicates that Eclipse is actually using 1.0 incorrectly!

The odd thing is that when I check dependency graph (in the pom editor) it
SAYS that it it IS using 1.1-SNAPSHOT!
Also, even though eclipse marks the referered class as incorrect (unknown
class), I DO see it when I use auto-completition AND when I click on the
class I jump to the workspace project and the correct class in the checked
out mylib 1.1-SNAPSHOT ?!?

Also, it seems that this problem does not occur when I run maven externally
to build the project...

Anyone have any feedback about this? and possible ways to fix/work around
it?
It is quite annoying and prevents us from working properly with snapshots
etc...

//Kent

Reply via email to