After some investigation I found out that was m2eclipse (in its newest version). I've just updated to indigo with m2e and will check if it's any better.
I have 2 maven projects in the workspace. 2011/7/27 Igor Fedorenko <[email protected]>: > What m2e version do you use and how many workspace projects do you have? > > m2e 1.0 needs about 2M for each workspace project, so 500M seems like > too much. I'd recommend using a profiler to see what uses all that memory. > > -- > Regards, > Igor > > On 11-07-27 10:16 AM, Konrad Garus wrote: >> >> I've been using m2e for a while and constantly fought problems with >> memory. I decided to measure it and discovered that without m2e >> Eclipse for my workspace needs about 500 MB, while with m2e it's >> _twice_ as much. That's only after opening the workspace, before I >> change any files or compile! >> >> What can I do to decrease memory impact of m2e? I don't care about >> anything but build path& dependency management. >> > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > -- Konrad Garus _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
