Finally, after over a week changing things and waiting a day for the
next build, the full test suite (minus hyphenation) is running in Gump
and passes under OpenJDK. It also uncovered a headless exception in
Batik which is now fixed.
http://vmgump.apache.org/gump/public/xml-fop/index.html
So, whe
On 03/03/11 12:44, Jeremias Maerki wrote:
> Finally, after over a week changing things and waiting a day for the
> next build, the full test suite (minus hyphenation)
Just curious: why no hyphenation?
> is running in Gump
> and passes under OpenJDK. It also uncovered a headless exception in
> Ba
On 04.03.2011 16:06:30 Vincent Hennebert wrote:
> On 03/03/11 12:44, Jeremias Maerki wrote:
> > Finally, after over a week changing things and waiting a day for the
> > next build, the full test suite (minus hyphenation)
>
> Just curious: why no hyphenation?
Mostly because that requires the OFFO
On 05/03/11 12:06, Jeremias Maerki wrote:
> On 04.03.2011 16:06:30 Vincent Hennebert wrote:
>> On 03/03/11 12:44, Jeremias Maerki wrote:
>>> Finally, after over a week changing things and waiting a day for the
>>> next build, the full test suite (minus hyphenation)
>>
>> Just curious: why no hyphen
On 08.03.2011 20:31:54 Vincent Hennebert wrote:
> On 05/03/11 12:06, Jeremias Maerki wrote:
> > On 04.03.2011 16:06:30 Vincent Hennebert wrote:
> >> On 03/03/11 12:44, Jeremias Maerki wrote:
> >>> Finally, after over a week changing things and waiting a day for the
> >>> next build, the full test s
On 09/03/11 07:51, Jeremias Maerki wrote:
> On 08.03.2011 20:31:54 Vincent Hennebert wrote:
>> On 05/03/11 12:06, Jeremias Maerki wrote:
>>> On 04.03.2011 16:06:30 Vincent Hennebert wrote:
On 03/03/11 12:44, Jeremias Maerki wrote:
> Finally, after over a week changing things and waiting a
On 09.03.2011 17:05:19 Vincent Hennebert wrote:
> On 09/03/11 07:51, Jeremias Maerki wrote:
> > On 08.03.2011 20:31:54 Vincent Hennebert wrote:
> >> On 05/03/11 12:06, Jeremias Maerki wrote:
> >>> On 04.03.2011 16:06:30 Vincent Hennebert wrote:
> On 03/03/11 12:44, Jeremias Maerki wrote:
> >>>
On 27 Mar 2011, at 15:30, Jeremias Maerki wrote:
> To whom it may engage...
>[junit] Testcase:
> bookmarks_1.xml(org.apache.fop.intermediate.IntermediateFormatTestSuite$1):
>Caused an ERROR
>[junit] cvc-complex-type.2.4.b: The content of element 'nav:bookmark' is
> not complete.
I've notified the Xerces project:
https://issues.apache.org/jira/browse/XERCESJ-1505
On 29.04.2011 11:06:02 Jeremias Maerki wrote:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.ht
I’m a bit at a loss to understand why Gump has suddenly started to throw
this error. The tests run fine on my local copy, both with a Sun and an
OpenJDK jvm. Could that be that the version of the Xerces library used
by Gump is not up-to-date? But then, why would that have worked before?
Any ideas?
On 07 Jun 2011, at 17:43, Vincent Hennebert wrote:
> I’m a bit at a loss to understand why Gump has suddenly started to throw
> this error. The tests run fine on my local copy, both with a Sun and an
> OpenJDK jvm. Could that be that the version of the Xerces library used
> by Gump is not up-to-da
On Tue, Jun 07, 2011 at 10:05:24PM +0200, Andreas L. Delmelle wrote:
> On 07 Jun 2011, at 17:43, Vincent Hennebert wrote:
>
> > I’m a bit at a loss to understand why Gump has suddenly started to throw
> > this error. The tests run fine on my local copy, both with a Sun and an
> > OpenJDK jvm. Coul
On 08 Jun 2011, at 12:07, Simon Pepping wrote:
> On Tue, Jun 07, 2011 at 10:05:24PM +0200, Andreas L. Delmelle wrote:
>> At any rate, the starting '\(' does indeed seem to be an invalid escape
>> sequence (Shouldn't it be '\\(' if it needs to match a literal bracket?)
>> It is present as-is, on
On 10/08/11 12:56, Jeremias Maerki wrote:
> junit-compile-java:
> [mkdir] Created dir: /srv/gump/public/workspace/xml-fop/build/test-classes
> [mkdir] Created dir: /srv/gump/public/workspace/xml-fop/build/test-gensrc
> [mkdir] Created dir: /srv/gump/public/workspace/xml-fop/build/test-r
On Wed, Aug 10, 2011 at 02:33:05PM +0100, Vincent Hennebert wrote:
> On 10/08/11 12:56, Jeremias Maerki wrote:
> > junit-compile-java:
> > [mkdir] Created dir:
> > /srv/gump/public/workspace/xml-fop/build/test-classes
> > [mkdir] Created dir:
> > /srv/gump/public/workspace/xml-fop/build/t
On 12/08/11 20:38, Simon Pepping wrote:
> On Wed, Aug 10, 2011 at 02:33:05PM +0100, Vincent Hennebert wrote:
>> On 10/08/11 12:56, Jeremias Maerki wrote:
>>> junit-compile-java:
>>> [mkdir] Created dir:
>>> /srv/gump/public/workspace/xml-fop/build/test-classes
>>> [mkdir] Created dir:
>>>
It is not a good idea to fetch xml.xsd from W3C each time. Put it in
the sources and if necessary use a catalog. xml.xsd is already
available at src/documentation/intermediate-format-ng/xml.xsd.
Simon
On Thu, Nov 10, 2011 at 08:27:53AM +, Jeremias Maerki wrote:
> To whom it may engage...
>
This is because fop-hyph.jar is not in the classpath in Gump. I logged
an issue:
https://issues.apache.org/jira/browse/GUMP-166
If for licensing reasons we cannot add it to the Gump classpath, then we
will have to exclude the HyphenationLayoutTestCase from the regex in the
junit-all target.
Vince
This appears to be failing because Gump doesn't have Mockito in its
class-path, I think it needs to be added to the Gump Metadata
(http://svn.apache.org/repos/asf/gump/metadata/project/xml-fop.xml),
does anyone know how I do this?
Thanks
Mehdi
On 23 November 2011 07:50, Jeremias Maerki wrote:
>
See https://issues.apache.org/jira/browse/GUMP-167, hopefully it will
be resolved in the next build.
On 23 November 2011 09:41, mehdi houshmand wrote:
> This appears to be failing because Gump doesn't have Mockito in its
> class-path, I think it needs to be added to the Gump Metadata
> (http://sv
FYI, this is caused by missing unlimited strength jurisdiction policy files
in the Gump server. I have asked Stefan@gump to update the files, which he
expects to do soon.
On Tue, Sep 3, 2013 at 2:02 AM, FOP Gump Nightly Build <
fop-dev@xmlgraphics.apache.org> wrote:
> To whom it may engage...
>
Just to let you know: I’m working on it. The error is different each
time, so I guess I’m making progress :-)
Vincent
On 20/12/13 01:08, FOP Gump Nightly Build wrote:
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gu
It seems that this is happening because we have FOP configured to use
checkstyle 5.5 and Gump is using 5.7-SNAPSHOT. I do not get the two
warnings that cause this failure when using 5.5.
I think we should move to use the same version as Gump, even if it is a
SNAPSHOT.
On 1/5/14, 1:07 AM, F
On 06/01/14 01:15, Luis Bernardo wrote:
It seems that this is happening because we have FOP configured to use
checkstyle 5.5 and Gump is using 5.7-SNAPSHOT. I do not get the two warnings
that cause this failure when using 5.5.
This issue is secondary. The real problem is that Gump doesn’t seem
Hello,
I could do with some help from Gump specialists here.
The gump-test target in the latest FOP build.xml file in Subversion does
no longer depend on Checkstyle, yet Gump still seems to be running it.
Also, in an earlier version [1] I modified the Checkstyle target to
display a report on st
Cc: fop-dev@xmlgraphics.apache.org
Subject: Re: [GUMP@vmgump]: Project xml-fop-test (in module xml-fop) failed
Hello,
I could do with some help from Gump specialists here.
The gump-test target in the latest FOP build.xml file in Subversion does no
longer depend on Checkstyle, yet Gump still seems
I'll fix this momentarily.
On Wed, Aug 6, 2014 at 6:57 PM, FOP Gump Nightly Build <
fop-dev@xmlgraphics.apache.org> wrote:
> To whom it may engage...
>
> This is an automated request, but not an unsolicited one. For
> more information please visit http://gump.apache.org/nagged.html,
> and/or con
Whatever this problem is doesn't seem related to my recent findbugs
changes. It looks like the checkstyle rules being run by gump don't
correspond to what is in trunk, since I am not seeing any of these warnings
(using Checkstyle 5.7). I also wonder why an unreleased (snapshot) of
Checkstyle 5.8 is
Hi Glenn,
Luis mentioned to me that Gump had upgraded the Checkstyle version.
Thanasis should have some time to look into the failures next week.
Thanks
Chris
On 15/08/2014 02:17, Glenn Adams wrote:
Whatever this problem is doesn't seem related to my recent findbugs
changes. It looks like t
Hi,
Could be stick to a released version of checkstyle otherwise its hard to run
locally.
Thanks
-Original Message-
From: Chris Bowditch [mailto:bowditch_ch...@hotmail.com]
Sent: 15 August 2014 16:09
To: fop-dev@xmlgraphics.apache.org
Subject: Re: [GUMP@vmgump]: Project xml-fop-test
graphics.apache.org
> Subject: Re: [GUMP@vmgump]: Project xml-fop-test (in module xml-fop)
> failed
>
> Hi Glenn,
>
> Luis mentioned to me that Gump had upgraded the Checkstyle version.
> Thanasis should have some time to look into the failures next week.
>
> Thanks
>
> C
il.com
<mailto:bowditch_ch...@hotmail.com> ]
Sent: 15 August 2014 16:09
To: fop-dev@xmlgraphics.apache.org <mailto:fop-dev@xmlgraphics.apache.org>
Subject: Re: [GUMP@vmgump]: Project xml-fop-test (in module xml-fop) failed
Hi Glenn,
Luis mentioned to me that Gump had upgraded the Checkstyle versio
;mailto:bowditch_ch...@hotmail.com>]
Sent: 15 August 2014 16:09
To: fop-dev@xmlgraphics.apache.org
<mailto:fop-dev@xmlgraphics.apache.org>
Subject: Re: [GUMP@vmgump]: Project xml-fop-test (in module
xml-fop) failed
Hi Glenn,
Luis mentioned to me that Gump had upg
Subject: Re: [GUMP@vmgump]: Project xml-fop-test (in module xml-fop) failed
Yes I'd prefer to work with Jenkins, Gump is a bit old school :-) I'd also like
to be able to control the version of build tools that we use, not sure if the
Apache Jenkins server will allow that or not?
Thanks,
You can raise an issue in JIRA for project GUMP:
https://issues.apache.org/jira/browse/GUMP. Simon
On Tue, Aug 16, 2011 at 11:40:33AM +0100, Vincent Hennebert wrote:
>
> Now I’m not too sure how to get JUnit upgraded. Should I send a mail to
> general at gump.apache.org, or builds at apache.org,
Done: https://issues.apache.org/jira/browse/GUMP-165
Thanks again,
Vincent
On 16/08/11 18:36, Simon Pepping wrote:
> You can raise an issue in JIRA for project GUMP:
> https://issues.apache.org/jira/browse/GUMP. Simon
>
> On Tue, Aug 16, 2011 at 11:40:33AM +0100, Vincent Hennebert wrote:
>>
>>
36 matches
Mail list logo
