Hi, Did we ever come up with a real solution as opposed to a workaround to the problem with Sling builds requiring lots of memory?
I'm hitting a similar issue with Eclipse Ganymede (with the m2eclipse plugin), where my memory usage shoots up to 1-2GB (and possibly higher, but I use -Xmx2GB) quickly after I import and build the Sling components. I have Eclipse workspaces with 50+ open Maven projects in them working fine with <500MB memory, so this shouldn't be just about the number of Sling components. BR, Jukka Zitting
