We had our own build server just before we moved to apache. Since we already have to maintain the Wicket Stuff server, there is little incentive to add another maintenance item to our list. Keeping everything on one box is much easier for us.
There are a couple of hudson instances running, and we could probably piggyback on one of them, or request our own zone to do so. Martijn On 5/5/08, James Carman <[EMAIL PROTECTED]> wrote: > Why are we using a non-ASF build server (not meaning not an ASF > product, but not hosted by the ASF) to build ASF artifacts in the > first place? Shouldn't this sort of stuff be done on ASF hardware via > ASF processes? I can see the wicketstuff "stuff" being done with the > wicketstuff TeamCity instance, but not the Apache Wicket stuff. I > realize that this stuff is ASF licensed software, so it's no big deal > to re-distribute it. I'm just curious if there was an issue with the > processes/procedures of the ASF with respect to the wants/needs of the > Apache Wicket project. > > > p.s. By the way, that is officially the most times I've typed "stuff" > in one email. :) > > > On Sun, May 4, 2008 at 5:00 PM, Martijn Dashorst > > <[EMAIL PROTECTED]> wrote: > > > On 5/4/08, Frank Bille <[EMAIL PROTECTED]> wrote: > > > Shouldn't we just disable the apache build configuration and not the > > > build agent? In theory the wicketstuff build may still run. > > > > In practice most stuff projects depend on wicket core :) > > > > But you are right, that would be the best action, this is much easier > > and quicker. > > > > > > > > Martijn > > > > -- > > Buy Wicket in Action: http://manning.com/dashorst > > Apache Wicket 1.3.3 is released > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 > > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
