Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342627

Summary:	Out of memory errors in development environment releng.
Product:	z_Archived	Reporter:	Igor Jacy Lino Campista <icampista>
Component:	Mylyn	Assignee:	Project Inbox <vex.core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Igor Jacy Lino Campista

2011-04-12 15:55:21 EDT

Releng, has no vmargs setup, so its very easy to get out of memory errors. 

We need some vmargs that give a good default.  perm 256m and

Comment 1 Florian Thienel

2011-11-09 17:37:54 EST

Moved to Mylyn Docs Vex.

Comment 2 Igor Jacy Lino Campista

2012-01-15 16:47:43 EST

Now that I was re-setting up my dev env. I had no success in using the releng.
The only way I managed to get my dev env working, was to download indigo SR1, install the additional WST addons, and the baltik 1.7 from the orbit update site.

So, therefore I unfortunately bypassed the releng to get my dev env working. 

Another thing, If I started from a modeling indigo SR1 distribution and setup the target platform within the releng editor, it will corrupt my installation after several minutes. Don't do that.  ;)


So for the time being, I cannot reproduce the right way, and the memory error as well.


BTW, pulling a fresh Vex repository using Eclipse tooling works quite nicely nowadays. (it differs a bit with the documentation from the wiki  http://wiki.eclipse.org/Vex/CommitterResources)

Comment 3 Florian Thienel

2014-09-05 04:32:24 EDT

In the mean time we use Eclipse Oomph (https://wiki.eclipse.org/Eclipse_Oomph_Installer) to setup the development environment (see https://wiki.eclipse.org/Vex/CommitterResources).