Where you running maven within an IDE such as MyEclipse? Today i attemped it inside MyEclipse and always received an OutOfMemoryError. Ran it within command prompt and had no problems.
On 2/24/06, Yann Le Du <[EMAIL PROTECTED]> wrote: > > OK, so the problem is not about 256 Mo then. Still the memory grows and > never goes over some value (90 Mo for you). I think it's worth a JIRA > issue, > can you create one ? > > To solve your problem, you can try and fork the compile and test tasks, > maybe you'll gain enough memory so that javadoc do not fail : > ~ <plugin> > ~ <artifactId>maven-compiler-plugin</artifactId> > ~ <configuration> > ~ <fork>true</fork> > ~ </configuration> > ~ </plugin> > ~ <plugin> > ~ <artifactId>maven-surefire-plugin</artifactId> > ~ <configuration> > ~ <forkMode>once</forkMode> > ~ </configuration> > ~ </plugin> > > 2006/2/24, Thorsten Heit <[EMAIL PROTECTED]>: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > I'm not even sure MAVEN_OPTS=-Xmx is efficient over 256 Mo. I tried > > several > > > values and always the mvn task grew to about 256 Mo then stopped. Can > > you > > > try again and watch in the task manager how the used memory evolves ? > > > > I watched Maven's memory consumption with Sysinternals Process Explorer, > > but the whole process never comsumed more than 90MB, independent of > > whether I used -Xmx384m or -Xmx256m in MAVEN_OPTS. In both cases the > > OOME occurs after quite a lot of time... > > > > > > Thorsten > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.2.1 (MingW32) > > > > iD8DBQFD/zXxQvObkgCcDe0RAlZfAJ44iJTdCPoTCi7k6tbJLmfPHrcBUwCgyv3H > > Vt+dEm3suYW8aIbIpRna6pA= > > =C5wA > > -----END PGP SIGNATURE----- > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > >
