Dear Gumpmeisters,
The following 9 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Module icu4j failed
[EMAIL PROTECTED]: Module xdoclet success, but with warnings.
[EMAIL PROTECTED]: Module smartfrog success, but
Dear Gumpmeisters,
The following 9 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Module icu4j failed
[EMAIL PROTECTED]: Module xdoclet success, but with warnings.
[EMAIL PROTECTED]: Module smartfrog success, but
Issue Subscription
Filter: open gump issues (36 issues)
Subscriber: gump@jakarta.apache.org
Project: Gump
Resolution: Unresolved
Key Summary
GUMP-131Build fails with build timed out
http://issues.apache.org/jira/browse/GUMP-131
GUMP-130Comprehensive integration test
Is there a way to increase this timeout, or remove it altogether?
I see this in the code:
TIMEOUT=60*60 # 60 minutes (in seconds)
if os.environ.has_key('GUMP_TIMEOUT'):
TIMEOUT = string.atoi(os.environ['GUMP_TIMEOUT'])
Setting to 0 will (I believe) remove it.
Gumpers,
What is the issue with Lucene building with Gump? To me it looks as
if its not doing a clean build and thus cannot find the JAR that was
successfully built in a past run because its looking for it by a
different dated name.
What does it take to get a clean build going? Should
There is a problem with run 'brutus-kaffe' (15052005_210002), location :
http://brutus.apache.org/gump/kaffe
The log ought be at:
http://brutus.apache.org/gump/kaffe/gump_log.txt
There is a problem with run 'brutus-kaffe' (15052005_210002), location :
http://brutus.apache.org/gump/kaffe
The log ought be at:
http://brutus.apache.org/gump/kaffe/gump_log.txt
