I discovered in last night's local Gump run that XML Commons has been
updated to require JAXP 1.3, which I didn't have installed locally (just the
java-xml-pack as suggested by xml-commons.xml). Brutus doesn't seem to run
at all since Wednesday, but I think it's going to get bitten pretty
Stefan Bodewig wrote:
On Wed, 09 Feb 2005, Peter Janes [EMAIL PROTECTED] wrote:
The way to fix the build is to use namespacing,
one way, not *the* way.
The other way is to use the xml descriptor instead of the properties
file as resource in the taskdef.
Ah, I should have left it to the Ant master
We do have a depend entry for ant-contrib which provides
that for task, but Gump does not seem to pick it up.
Is our descriptor missing something, e.g. a nested entry for
the ant or something? Sorry, i cannot figure it out.
ant-contrib recently removed the for task from the antcontrib.properties
Dalibor Topic wrote:
Traceback (most recent call last):
File gump.py, line 118, in ?
main(sys.argv)
File gump.py, line 108, in main
getattr(command, process)(options,arguments)
File /var/tmp/topic/gump/python/gump/commands/build.py, line 41, in process
workspace =
Gareth Webbley wrote:
The way I got around this problem was to cd to the cron directory and either
run gump.sh in that directory or python gump.py. There is another copy of
gump.py in the cron directory which works differently to the one in the root
directory. I think this is the one used in
Stefano Mazzocchi wrote:
The status of the gump.py file in the root is *up in the air* at best
and totally untested for a lot of things. In short, it's a mess.
[...]
So, for now, use the cron script or you can help me out and fix the
bugs :-)
Love to, but I think I've exhausted my Python
I've recently synced both the trunk and live branch of Gump (which are
identical as of revision 56892) and have a problem running both of them. If I
execute python2.3 gump.py build I get the following traceback:
Traceback (most recent call last):
File gump.py, line 118, in ?
I've recently synced both the trunk and live branch of Gump (which are
identical as of revision 56892) and have a problem running both of them. If I
execute python2.3 gump.py build I get the following traceback:
Traceback (most recent call last):
File gump.py, line 118, in ?
Gump wrote:
Dear Gumpmeisters,
The following 1 notifys should have been sent
Sorry folks, this run got away on me. Please go about your business,
nothing to see here. :)
--
Sometimes the Universe needs a change of perspective.
--J. Michael Straczynski
smime.p7s
Description:
Leo Simons wrote:
I will assert that the most serious concern with gump is that it is too
hard to use, understand or improve for non-gump-gurus. If this were a
componay and I were the boss, the first thing I would tell people to
work on is a much more readable and enticing website. Ie What is
Adam R. B. Jack wrote:
All builders (Ant|Maven|NAnt) and updaters (CVS|SVN|P4 -- I think) support:
debug=true|false
verbose=true|false
I didn't include anything specifically for debug/verbose in the P4 updater,
so it probably ignores those attributes. There's not much extra info that
it
I've written some basic Perforce support for Traditional Gump, based very
much on the cvs repository support. However, since Trad Gump is in the
process of being replaced by Python Gump, I'd like to migrate the Perforce
support as well.
Would anyone be able to provide pointers on what parts I
12 matches
Mail list logo
