The maven repository is in another machine, and Eclipse take a long time to access to it, when it search a java class. My first test was with jars on my machine and it is much more faster. The problem are the jars located in another machine. You are right: "m2eclipse is contributing a new classpath container type. All classes visible trough that container are available to the search engine and that engine is part of JDT." I thought that m2 alter the order of classpath, but not. Sorry, and thanks
2007/10/30, Eugene Kuleshov <[EMAIL PROTECTED]>: > > > Would you mind to clarify which part I am right on? :-) > > Thanks > > Eugene > > > Edgar Espina wrote: > > Thanks for you help. You are rigth > > > > 2007/10/30, Eugene Kuleshov <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>: > > > > Edgar Espina wrote: > > > Hi Eugene, thanks for response. This delay only happens when a > > project > > > has maven project builder. If I removed the maven nature, works > > fine. > > > Any idea? > > m2eclipse is contributing a new classpath container type. All > > classes > > visible trough that container are available to the search engine and > > that engine is part of JDT. There isn't much we can do if search > > engine > > can't handle standard features. > > > > For a sake of experiment you can try to delete container, but > > manually > > add all the same jars and see if search will be any faster. Then > > compare > > it with new "user library" (basically also classpath container) in > > Window / Preferences... / Java / Build Path / User Libraries; add > > same > > jars in there and then add this "user library" into the classpath > for > > your project from Project / Properties / Java Build Path / Libraries > / > > Add Library... > > > > regards, > > Eugene > > > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
