[ http://jira.codehaus.org/browse/MNGECLIPSE-198?page=comments#action_75964 ] Eugene Kuleshov commented on MNGECLIPSE-198: --------------------------------------------
Why people are using those graphs when simple tree is just as good, byt way more compact and readable?... Anyways, I wonder how many dependencies your project has and how many of those actually have javadocs deployed? BTW, looking at your graph, slow part isn't really resolveClasspathEntries, but getMavenEmbedder(), which creates embedder every time (not sure what is underneath and you can dig into that if you want). I'll look at reusing embedder within unit of work when will be integrating new embedder build... > resolveClasspathEntries performance bug > --------------------------------------- > > Key: MNGECLIPSE-198 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-198 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug > Components: Dependency Resolver > Affects Versions: 0.0.10 > Environment: Eclipse 3.2 for Windows > Reporter: Marek Bieganski > Attachments: call_graph.zip > > > Most of time used by resolveClasspathEntries method is wasted for resolving > javadoc urls. > I attached call graps from jprofiler. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
