On Tue, 14 Dec 2004, Ceki Gülc [EMAIL PROTECTED] wrote:
The fact that a small typo affects 200 projects should tell you that
something is wrong with Gump's current approach.
Absolutely agreed. We know we could do better, we just haven't had
the time/skills to change it yet.
For example,
Dear Gumpmeisters,
The following 5 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Project nant (in module nant) failed
[EMAIL PROTECTED]: Project txt2html-task (in module jakarta-servletapi-5)
success, but with
Hi all,
the last log4j run failed because of
[javac]
/home/gump/workspaces2/public/workspace/logging-log4j/src/java/org/apache/log4j/joran/util/JoranDocument.java:126:
unreported exception java.io.IOException; must be caught or declared to be
thrown
[javac] return
Stefan Bodewig bodewig at apache.org writes:
On Tue, 14 Dec 2004, Dalibor Topic robilad at kaffe.org wrote:
Davanum Srinivas davanum at gmail.com writes:
i think so...
Yeah, the RMIC code essentially the same as in old Kaffe, but under
the GNU namespace.
Unfortunately we
Date: 2004-12-15T05:22:47
Editor: DavanumSrinivas [EMAIL PROTECTED]
Wiki: Gump Wiki
Page: BugsFoundByGump
URL: http://wiki.apache.org/gump/BugsFoundByGump
no comment
Change Log:
--
@@ -5,5 +5,6 @@
Ceki,
see http://brutus.apache.org/...gump runs on 1.4, 1.5 and Kaffe.
-- dims
On Wed, 15 Dec 2004 15:27:09 +0100, Ceki Gülcü [EMAIL PROTECTED] wrote:
Stefan,
Many thanks for the detailed report and the proposed fix.
If my memory serves me correctly, we have already encountered the
Stefan Bodewig wrote:
On 14 Dec 2004, [EMAIL PROTECTED] wrote:
removed xerces and xalan deps, since JDK 1.4 comes w/ Crimson and
Xalan
Yes, but JDK 1.5 doesn't (no Xalan-J 2.x but XSLTC) and Kaffe
certainly doesn't.
Your change is fine if you need an arbitrary XML parser and XSLT
On Wed, 15 Dec 2004, Ceki Gülc [EMAIL PROTECTED] wrote:
If my memory serves me correctly, we have already encountered the
same exact problem previously and had solved it.
Quite possible, one of the nasty little BWC problems of JAXP 1.3.
This particular instance of the problem will get fixed
On Wed, 15 Dec 2004 17:24:53 +0100, Stefan Bodewig [EMAIL PROTECTED] wrote:
On Wed, 15 Dec 2004, Ceki Gülc [EMAIL PROTECTED] wrote:
[...]
On a different but related matter, I would love if Gump's scope (or
mission statement) could be extended to run tests on the many
different platforms it
On Wed, 15 Dec 2004, Ian Springer [EMAIL PROTECTED] wrote:
You're right, it looks like JDK 1.5 includes a bastardized version
of Xalan with the package name changed from org.apache.xalan to
com.sun.org.apache.xalan.
Not only have the packages been changed, you also don't get your
trusted
Currently Gump is reporting that 'jakarta-tomcat-jk-native-configure' is
failing, but this is really because 'jakarta-tomcat-jk-native-buildconf' is
failing (but not with a status code, so Gump has no way of knowing this).
The reason is that the buildconf.sh script depends on automake being
Bill Barker wrote:
Currently Gump is reporting that 'jakarta-tomcat-jk-native-configure' is
failing, but this is really because 'jakarta-tomcat-jk-native-buildconf' is
failing (but not with a status code, so Gump has no way of knowing this).
The reason is that the buildconf.sh script depends on
[EMAIL PROTECTED] wrote:
Stefano,
Some afterthoughts. Hopefully to help clarify. The scope of a Project
in our system (currently) is that of a build (a series of builds) for a
given
instance of (1) product-release on a given (2) target. This of course
means that a single configuration for a
[EMAIL PROTECTED] wrote:
Stefano:
See my responses below.
Stefano Mazzocchi [EMAIL PROTECTED] wrote on 12/10/2004 02:21:48 PM:
[EMAIL PROTECTED] wrote:
[...]
In my Build Results system, I have a schema that also includes a few
additional things:
- abritrary groupings of projects, which helps in
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 contact the folk at [EMAIL PROTECTED]
Project jdbm has an issue affecting its community integration.
This issue affects 3
Hi,
on the last run we've successfully built JUnit, which probably means
more of Swing is available to Kaffe now.
Looking into junit's build log, I see that javadoc failed because
Kaffe's version of javadoc doesn't seem to be compatible with Sun's
command line options.
Dalibor, can you provide
Date: 2004-12-15T05:22:36
Editor: DavanumSrinivas [EMAIL PROTECTED]
Wiki: Gump Wiki
Page: BugsFoundByGump
URL: http://wiki.apache.org/gump/BugsFoundByGump
no comment
New Page:
= Bugs found by Gump =
||Instance || Project || URL ||
||Kaffe|| xml-stylebook ||
There is a problem with run 'brutus-jdk15' (15122004_060001), location :
http://brutus.apache.org/gump/jdk15
The log ought be at:
http://brutus.apache.org/gump/jdk15/gump_log.txt
removed xerces and xalan deps, since JDK 1.4 comes w/ Crimson and
Xalan
Yes, but JDK 1.5 doesn't (no Xalan-J 2.x but XSLTC) and Kaffe
certainly doesn't.
You're right, it looks like JDK 1.5 includes a bastardized version of
Xalan with the package name changed from org.apache.xalan to
There is a problem with run 'brutus-kaffe' (15122004_150001), location :
http://brutus.apache.org/gump/kaffe
The log ought be at:
http://brutus.apache.org/gump/kaffe/gump_log.txt
Ceki Gülcü wrote:
Stefan,
Many thanks for the detailed report and the proposed fix.
If my memory serves me correctly, we have already encountered the same
exact problem previously and had solved it. This particular instance
of the problem will get fixed later today.
It's a good thing Gump
21 matches
Mail list logo
