On Tue, 20 Jul 2004 06:53:04 -0400, Ted Husted <[EMAIL PROTECTED]> wrote:
> On Mon, 19 Jul 2004 21:21:52 -0700, Martin Cooper wrote:
> >ï(BTW, that's something I think we should develop a policy on, so
> >ïthat we're not seen as making arbitrary decisions in this area, but
> >ïthat's another topic entirely.)
> 
> I think the decision would have to depend on who is going to maintain the glue.
> 
> A case in point is the VelTools. There's some Struts glue that is currently being 
> maintained there. I encouraged that since the people interested in the glue were 
> members of the Velocity community. A volunteer shouldn't have to follow a DEV list 
> to maintain code, they should maintain code because they are following a DEV list. 
> :) Of course, that's changed a bit now, and we have VelStrutsTools people who hang 
> out here now, so today it could go either way.

We have precedents for dealing with this that seem to work fine:

* File upload -- generic code in separate (Commons) package; glue in Struts
* Chain integration -- same thing

If the Tiles folks want to create a Struts-free distribution, two
separate modules (generic and glue) are certainly possible.  And, as
far as I'm concerned, the generic one is welcome to stay here.

> 
> In a volunteer organization, some decisions may seem arbitrary, since the volunteers 
> can be arbitrary, and decisions without volunteers don't exist. :)
> 
> 
> 
> -Ted.
> 

Craig

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to