On Tue, 30 Jul 2002, Vincent Massol <[EMAIL PROTECTED]> wrote: > You mean XDoclet ?
It's been changing 8-) First it has been xdoclet, then it has been mx4j that couldn't work with CVS HEAD of xdoclet (which still is an xdoclet problem, of course), then it's been Tomcat 4 itself that used the wrong Jasper branch (and I guess it'd still do if all prereqs were there), now it's mx4j again ... > Then let's consider XDoclet an installed package until someone > reports it builds fine ... ? It builds fine - at least the jars. The build failures occur during documentation creation and don't affect any builds depending on xdoclet right now. But that doesn't take away anything from your point. > Don't you think there should be a policy like: a project which > doesn't build for the past X weeks/months would go as an installed > package until the build is fixed, at which point it will be > restored, or something like that ? It depends on the interest in getting that project under Gump's control, I guess. If I was using xdoclet, I'd want to know that they are changing their task interface in a backwards incompatible way. Maybe it is not that good idea to make your nightly build system rely on too many other projects, then. It's probably rather easy to have two project definitions, one that used installed packages and one that uses the latest and most broken code 8-). Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
