Re: m2eclipse+galileo: index issue? (solved)
tony_k wrote: > > ... > > so on a lark, i reinstalled galileo and then m2eclipse and this time let > the "updating indexes" phase run to completion (it actually did take about > a half hour) and then things seemed ok. > > ... > re-installing may not be necessary. I tried this: Do in eclipse: window->show view->other->maven->maven indexes. One of the indexes is: http://repo1.maven.org/maven2. right-click on this one, and try rebuild index. If that does not work, create a new index with the same address, and do a rebuild of that. With me that worked, and I could remove the original one. After this a restart of eclipse will NOT show the error anymore, and the add dependency search function operates as it should. Problem solved. -- View this message in context: http://n2.nabble.com/m2eclipse-galileo-index-issue-tp3165039p3699256.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: m2eclipse+galileo: index issue? (solved)
It should normally take only a few minutes to retrieve the initial index from s3 and process it. Subsequent requests will pick up the weekly incremental which is ~150k and is barely noticeable. There are some known problems where the indexes get left in an odd state if it's aborted. On Sat, Jun 27, 2009 at 12:29 AM, tony_k wrote: > > i read somewhere about the the initial m2eclipse "updating indexes" phase > taking a half hour > and i recalled that i actually forcefully stopped that phase in eclipse by > clicking the red button > to the right of the progress bar. > > so on a lark, i reinstalled galileo and then m2eclipse and this time let the > "updating indexes" phase run to completion (it actually did take about a > half hour) and then things seemed ok. > > i must have corrupted something when i killed the index update in mid > stream, so beware... > > is it normal to take that long, or is it possible that something about > galileo is making that process suck wind? > > anyway just wanted to share in case anyone else gets plagued with this > issue... > > party on! > -- > View this message in context: > http://n2.nabble.com/m2eclipse%2Bgalileo%3A-index-issue--tp3165039p3165318.html > Sent from the maven users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: m2eclipse+galileo: index issue? (solved)
i read somewhere about the the initial m2eclipse "updating indexes" phase taking a half hour and i recalled that i actually forcefully stopped that phase in eclipse by clicking the red button to the right of the progress bar. so on a lark, i reinstalled galileo and then m2eclipse and this time let the "updating indexes" phase run to completion (it actually did take about a half hour) and then things seemed ok. i must have corrupted something when i killed the index update in mid stream, so beware... is it normal to take that long, or is it possible that something about galileo is making that process suck wind? anyway just wanted to share in case anyone else gets plagued with this issue... party on! -- View this message in context: http://n2.nabble.com/m2eclipse%2Bgalileo%3A-index-issue--tp3165039p3165318.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
