Eclipse updating maven dependencies long time

6854933580_2c8b688306_z

Build Path Classpath(Build Path Manager.java:363) at org.eclipse.m2internal.

Build Path Classpath(Build Path Manager.java:343) at org.eclipse.m2internal.

Build Manager.build(Build Manager.java:383) at org.internal.events. Auto Build Build(Auto Build Job.java:144) at org.internal.events. Zip File$Zip Entry Element(Zip File.java:499) at zip. Main.main(Main.java:1288) This was perplexing at best. This got resolved for me by explicitly deleting the selenium-java v3.4.0 javadoc related file(s) in local maven repository. Thanks for the workaround, this had me stumped for a fair while!

Maven Builder$Build Project Facade(Maven Builder.java:154) at org.eclipse.m2internal.builder.

Maven Builder$Build Method

Build Manager.build(Build Manager.java:383) at org.internal.events. Auto Build Build(Auto Build Job.java:144) at org.internal.events. Zip File$Zip Entry Element(Zip File.java:499) at zip. Main.main(Main.java:1288) This was perplexing at best. This got resolved for me by explicitly deleting the selenium-java v3.4.0 javadoc related file(s) in local maven repository. Thanks for the workaround, this had me stumped for a fair while!

Maven Builder$Build Project Facade(Maven Builder.java:154) at org.eclipse.m2internal.builder.

Maven Builder$Build Method$1.call(Maven Builder.java:89) at org.eclipse.m2internal.embedder. Maven Execution Context.execute Bare(Maven Execution Context.java:176) at org.eclipse.m2internal.embedder.

Build Path Classpath(Build Path Manager.java:371) at org.eclipse.m2internal.

Build Path Manager.update Classpath(Build Path Manager.java:191) at org.eclipse.m2internal.

Some of our problems are:- Opening the project takes about 30 minutes and most of the time involves re-indexing of all files, including JDK classes (by comparison, "mvn eclipse:clean eclipse:eclipse" takes about a minute)- Very often IDEA becomes totally unresponsive and hangs forever when the project is opened- After running a Maven build from the command-line, IDEA indexes all files produced by the build, again causing a loss of time for the developer Although the extremely poor performance makes me wonder whether IDEA's approach of integrating with Maven is fundamentally wrong, I do understand that such criticism isn't very helpful.

||

Build Manager.build(Build Manager.java:383) at org.internal.events. Auto Build Build(Auto Build Job.java:144) at org.internal.events. Zip File$Zip Entry Element(Zip File.java:499) at zip. Main.main(Main.java:1288) This was perplexing at best. This got resolved for me by explicitly deleting the selenium-java v3.4.0 javadoc related file(s) in local maven repository. Thanks for the workaround, this had me stumped for a fair while! Maven Builder$Build Project Facade(Maven Builder.java:154) at org.eclipse.m2internal.builder.Maven Builder$Build Method$1.call(Maven Builder.java:89) at org.eclipse.m2internal.embedder. Maven Execution Context.execute Bare(Maven Execution Context.java:176) at org.eclipse.m2internal.embedder.Build Path Classpath(Build Path Manager.java:371) at org.eclipse.m2internal.Build Path Manager.update Classpath(Build Path Manager.java:191) at org.eclipse.m2internal.Some of our problems are:- Opening the project takes about 30 minutes and most of the time involves re-indexing of all files, including JDK classes (by comparison, "mvn eclipse:clean eclipse:eclipse" takes about a minute)- Very often IDEA becomes totally unresponsive and hangs forever when the project is opened- After running a Maven build from the command-line, IDEA indexes all files produced by the build, again causing a loss of time for the developer Although the extremely poor performance makes me wonder whether IDEA's approach of integrating with Maven is fundamentally wrong, I do understand that such criticism isn't very helpful.

.call(Maven Builder.java:89) at org.eclipse.m2internal.embedder. Maven Execution Context.execute Bare(Maven Execution Context.java:176) at org.eclipse.m2internal.embedder.

Build Path Classpath(Build Path Manager.java:371) at org.eclipse.m2internal.

Build Path Manager.update Classpath(Build Path Manager.java:191) at org.eclipse.m2internal.

Some of our problems are:- Opening the project takes about 30 minutes and most of the time involves re-indexing of all files, including JDK classes (by comparison, "mvn eclipse:clean eclipse:eclipse" takes about a minute)- Very often IDEA becomes totally unresponsive and hangs forever when the project is opened- After running a Maven build from the command-line, IDEA indexes all files produced by the build, again causing a loss of time for the developer Although the extremely poor performance makes me wonder whether IDEA's approach of integrating with Maven is fundamentally wrong, I do understand that such criticism isn't very helpful.

You must have an account to comment. Please register or login here!