Eugene Kuleshov schrieb:
Daniel Serodio (lists) wrote:
I have a project ("A") which depends on a bunch of 3rd party
libraries, plus
a "home-grown" ("B") library. Both are "managed" by Maven.
Project A's pom.xml contains the dependency on B, but while project B
is open
in my workspace, Eclipse is unable to resolve B's classes. If I close
Project
B in Eclipse, the class is resolved correctly.
I'm using Eclipse 3.3.1.1 and m2eclipse 0.0.12
Daniel, unfortunately this is not enough information to reproduce
your issue. Generally, this is very typical scenario and it does work
with our own test cases. So please open a JIRA issue and attach test
project that would allow us to reproduce it. See some hints at
http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues
when problems with resolvings occur i always did following (as a
workaround): make a Clean of the project.
after that check whether resolving is done correctly, so go to
Project->Properties->Java Build Path->Libaries(Tab). do an expand of
'Maven Dependencies' and the you see whether a project or library from
repository has been properly included.
--
manuel aldana
[EMAIL PROTECTED]
homepage: www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
