I was just training a new Java developer today and explaining that there are various views on the topic so don’t get me wrong when I say this – I do understand that views differ – but what kind of solution would have 300+ Eclipse projects in a single workspace? I break my workspaces up by deliverable, or by business process or something related so only related projects go in a single workspace. I am constantly deleting and recreating workspaces – they’re supposed to be a throw-away objects and transitory in nature. My typical workspace has 1 to 5 projects. The project count also goes up and down as I work on a solution.
From: m2e-users-boun...@eclipse.org [mailto:m2e-users-boun...@eclipse.org] On Behalf Of Saqib Rasul Sent: Friday, January 15, 2016 10:42 To: m2e-users@eclipse.org Subject: [EXTERNAL][m2e-users] m2e hanging at 65% (aka Aether locking) We have a similar setup with over 300 projects and many inter-project dependencies. And we are experiencing performance issues. Saving a java file causes heaps of other projects to be "refreshed" and this makes eclipse unusable for that period. Refreshing all projects takes minutes. When it only takes under 20 secs in the eclipse-world. When having those projects as just eclipse projects, the performance is more than adequate. We are running on SSD drives, so IO should't be an issue. It seems this plugin works well when there are only limited number of projects in the workspace. As soon as we have lots of projects, it becomes unusable.
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
