Issue Details (XML | Word | Printable)

Key: MNGECLIPSE-329
Type: Bug Bug
Status: Closed Closed
Resolution: Duplicate
Priority: Critical Critical
Assignee: Unassigned
Reporter: Derek Clarkson
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Maven Integration for Eclipse

Adding a dependency to the pom causes plugin to go into loop and freeze eclipse, issuing lots of "Unable to index ..." messages

Created: 02/May/07 08:57 PM   Updated: 28/Sep/07 01:01 AM
Component/s: None
Affects Version/s: 0.0.11
Fix Version/s: None

Time Tracking:
Not Specified

Environment: V0.0.11 built from latest source.
Issue Links:
Duplicate
 


 Description  « Hide
when I add a new dependency to the pom which is not currently in my local repository, the plugin will drop into a loop issuing error messages. Sample from log:
....
3/05/07 11:17:35: Downloading Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:35: Downloading Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:35: Downloading Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:35: Downloaded Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:36: Unable to index jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1; Lock obtain timed out: Lock@C:\DOCUME~1\CLARKS~1\LOCALS~1\Temp\lucene-92d5fc440e7c0ff376b065a24d717224-write.lock
3/05/07 11:17:36: Downloaded Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:37: Unable to index jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1; Lock obtain timed out: Lock@C:\DOCUME~1\CLARKS~1\LOCALS~1\Temp\lucene-92d5fc440e7c0ff376b065a24d717224-write.lock
3/05/07 11:17:37: Downloaded Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:38: Unable to index jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1; Lock obtain timed out: Lock@C:\DOCUME~1\CLARKS~1\LOCALS~1\Temp\lucene-92d5fc440e7c0ff376b065a24d717224-write.lock
3/05/07 11:17:38: Downloaded Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:39: Unable to index jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1; Lock obtain timed out: Lock@C:\DOCUME~1\CLARKS~1\LOCALS~1\Temp\lucene-92d5fc440e7c0ff376b065a24d717224-write.lock
3/05/07 11:17:39: Downloaded Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
3/05/07 11:17:40: Unable to index jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1; Lock obtain timed out: Lock@C:\DOCUME~1\CLARKS~1\LOCALS~1\Temp\lucene-92d5fc440e7c0ff376b065a24d717224-write.lock
3/05/07 11:17:40: Downloaded Repositorycentral/jboss/jboss-j2ee/4.0.2/jboss-j2ee-4.0.2.jar.sha1
....

It does eventually resolve and download the files, but it takes an enormous amount of time. I've watched it take up to 5 minutes just to resolve a single sha1 file, and it's not unusual for a new dependency to trigger a 20 or 30 minute wait.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Eugene Kuleshov added a comment - 03/Jun/07 01:37 AM
Please provide project that will be sufficient to reproduce this issue. Also see http://docs.codehaus.org/display/M2ECLIPSE/How+To+Report+Issues

Thanks.


Derek Clarkson added a comment - 03/Jun/07 02:33 AM
Easy, pick a project, any project in fact, but the more dependencies it has the better. Then wipe your local maven cache, start Eclipse and clean the project. The plugin will then start miss-behaving. This is 100% reproducable and occurs on every eclipse install we have. Tehre are plenty of comments from other people with the same problem.

Eugene Kuleshov added a comment - 03/Jun/07 11:10 AM
Please comment on MNGECLIPSE-302

Jol Blazey added a comment - 27/Sep/07 10:42 PM
Please Please fix this problem.
Last time I added a dependency for CXF (apache incubator web services) It took about one hour. Error message exactly as above with different file paths. I cant copy the message because my workspace is still frozen from the error message loop. Eclipse 3.2. Win XP all updates. m2 plugin from update site.
mvn command line works fine.

It must be related to eclipse trying to re-index new jar and sha files as they are downloaded from repos. Can't the indexing be turned off while m2 reads the pom and downloads?

I'm going to disable Maven in eclipse, its a show stopper.


Jol Blazey added a comment - 28/Sep/07 01:01 AM
Make that 2.5 hours downtime for the last add dependency indexing error loop. Plus error message at end. could not resolve activation..jar please download from people.apache ... incubator.