Hi, I encountered this, too, myself. This is most probably caused by the implementation of SLING-437 (merge jackrabbit-text-extractors into jackrabbit-server), which causes a much bigger bundle with tons of additional classes to be built and analized.
I will look into that and try to find a solution to this problem... See SLING-443 [1] Regards Felix [1] https://issues.apache.org/jira/browse/SLING-443 Am Freitag, den 09.05.2008, 20:20 +0200 schrieb Dominik Süß: > Hi Paul, > > On Fri, May 9, 2008 at 8:07 PM, Paul Noden <[EMAIL PROTECTED]> wrote: > > > Just to check - you need to close the cmd prompt and open a new one > > for the environment variable to take effect - unless you used SET on > > the command line? > > > yes I opened a new cmd prompt and received the error. > > > > > For reference my current maven_opts is set to -Xmx1280m -Xms756m > > Am running 1.5.0_03, but otherwise the same. Ensure you have an easy > > 800mb free in the TMP path location too. > > > > Your current settings work fine for me, not producing any more heap space > errors. > This is the first time I had to give maven more heap space than default - I > don't know much about these tasks but it might be worth to check what > changed since last week to push the memoryrequirements. > > > > > > Hope this helps - am leaving the office now, will check how you got on > > later! > > > > Yes it dit! Thanks :) > > Dominik
