Don't remember if anyone answered this.
Anyway, m2eclipse does not change, nor extend JDT model used by type
hierarchy and other views. All it does it contributes classpath
container build dynamically based on content of the pom.xml. that
container is no different then one used for Java runtime libraries.
If you want us to investigate this issue further, please create some
test projects and submit them to a jira issue along with step by step
instructions how to reproduce it.
Thanks
Eugene
sverhagen wrote:
Hi, is there any documentation available on what's being shown for standard
Eclipse commands like Call/type hierarchy, References and Declarations, when
using m2eclipse, and per consequence dependencies rather than just workspace
projects?
(These commands give us strange results, given that we don't know their
background in the Maven context, even to the extent that I wouldn't know how
to explain them here without familiarizing all of you with our particular
project structure, so I'll try to not go there.)
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
