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: [email protected] For additional commands, e-mail: [email protected]
