On 6/21/10 5:34 AM, Stefan Bodewig wrote:
This would allow for a little more concurrency than we can do on the
Zone or VM... of course we'd have to be able to address all of those
cores. Wonder whether Python has glue for Grand Central Dispatch?
Most of the weight in gump runs is inside the ja
Wonderful. Thanks for your feedback, Stefan!
On 21.06.2010 12:08:07 Stefan Bodewig wrote:
> On 2010-06-21, Jeremias Maerki wrote:
>
> > It appears as if Gump didn't SVN update the workspace properly and the
> > changes [4] I made to FOP Trunk to adjust for the move are not visible
> > to Gump.
>
On 2010-06-21, Jeremias Maerki wrote:
> It appears as if Gump didn't SVN update the workspace properly and the
> changes [4] I made to FOP Trunk to adjust for the move are not visible
> to Gump.
You are correct, the workspace is locked because of some earlier error
while we had svn problems
There is a problem with run 'vmgump-public' (21062010_02), location :
http://vmgump.apache.org/gump/public
The log ought be at:
http://vmgump.apache.org/gump/public/gump_log.txt
Hi there,
I need some help figuring out why xml-fop currently fails. I've moved
some newly added classes from package org.apache.xmlgraphics.java2d to
org.apache.xmlgraphics.java2d.color [1]. Now, xmlgraphics-commons
happily builds and if I look at the generated JAR [2], the classes are
in the rig