Hi,
I think I fixed the problem (it's in CVS, as far as I remember
non-developers will have to wait until tomorrow to see those changes).
I still see several instances of the "WOLips Project Files Updates (Java
Elements)" jobs active at the same time. I am still conviced that the
proper place for the stuff done in all the "WOLips Project Files
Updates" jobs is a new eclise builder (it should simplify the handling
of resource changes greatly).
Another problem is that the IncrementalBuilder currently in CVS doesn't
propagate file deletions into the build (if you delete stuff from your
project you'll have to do a full build).
Harald
Ian McDougall wrote:
> I'm experiencing the same issue. When I increase the max heap size
> (-vmargs -Xmx512m) the "WOLips Project Files Update (Java Elements)" runs
> and won't complete. Pressing cancel does nothing.
>
> Perhaps this issue is not completely fixed?
> http://objectstyle.org/jira/secure/ViewIssue.jspa?key=WOL-89
>
>
>>-----Original Message-----
>>From: Donna Yorukoglu [mailto:dym..utreach.psu.edu]
>>Sent: Monday, July 26, 2004 9:06 AM
>>To: woproject-de..bjectstyle.org
>>Subject: Out of Memory Error
>>
>>
>>Checked out the latest version of WOLips from CVS. Since the update, I
>>keep running out of memory.
>>
>>Here is my Console info:
>>
>>!ENTRY org.eclipse.core.runtime 4 2 Jul 26, 2004 11:01:46.361
>>!MESSAGE An internal error occurred during: "WOLips Project Files
>>Updates (Java Elements)".
>>!STACK 0
>>java.lang.OutOfMemoryError
>>
This archive was generated by hypermail 2.0.0 : Thu Jul 29 2004 - 12:51:43 EDT