Hi Jukka, Jukka Zitting schrieb: > 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?
No, we never came around to a real solution. Actually and to be honest: The only module which actually suffers from this problem is the jcr/jackrabbit-server module, which creates a bundle with an embedded Jackrabbit Server. The reason for this massive memory requirement is that the BND tool used by the maven-bundle-plugin is analyizing all libraries embedded in the module, and this is alot since besides jackrabbit-core we also include Xerces (since Jackrabbit still needs this), Lucene and a few others. Now, one approach I have been considering earlier and might be considering again now, is to not use the maven-bundle-plugin anymore for the jcr/jackrabbit-server module but to hand code the manifest based on a prototype output we might get from the bundle plugin. There just was not anybody getting it done up to now. > > 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 generally build Sling from the command line > > 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. Certainly not. What you might try is omit the jackrabbit-server module from your build and check to see, whether this is really the culprit (of which I am pretty sure, though). Regards Felix
