Hi Dominik,

Am Donnerstag, den 22.05.2008, 15:03 +0200 schrieb Dominik Süß:
> Regarding to the change to "minor" in JIRA I worry that this problem will
> occur to anyone working with maven standard values. Since anyone has to
> build this bundle at least one time this could scare some developers.
> 
> WDYT? Or did I miss a better workarround?

Yes, the workaround is to set the MAVEN_OPTS environment variable as
discussed. In addition this seems to only happen on Windows boxes - on
my Fedora 7 box, this does not happen. Finally, this only is an issue
while doing a reactor build from the root of the project.

Given these three reasons and the fact, that the issue has no influence
of actually running Sling, I deliberatly degraded the priority and
descheduled it from the initial release.

Our goal is to get a release out of the doors real-soon-now. In the
meantime you may also use the SNAPSHOTs Carsten is building and
deploying to the Snapshot repository at
http://people.apache.org/repo/m2-snapshot-repository/ every once in a
while.

Hope this helps.

Regards
Felix

> 
> Best regards,
> Dominik
> 
> On Tue, May 13, 2008 at 9:14 AM, Felix Meschberger <[EMAIL PROTECTED]>
> wrote:
> 
> > 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
> >
> >

Reply via email to