Hi David,
Sounds good.
Are you saying that any committer can now manage the content of the web
site?
If so, then perhaps a few more instructions are needed (at least by me).
If not, then I notice that the announcement of the release of version 4.1.0
is rather out of date
thanks,
Jon
On 9 Jan
All -
I updated the ooRexx web sites tonight. They now reflect updated
information and new copyright dates.
The biggest change is that they now are an SVN checkout. So you can
checkout your own copy, make updates, and then update the web sites with
a simple "svn update" command.
Let me know if y
I doubt this depends on the physical memory of the system (or should I say,
"virtual physical memory"?). The JVM gets initialized with a heap size
maximum, which is controllable via the startup options.
Rick
On Wed, Jan 8, 2014 at 9:49 AM, David Ashley wrote:
> Mark -
>
> Bumping up the memory
I looked up the fix I read about before:
Q:
I get an error Exception in thread "main" java.lang.OutOfMemoryError: Java
heap space when trying to build PDF. What is wrong?
A:
The default memory allocated for Java is not big enough to build your PDF.
You need to increase the memory allocated to *F
Here's a nice thread that discusses how to increase the heap size:
http://stackoverflow.com/questions/1565388/increase-heap-size-in-java
Is the doc build machine a 32-bit or a 64-bit system? A 32-bit one is more
limited, obviously.
Rick
On Wed, Jan 8, 2014 at 9:46 AM, Mark Miesfeld wrote:
>
Mark -
Bumping up the memory is not a problem. I raised it from 2GB to 4GB. We
will see if it builds successfully tonight.
Thanks for the insight.
David Ashley
On Wed, 2014-01-08 at 06:39 -0800, Mark Miesfeld wrote:
>
> On Wed, Jan 8, 2014 at 5:47 AM, David Ashley
> wrote:
> Mark, any
David,
This is what causes the build to fail:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
One suggested fix is a flag to increase the heap space. But as I said, I
could never get it to work. And, I don't remember the flag right now.
--
Mark Miesfeld
On Wed, Jan 8,
On Wed, Jan 8, 2014 at 5:47 AM, David Ashley wrote:
> Mark, anyone -
>
> Would someone please take a look at the ooDialog document? It has not
> built successfully in almost two weeks on the Build Machine.
>
David,
It is a Java out of memory problem.
I have that problem on one of my laptops wi
Mark, anyone -
Would someone please take a look at the ooDialog document? It has not
built successfully in almost two weeks on the Build Machine.
Thanks,
David Ashley
--
Rapidly troubleshoot problems before they affect
