On Thu, 15 Feb 2001, Geir Magnusson Jr. wrote:
> That's great!
>
> We as a project need to work out what to do with non-core things like
> this - I am sure since it was useful to you, it will be useful to many
> others. (Yo, Paulo!)
>
> Anyway, there are a few other things floating around that are non-core/
> non-basic but need to be kept somewhere.
>
> If we set up a site / place for non-officially-supported contributions /
> accessories, would you be willing to commit to support it?
If people are going to commit to supporting segments of
code, why do we necessarily have to go off-site to do this?
I think an org.apache.velocity.app package would do the
job. I don't think things like a DBResourceLoader, or
ServletResourceLoader are going to be abandoned and
I think it would be nice to have be in the velocity
CVS. We can definitely keep them in a separate JAR
file and keep them out of the core, but I think it would
be nice to keep them in CVS.
I think the idea for an VelocityCentral type site would
be good for things like apps made with Velocity, but
not the components to make the apps.
I think that it would be confusing and inconvenient
to have to grab resource loaders from somewhere other
then the velocity CVS, or a velocity dist. At least for things like a
resource loader: as a piece of code that doesn't
function apart from velocity. For other tools,
tools that might be used with any templating engine, or a general
servlet tool, I think it would be fine to keep them out
of velocity proper but I even think those could be
kept in velocity too.
jvz.
