15 May 14:45
Re: [groovy-dev] Groovy Build System
From: Jochen Theodorou <blackdrag@...>
Subject: Re: [groovy-dev] Groovy Build System
Newsgroups: gmane.comp.lang.groovy.devel
Date: 2008-05-15 12:45:39 GMT
Subject: Re: [groovy-dev] Groovy Build System
Newsgroups: gmane.comp.lang.groovy.devel
Date: 2008-05-15 12:45:39 GMT
Hans Dockter schrieb: > > On May 15, 2008, at 1:44 PM, Jochen Theodorou wrote: > >> Paul King schrieb: >>> I vote betamax!>>> No, not getting into the debate. I think we are in early days >>> in the build tool wars and I would like to think all sides will >>> greatly improve over the coming year or so. >>> I just had one point to make with Russel's comment below: >>>> [...] The current Ant build for >>>> example handles all these issues thanks to Paul's sterling efforts. >>> Actually, there are still some manual steps which Jochen does >>> which we could (should!) automate but haven't yet. >> >> yes... I would for example not like to upload the javadoc on our >> website without rsync. rsync is very fast and the docs are mostly not >> changing much (if 10% of the pages do change it is already very much). >> rsync is very nice here, because t checks the files on the server and >> uploads only the files I really need. Since I have a slow internet >> connection (128kb upstream only), it is very nice to have that part >> done in a short time. > > I would have thought Stuttgart is a high bandwidth paradise :). I have a VDSL box in front of my house, so I could be much faster... well, there are different reasons I use the current conncetion and have not switched yet >> Uploading one zip takes easily 15 minutes here. I do upload the zips >> manually, because what ever is used for the zips to upload seems to >> simply stop if there is a connection problem.. well maybe it is not >> like this anymore, because uploading the jars usually works... but >> they are smaller.. don't know. What I also have to do manually is >> changing the version information and doing the branching.. but doing >> the branching did become so easy with svn... that's not a problem. >> Then there is also that "ant deploy" does many things "ant dist" does >> too... like building the javadoc... our build takes not very long, but >> it would be nice to not to have to run it multiple times. > > I think its nice when its fully automated. That way the process is > described in an executable document (the build script). It is reliable > and imposes less stress. It can also be easily done when you are on > holiday ;). hehe, true bye blackdrag -- -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead (http://groovy.codehaus.org) http://blackdragsview.blogspot.com/ http://www.g2one.com/ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
>>> No, not getting into the debate. I think we are in early days
>>> in the build tool wars and I would like to think all sides will
>>> greatly improve over the coming year or so.
>>> I just had one point to make with Russel's comment below:
>>>> [...] The current Ant build for
>>>> example handles all these issues thanks to Paul's sterling efforts.
>>> Actually, there are still some manual steps which Jochen does
>>> which we could (should!) automate but haven't yet.
>>
>> yes... I would for example not like to upload the javadoc on our
>> website without rsync. rsync is very fast and the docs are mostly not
>> changing much (if 10% of the pages do change it is already very much).
>> rsync is very nice here, because t checks the files on the server and
>> uploads only the files I really need. Since I have a slow internet
>> connection (128kb upstream only), it is very nice to have that part
>> done in a short time.
>
> I would have thought Stuttgart is a high bandwidth paradise :).
I have a VDSL box in front of my house, so I could be much faster...
well, there are different reasons I use the current conncetion and have
not switched yet
>> Uploading one zip takes easily 15 minutes here. I do upload the zips
>> manually, because what ever is used for the zips to upload seems to
>> simply stop if there is a connection problem.. well maybe it is not
>> like this anymore, because uploading the jars usually works... but
>> they are smaller.. don't know. What I also have to do manually is
>> changing the version information and doing the branching.. but doing
>> the branching did become so easy with svn... that's not a problem.
>> Then there is also that "ant deploy" does many things "ant dist" does
>> too... like building the javadoc... our build takes not very long, but
>> it would be nice to not to have to run it multiple times.
>
> I think its nice when its fully automated. That way the process is
> described in an executable document (the build script). It is reliable
> and imposes less stress. It can also be easily done when you are on
> holiday ;).
hehe, true
bye blackdrag
RSS Feed