Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346760

Summary: Updating Maven Dependencies for 3 hours?????
Product: z_Archived Reporter: Jay HatesThis <jbailey>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: CLOSED INVALID QA Contact:
Severity: major    
Priority: P3 CC: igor
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Jay HatesThis CLA 2011-05-20 14:58:05 EDT 
This issue has been raised before on other boards, and was dismissed out of hand by an individual who didn't understand what was being reported.

http://jira.codehaus.org/browse/MNGECLIPSE-1029

At startup, under no circumstances should a process that hangs up Eclipse while it takes hours to complete be run by default.  The problem here has nothing to do with fast or slow Internet connections.  It has to do with M2E/Maven's internal bookkeeping taking way too long when running upon complex codebases.  This is made worse by the fact that you can't stop the process once it starts.  Click on "Cancel" and it says "cancel requested," but never actually cancels.

Now, it is true that we can uncheck the "update on startup" option.  That isn't good enough, because if you open a workspace with a POM in it that does this, you get caught by surprise, and are then stuck.  Even if you do the unchecking then, and kill and restart Eclipse, you are still stuck, as it picks up where it left off.

In all cases, when we code things, we need to understand their impact.  If an update is going to take an interminable amount of time, warn the user, and ask whether to do it or not.  If a "cancel" button is clicked, actually cancel the operation.  Don't set potentially harmful options as installation defaults.  Don't start up something the next time that is harmful or has been turned off.

Please address this for real this time.
Comment 1 Igor Fedorenko CLA 2011-05-20 17:42:32 EDT 
With all due respect, this does not provide enough information to be able to reproduce the problem and ultimately come up with a solution. 

Assuming the problem appears in the latest 0.13 build, which is part of Eclipse 3.7/Indigo repository and "For Java Developers" package, please provide the following

* Attach your Eclipse configuration details (Help->About_Eclipse_SDK->Installation_Details->Configuration)

* Explain what "a process that hangs up Eclipse" means exactly, i.e. Eclipse UI is fully blocked, Save or Build operations are "blocked" by background process, etc.

* Attach JVM Thread dump when Eclipse is in this "hung" state

* If practical, attach sample project and describe steps to reproduce the problem. Indicate any special environmental conditions are required (slow internet connections, timeouts, etc).
Comment 2 Igor Fedorenko CLA 2011-08-01 02:51:58 EDT 
Closing old bug reports. Please reopen when you are able to provide information requested in comment 1.
Comment 3 Denis Roy CLA 2021-04-19 13:22:59 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/