OK, I seem to have found the bug: the checkout rule for wicketstuff-scriptaculous was:
+:trunk/wicket-contrib-scriptaculous:. however, recently someone renamed the wicket-contrib-scriptaculous directory in the svn repository to wicketstuff-scriptaculous, making this checkout rule invalid. The bug is then: that a bad checkout rule in one build-configuration can invalidate all build configurations sharing that scm root. Martijn On Mon, May 26, 2008 at 11:25 PM, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Currently the builds for wicketstuff projects are failing because > somehow the server doesn't know how to checkout the sources. I am not > sure how this is possible, since this setup has worked for quite a > while. > > Did someone edit the configuration in a way that caused this? > > I have also submitted a bug report with jetbrains to get an > explanation for the odd behavior: > > Most of the projects are setup such that they share the wicketstuff > repository and use checkout rules to check out into a separate > directory. > > So wicketstuff-minis checks out into wicketstuff-minis, and > wicket-contrib-scriptaculous into wicketstuff-scriptaculous. > > However, when I currently start the build of wicketstuff-minis, > teamcity tries to check out wicketstuff-scriptaculous. > > I hope to resolve this soon. > > 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
