You are viewing a plain text version of this content. The canonical link for it is here.
Posted to alexandria-dev@jakarta.apache.org by Sam Ruby <ru...@apache.org> on 2002/11/10 18:06:01 UTC
Gump changes
A number of gump changes that some might want to be aware of:
1) Due to space concerns, gump's output is moving from
daedalus.apache.org to icarus.apache.org. This includes build logs, cvs
extract snapshots, and nightly builds. If you have any urls which
reference one of these, simply change the first name in the URL from
either jakarta or xml to cvs.
Example: http://cvs.apache.org/builds/gump/latest/
2) Unless I hear significant objections, I plan to upgrade to JDK 1.4 as
there are getting to be too many failures as JDK 1.4 specific methods
are increasingly being used. Current examples include:
http://cvs.apache.org/builds/gump/2002-11-10/jakarta-bcel.html
http://cvs.apache.org/builds/gump/2002-11-10/jakarta-tomcat-catalina.html
3) I plan to move Gump out of Alexandria. My favorite suggestion to
date is from Costin: move Gump to jakarta-commons. If you care to
comment on this, please direct your replies to alexandria-dev.
- Sam Ruby
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Scott Sanders <sa...@apache.org>.
On Sun, 10 Nov 2002, Sam Ruby <ru...@apache.org> wrote:
> 3) I plan to move Gump out of Alexandria.
+1
> My favorite suggestion to date is from Costin: move Gump to
> jakarta-commons.
+1. Or to the incubator (to help gain developers). Just a thought.
I think that jakarta-commons, or commons for that matter (Gump can/should do more than java), would be a good move.
--
Scott Sanders - sanders@apache.org
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 10 Nov 2002, Sam Ruby <ru...@apache.org> wrote:
> 1) Due to space concerns, gump's output is moving from
> daedalus.apache.org to icarus.apache.org.
+1
Do you have a list of the projects you are doing the nightly builds
for so that we can notify them indivdually? I'll take care of Ant.
> 2) Unless I hear significant objections, I plan to upgrade to JDK
> 1.4
+0 - but I guess we'll simply swap one set of build problems for
another.
Just make sure you update gump.covalent.net as well (get it updated).
I still frequently use it to debug some problems.
> 3) I plan to move Gump out of Alexandria.
+1
> My favorite suggestion to date is from Costin: move Gump to
> jakarta-commons.
Works for me.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 11 Nov 2002, Stephen McConnell <mc...@apache.org> wrote:
> What is the size of the development community supporting gump ?
Four or five people have made commits to the Gump part of Alexandria
during the past three months. But most haven't touched Gump's code
but merely updated the project descriptors.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 2002/11/10 8:25 PM, "Stephen McConnell" <mc...@apache.org> wrote:
> What is the size of the development community supporting gump ?
1.3
Sam might be short, but he has .3 of someone else's personality!
=)
-jon
--
StudioZ.tv /\ Bar/Nightclub/Entertainment
314 11th Street @ Folsom /\ San Francisco
http://studioz.tv/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stephen McConnell <mc...@apache.org>.
Andrew C. Oliver wrote:
> Jon Scott Stevens wrote:
>
>> on 2002/11/10 9:06 AM, "Sam Ruby" <ru...@apache.org> wrote:
>>
>>
>>
>>> 3) I plan to move Gump out of Alexandria. My favorite suggestion to
>>> date is from Costin: move Gump to jakarta-commons. If you care to
>>> comment on this, please direct your replies to alexandria-dev.
>>>
>>> - Sam Ruby
>>>
>>
>>
>> Personally, I think it should just become a top level project. It is a
>> container for all the other projects and a very important part of the
>> whole
>> larger picture. Gump.apache.org
>>
>> -jon
>>
>>
>>
> +1
>
What is the size of the development community supporting gump ?
Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Jon Scott Stevens wrote:
>on 2002/11/10 9:06 AM, "Sam Ruby" <ru...@apache.org> wrote:
>
>
>
>>3) I plan to move Gump out of Alexandria. My favorite suggestion to
>>date is from Costin: move Gump to jakarta-commons. If you care to
>>comment on this, please direct your replies to alexandria-dev.
>>
>>- Sam Ruby
>>
>>
>
>Personally, I think it should just become a top level project. It is a
>container for all the other projects and a very important part of the whole
>larger picture. Gump.apache.org
>
>-jon
>
>
>
+1
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Costin Manolache wrote:
> Nicola Ken Barozzi wrote:
>
>>I don't like it to move under Jakarta Commons...
>
> Can you give any reasons for that ?
See below...
>>Probably ATM simply moving the codebase to its own gump CVS repo and
>>make its own mailing list would solve this handily, since we remain ATM
>>under Jakarta but move out of the Alexandria skin.
>
>
> The problem is growing its commmunity and improving a bit the code
> and usability.
>
> The reason I proposed jakarta-commons is that it's the best place
> where this can happen. If Sam is not afraid of losing control over
> gump ( which may happen in j-c ), than I can't see any reason to
> not have it in j-c.
Of course this is just MHO, I am not going to vote on this thing, since
I don't feel entitled to, because of my minimal code involvement with Gump.
I recall Sam having problems about changes in Ant that broke his builds,
and thus the creation of Gump (http://jakarta.apache.org/gump/why.html)
... I smell that this will bring the same problems, but if Sam is ok...
If users would just show interest and some patches, they would easily
become committers, and I fail to see why moving the code round will help
this involvement.
>>>>A solution would be to make two repos: gump and gump-repos, and have
>>>>gump-repos open to all *Apache* committers.
>>>
>>>
>>>Why? You can already host descriptors outside of Gump's control.
>>
>>The descriptors were initially all in the Gump repo for better control
>>and cross-project check.
>>
>>Making a common repo would continue this tentative, while not
>>relinquishing control of the whole Gump codebase to people that could
>>start bashing (am I being too defensive here?)
>
> Is 'relinquishing' control a problem ?
Could be.
> If the 'bashing' results in
> finding problems and improving gump - or even increasing awarness -
> then it's should be welcomed.
Of course. *If*
There is a "competing" Gump project called Maven (which started in Gump
BTW).
Maven developers have access to j-c.
Gump developers don't have access to Maven.
It's the same reason why Maven developer would not want Maven moved
under j-c.
Will this make Maven work nicer with Gump while not assimilating it?
Could be a deal.
If not, I wouldn't like it... but hey, this is where I'm being
defensive, maybe I'm just plain wrong.
>>As a start though I'd probably keep things as is, and suggest all
>>committers that ask the descriptor to be patched to move it to their
>>codebase and have it administered. Probably.
>
> I think the real issue is where to host gump's code - i.e. the xslt and
> java code.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Costin Manolache <cm...@yahoo.com>.
Nicola Ken Barozzi wrote:
> I don't like it to move under Jakarta Commons...
Can you give any reasons for that ?
> Probably ATM simply moving the codebase to its own gump CVS repo and
> make its own mailing list would solve this handily, since we remain ATM
> under Jakarta but move out of the Alexandria skin.
The problem is growing its commmunity and improving a bit the code
and usability.
The reason I proposed jakarta-commons is that it's the best place
where this can happen. If Sam is not afraid of losing control over
gump ( which may happen in j-c ), than I can't see any reason to
not have it in j-c.
>>>A solution would be to make two repos: gump and gump-repos, and have
>>>gump-repos open to all *Apache* committers.
>>
>>
>> Why? You can already host descriptors outside of Gump's control.
>
> The descriptors were initially all in the Gump repo for better control
> and cross-project check.
>
> Making a common repo would continue this tentative, while not
> relinquishing control of the whole Gump codebase to people that could
> start bashing (am I being too defensive here?)
Is 'relinquishing' control a problem ? If the 'bashing' results in
finding problems and improving gump - or even increasing awarness -
then it's should be welcomed.
> As a start though I'd probably keep things as is, and suggest all
> committers that ask the descriptor to be patched to move it to their
> codebase and have it administered. Probably.
I think the real issue is where to host gump's code - i.e. the xslt and
java code.
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Stefan Bodewig wrote:
> On Mon, 11 Nov 2002, Nicola Ken Barozzi <ni...@apache.org> wrote:
>
>
>>I second Jon, he is right.
>
> +0. I'm not that Gump qualifies from the community aspect for a
> top-level project.
Conceptually, Gump has a higher goal than just be part of Jakarta, and
it's possibly also cross-language. Remember I'm also a Forrest
committer, so I see the synergy between the projects of higher value to
Apache, and keep pursuing that vision.
I understand that community-wise it's not (yet) a top-level project, but
I don't like it to move under Jakarta Commons...
Probably ATM simply moving the codebase to its own gump CVS repo and
make its own mailing list would solve this handily, since we remain ATM
under Jakarta but move out of the Alexandria skin.
One step at a time.
> I'm in favor of moving it out of the Alexandria module, BTW.
+1
>>A solution would be to make two repos: gump and gump-repos, and have
>>gump-repos open to all *Apache* committers.
>
>
> Why? You can already host descriptors outside of Gump's control.
The descriptors were initially all in the Gump repo for better control
and cross-project check.
Making a common repo would continue this tentative, while not
relinquishing control of the whole Gump codebase to people that could
start bashing (am I being too defensive here?)
As a start though I'd probably keep things as is, and suggest all
committers that ask the descriptor to be patched to move it to their
codebase and have it administered. Probably.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 11 Nov 2002, Nicola Ken Barozzi <ni...@apache.org> wrote:
> I second Jon, he is right.
+0. I'm not that Gump qualifies from the community aspect for a
top-level project.
I'm in favor of moving it out of the Alexandria module, BTW.
> A solution would be to make two repos: gump and gump-repos, and have
> gump-repos open to all *Apache* committers.
Why? You can already host descriptors outside of Gump's control.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jon Scott Stevens wrote:
> on 2002/11/10 9:06 AM, "Sam Ruby" <ru...@apache.org> wrote:
>
>
>>3) I plan to move Gump out of Alexandria. My favorite suggestion to
>>date is from Costin: move Gump to jakarta-commons. If you care to
>>comment on this, please direct your replies to alexandria-dev.
>>
>>- Sam Ruby
>
>
> Personally, I think it should just become a top level project. It is a
> container for all the other projects and a very important part of the whole
> larger picture. Gump.apache.org
I second Jon, he is right.
The reason why Gump should be in jakarta-commons is that it's good for
projects to have control over their descriptors, but not the core.
A solution would be to make two repos: gump and gump-repos, and have
gump-repos open to all *Apache* committers.
My 2c
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Jon Scott Stevens wrote:
>on 2002/11/10 9:06 AM, "Sam Ruby" <ru...@apache.org> wrote:
>
>
>
>>3) I plan to move Gump out of Alexandria. My favorite suggestion to
>>date is from Costin: move Gump to jakarta-commons. If you care to
>>comment on this, please direct your replies to alexandria-dev.
>>
>>- Sam Ruby
>>
>>
>
>Personally, I think it should just become a top level project. It is a
>container for all the other projects and a very important part of the whole
>larger picture. Gump.apache.org
>
>-jon
>
>
>
+1
Re: Gump changes
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 2002/11/10 9:06 AM, "Sam Ruby" <ru...@apache.org> wrote:
> 3) I plan to move Gump out of Alexandria. My favorite suggestion to
> date is from Costin: move Gump to jakarta-commons. If you care to
> comment on this, please direct your replies to alexandria-dev.
>
> - Sam Ruby
Personally, I think it should just become a top level project. It is a
container for all the other projects and a very important part of the whole
larger picture. Gump.apache.org
-jon
--
StudioZ.tv /\ Bar/Nightclub/Entertainment
314 11th Street @ Folsom /\ San Francisco
http://studioz.tv/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 12 Nov 2002, Pier Fumagalli <pi...@betaversion.org> wrote:
> So I'm wondering why the heck I'm running that thing 4 times a day,
> if at the end, no one uses it...
Gump runs a couple of times a day on a couple of machines (this
includes running on nagoya). Those are linked from Gump's website as
intermediate (or experimental, depends on context) runs.
One run is the "official" nightly run, this one produces nightly
builds for a couple of sub-projects as a side-effect. This "official"
run is not performed on Nagoya.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 12 Nov 2002, Pier Fumagalli <pi...@betaversion.org> wrote:
> So I'm wondering why the heck I'm running that thing 4 times a day,
> if at the end, no one uses it...
Gump runs a couple of times a day on a couple of machines (this
includes running on nagoya). Those are linked from Gump's website as
intermediate (or experimental, depends on context) runs.
One run is the "official" nightly run, this one produces nightly
builds for a couple of sub-projects as a side-effect. This "official"
run is not performed on Nagoya.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Stefan Bodewig" <bo...@apache.org> wrote:
> On Mon, 11 Nov 2002, Pier Fumagalli <pi...@betaversion.org> wrote:
>
>> Huh? Why not leaving it on Nagoya?
>
> I don't think the "nightly" build is created on Nagoya, but on Sam's
> private machine.
So I'm wondering why the heck I'm running that thing 4 times a day, if at
the end, no one uses it... It's a nice way to waste 4 gigs of RAM, and
roughly 20 gigs of HDD.
Pier
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Stefan Bodewig" <bo...@apache.org> wrote:
> On Mon, 11 Nov 2002, Pier Fumagalli <pi...@betaversion.org> wrote:
>
>> Huh? Why not leaving it on Nagoya?
>
> I don't think the "nightly" build is created on Nagoya, but on Sam's
> private machine.
So I'm wondering why the heck I'm running that thing 4 times a day, if at
the end, no one uses it... It's a nice way to waste 4 gigs of RAM, and
roughly 20 gigs of HDD.
Pier
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 11 Nov 2002, Pier Fumagalli <pi...@betaversion.org> wrote:
> Huh? Why not leaving it on Nagoya?
I don't think the "nightly" build is created on Nagoya, but on Sam's
private machine.
> Hmm... Do I need to install 1.4.1 (latest) on Nago, then?
I think so.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 11 Nov 2002, Pier Fumagalli <pi...@betaversion.org> wrote:
> Huh? Why not leaving it on Nagoya?
I don't think the "nightly" build is created on Nagoya, but on Sam's
private machine.
> Hmm... Do I need to install 1.4.1 (latest) on Nago, then?
I think so.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 10/11/02 5:06 pm, "Sam Ruby" <ru...@apache.org> wrote:
> A number of gump changes that some might want to be aware of:
>
> 1) Due to space concerns, gump's output is moving from
> daedalus.apache.org to icarus.apache.org. This includes build logs, cvs
> extract snapshots, and nightly builds. If you have any urls which
> reference one of these, simply change the first name in the URL from
> either jakarta or xml to cvs.
>
> Example: http://cvs.apache.org/builds/gump/latest/
Huh? Why not leaving it on Nagoya? I mean, there is generated, you can live
it there and make few redirects on Daedalus...
> 2) Unless I hear significant objections, I plan to upgrade to JDK 1.4 as
> there are getting to be too many failures as JDK 1.4 specific methods
> are increasingly being used. Current examples include:
Hmm... Do I need to install 1.4.1 (latest) on Nago, then?
Pier
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 2002/11/10 9:06 AM, "Sam Ruby" <ru...@apache.org> wrote:
> 3) I plan to move Gump out of Alexandria. My favorite suggestion to
> date is from Costin: move Gump to jakarta-commons. If you care to
> comment on this, please direct your replies to alexandria-dev.
>
> - Sam Ruby
Personally, I think it should just become a top level project. It is a
container for all the other projects and a very important part of the whole
larger picture. Gump.apache.org
-jon
--
StudioZ.tv /\ Bar/Nightclub/Entertainment
314 11th Street @ Folsom /\ San Francisco
http://studioz.tv/
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Gump changes
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 10/11/02 5:06 pm, "Sam Ruby" <ru...@apache.org> wrote:
> A number of gump changes that some might want to be aware of:
>
> 1) Due to space concerns, gump's output is moving from
> daedalus.apache.org to icarus.apache.org. This includes build logs, cvs
> extract snapshots, and nightly builds. If you have any urls which
> reference one of these, simply change the first name in the URL from
> either jakarta or xml to cvs.
>
> Example: http://cvs.apache.org/builds/gump/latest/
Huh? Why not leaving it on Nagoya? I mean, there is generated, you can live
it there and make few redirects on Daedalus...
> 2) Unless I hear significant objections, I plan to upgrade to JDK 1.4 as
> there are getting to be too many failures as JDK 1.4 specific methods
> are increasingly being used. Current examples include:
Hmm... Do I need to install 1.4.1 (latest) on Nago, then?
Pier
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Jon Scott Stevens <jo...@latchkey.com>.
on 2002/11/10 9:06 AM, "Sam Ruby" <ru...@apache.org> wrote:
> 3) I plan to move Gump out of Alexandria. My favorite suggestion to
> date is from Costin: move Gump to jakarta-commons. If you care to
> comment on this, please direct your replies to alexandria-dev.
>
> - Sam Ruby
Personally, I think it should just become a top level project. It is a
container for all the other projects and a very important part of the whole
larger picture. Gump.apache.org
-jon
--
StudioZ.tv /\ Bar/Nightclub/Entertainment
314 11th Street @ Folsom /\ San Francisco
http://studioz.tv/
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Gump changes
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 10/11/02 5:06 pm, "Sam Ruby" <ru...@apache.org> wrote:
> A number of gump changes that some might want to be aware of:
>
> 1) Due to space concerns, gump's output is moving from
> daedalus.apache.org to icarus.apache.org. This includes build logs, cvs
> extract snapshots, and nightly builds. If you have any urls which
> reference one of these, simply change the first name in the URL from
> either jakarta or xml to cvs.
>
> Example: http://cvs.apache.org/builds/gump/latest/
Huh? Why not leaving it on Nagoya? I mean, there is generated, you can live
it there and make few redirects on Daedalus...
> 2) Unless I hear significant objections, I plan to upgrade to JDK 1.4 as
> there are getting to be too many failures as JDK 1.4 specific methods
> are increasingly being used. Current examples include:
Hmm... Do I need to install 1.4.1 (latest) on Nago, then?
Pier
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org