"Craig R. McClanahan" <[EMAIL PROTECTED]> wrote on 15/10/2002 02:20:01 AM:
> > > On Mon, 14 Oct 2002 [EMAIL PROTECTED] wrote: > > > > > Is there a rule somewhere about not having sandbox components as a > > dependency? > > At a minimum, I think you can infer an indirect rule from the following > conventions: > > * You can't release a Sandbox component at all -- it's just > a wad-o-code. > > * You can't release a Commons component that depends on > non-released other code. > > Struts has some interim dependencies on a sandbox component or two, but > that will need to be resolved before a final Struts 1.1 release. Craig, out of curiosity, do you know where these conventions are laid out? Did I notice struts having 1.1 beta release(s) with sandbox dependencies? > Craig Don't get me wrong, I'm all for this as a 'rule', as it forces stuff out of the sandbox, but I like things to be documented so the next person knows too. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers
