Dear Gumpmeisters,
The following 4 nags should have been sent
*** G U M P
[EMAIL PROTECTED]: jakarta-tapestry/ognl failed
[EMAIL PROTECTED]: javasrc/javasrc failed
[EMAIL PROTECTED]: eyebrowse/eyebrowse failed
[EMAIL PROTECTED]:
> > Running gump once without offline ought to correct this?
>
> I can try that. Is this just once after install?
Yes, unless you keep the resultant repository, tar it up, and install it as
well.
- Brett
> Someone has deleted the local repository that you were using. Until all
the
> maven plugins you have use project.properties overrides, you'll have to
> maintain a local repository with the JARs they need.
Strange, 'cos I doubt there was ever a non-offline run. Hmm, I wonder if it
ever worked on
Someone has deleted the local repository that you were using. Until all the
maven plugins you have use project.properties overrides, you'll have to
maintain a local repository with the JARs they need.
Running gump once without offline ought to correct this?
BTW, we are getting really close to rel
The Maven hasn't been updated, nor should have the project. The Maven is
being called using --offline, so oughtn't be network savvy. Still something
has changed, 'cos this started failing.
Any guesses how & why this would start failing (about 4 runs ago)?
http://brutus.apache.org/gump/public/jaka
ajack 2004/05/10 21:20:01
Modified:python/gump/model server.py
server hermes.xml
python/gump/core commandLine.py gumprun.py engine.py
python/gump/document/forrest documenter.py
Log:
1) Set hermes down
2) Respect server status (e.g.
On Monday 10 May 2004 16:20, Stefan Bodewig wrote:
> On Sat, 8 May 2004, Peter Donald <[EMAIL PROTECTED]> wrote:
> > I have still gotten about 5 related gump mails in the last week -
> > could someone look at removing me from ALL gump notifications.
> You know you have commit access to the Gump mo
> I've created a /usr/local/gump/test/gump parallel to
> /usr/local/gump/public/gump on brutus. This is a unit test workspace that
> has metadata constructs, but doesn't even have contents to build. The
> purpose of this workspace is to allow fast runs, to generally test the
code.
>
> Nick and I a
ajack 2004/05/10 14:34:09
Modified:.gumpy.py
Log:
If is a TTY cat log to screen.
Revision ChangesPath
1.29 +8 -2 gump/gumpy.py
Index: gumpy.py
===
RCS file: /home/cvs/gump/gumpy.p
> Brutus is up again. Sam and I found the problem. It simply wasn't
loading
> the network driver, so there was no network connectivity. Thom fixed it.
> We're not sure why, but it *appears* that the debian discover wasn't
finding
> and loading the network driver.
Thanks guys.
Most likely the
bodewig 2004/05/10 01:12:29
Modified:project checkstyle.xml
Log:
checkstyle wants to use Anakia
Revision ChangesPath
1.27 +3 -0 gump/project/checkstyle.xml
Index: checkstyle.xml
===
RCS fi
ajack 2004/05/10 10:25:24
Modified:project jakarta-commons.xml
Log:
Experimental change, to help commons-id
Revision ChangesPath
1.126 +2 -2 gump/project/jakarta-commons.xml
Index: jakarta-commons.xml
bodewig 2004/05/10 01:19:15
Modified:project incubator-altrmi.xml
Log:
Remove Peter's address
Revision ChangesPath
1.25 +0 -2 gump/project/incubator-altrmi.xml
Index: incubator-altrmi.xml
==
bodewig 2004/05/10 01:15:10
Modified:project james-server.xml qdox.xml
Log:
Replace Peter's address
Revision ChangesPath
1.6 +1 -1 gump/project/james-server.xml
Index: james-server.xml
===
Brutus is up again. Sam and I found the problem. It simply wasn't loading
the network driver, so there was no network connectivity. Thom fixed it.
We're not sure why, but it *appears* that the debian discover wasn't finding
and loading the network driver.
--- Noel
Sam, et al.
Can you take a look at brutus
Noel J. Bergman wrote:
-bash-2.05b$ ssh [EMAIL PROTECTED]
ssh: connect to host brutus.apache.org port 22: Host is down
-bash-2.05b$ ssh [EMAIL PROTECTED]
ssh: connect to host brutus.apache.org port 22: Operation timed out
brutus is running. I can
Adam R. B. Jack wrote:
Any input on this folks? Choices:
Do we change our id's to be full artefact ids, or add separate?
I think we bite the bullet and change our id's to be artefact ids (changing
metadata as we need). Any thoughts?
I think changing the ID is better than adding a new
--
Any input on this folks? Choices:
To: "Gump code and data" <[EMAIL PROTECTED]>
Sent: Wednesday, May 05, 2004 11:29 AM
Subject: Maven/Gump & Artefact/Jar Identifiers
> I tinkered with using Maven to build commons-id. Some success, but the
> problems come down to artefact identifiers. I.e. co
All,
I took Gump down on Hermes, and it'll either stay down (or find some idle
time slot, or something).
The infrastructure@ folks are curious as to the outcome, and how Java
operated on FreeBSD. If you have time, please meet them on their list and
update them. I'm not up to discussing the topic
On Sat, 8 May 2004, Peter Donald <[EMAIL PROTECTED]> wrote:
> I have still gotten about 5 related gump mails in the last week -
> could someone look at removing me from ALL gump notifications.
Done, at least for all descriptors I could access. Don't know about
the external ones.
You know you ha
n2.jar:/data3/gump/ant/dist/lib/ant-trax.jar:/data3/gump/ant/dist/lib/ant.jar:/data3/gump/ant/dist/lib/ant-nodeps.jar:/data3/gump/jakarta-commons/logging/dist/commons-logging.jar:/data3/gump/jakarta-commons/logging/dist/commons-logging-api.jar:/data3/gump/jakarta-commons/codec/dist
21 matches
Mail list logo
