And what is the use of publishing jars that are built against the latest
jars ? They will be useless in a real environment or even test
environments and will probably not get any support from the project
concerning. It simply is not a nightly build against the dependencies
set by the project.
- Original Message -
From: robert burrell donkin [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Sunday, June 20, 2004 10:01 AM
Subject: Re: [VOTE] retire java gump
On 19 Jun 2004, at 22:49, Sebastian Bazley wrote:
[...]
The -1 was primarily intended to ensure
robert burrell donkin wrote:
they could easily be hosted offshore with traditional gump but unless
some people step up and make the offshore builds happen, they won't.
for me, this is the major obstacle and is independent of the decision
to officially stop development of traditional gump.
I
Adam R. B. Jack wrote:
We could take the opportunity to:
1) Move Gump (Python) core to SVN
2) Move Gump Metadata to a separate CVS repository [to move to SVN one day
in the future, when all ASF committer are comfortable w/ SVN].
We could leave the current repository as is, tagged but even CVS HEAD
+1
I'd rather try to find the time to understand Gumpy in order to
implement the things missing (javadoc for example). Playing catch-up
with Gumpy isn't fun and nothing should stop Gumpy to go into ways
that Java Gump won't follow fast enough.
Stefan
Stefan Bodewig wrote:
+1
I'd rather try to find the time to understand Gumpy in order to
implement the things missing (javadoc for example). Playing catch-up
with Gumpy isn't fun and nothing should stop Gumpy to go into ways
that Java Gump won't follow fast enough.
+1
--
Stefano.
smime.p7s
- Original Message -
From: Michael Davey [EMAIL PROTECTED]
To: Gump code and data [EMAIL PROTECTED]
Sent: Tuesday, June 08, 2004 5:07 PM
Subject: Re: [VOTE] retire java gump
Leo Simons wrote:
Hi gang!
And now for something completely different...
Saw both Adam and Stefan
Hi gang!
And now for something completely different...
Saw both Adam and Stefan suggest this recently. I concur. Let's retire
(kill off sounds way to harsh for this faithful servant!) the java
version of gump. The python one is now superior in most ways, and Adam
keeps getting a headache
+1 from me.
On Tue, 08 Jun 2004 17:25:23 +0200, Leo Simons [EMAIL PROTECTED] wrote:
Hi gang!
And now for something completely different...
Saw both Adam and Stefan suggest this recently. I concur. Let's retire
(kill off sounds way to harsh for this faithful servant!) the java
version
Let's retire the java version of gump.
+1. And with thanks for the years of service...
regards,
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Leo Simons wrote:
Hi gang!
And now for something completely different...
Saw both Adam and Stefan suggest this recently. I concur. Let's retire
(kill off sounds way to harsh for this faithful servant!) the java
version of gump. The python one is now superior in most ways, and Adam
keeps getting
I'd suggest tagging CVS and making it clear that java gump may deviate
from documentation, etc but permit changes to the code.
We could take the opportunity to:
1) Move Gump (Python) core to SVN
2) Move Gump Metadata to a separate CVS repository [to move to SVN one day
in the future, when all
+1 for stopping maintenance on and running java gump.
Mvgr,
Martin
On Tue, 2004-06-08 at 17:25, Leo Simons wrote:
Hi gang!
And now for something completely different...
Saw both Adam and Stefan suggest this recently. I concur. Let's retire
(kill off sounds way to harsh for this faithful
13 matches
Mail list logo
