Jason van Zyl wrote:
>
> Jon Stevens wrote:
>
> > on 3/5/01 3:26 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
> >
> > > We should decide what should be done befor this date: the two
> > > things that I would like to do code wise are clean up the configuration
> > > code and start using log4j. After that bug fixes and documentation.
> >
> > Update the TODO page then. :-)
>
> I'll start the list to get us rolling then ...
>
> o Configuration cleanup: I would like to use the Configuration class instead
> of
> Properties as it deals with multiple same name keys, includes, and deals
> with
> default values internally. This would clean up the Runtime, and all
> configuration
> issues will be handled by the Configuration class. The Configuration
> class is
> an amalgum of the
> VelocityResources/ExtendedProperties/ConfigurationRepository.
> The attempt was to make it work like a standard Properties class except
> it has
> more features.
I think that we really should consider this decision carefully. I
really like having the options of using the Properties to load - since I
would bet that the Properties class is very common for people to use in
their own apps, every java101 programmer understands how to use it, etc,
etc, etc
The multi-key problem only surfaced recently with the multi-node
template and jar paths, and that was solvable in the same way WM solved
it, by letting the property be free form, and letting the entity that
required multi-valued properties to parse in the way it needs.
Everything that we want to do could be achieved with the
java.util.Properties. If Configuration makes life easier internally to
justify the added code, then I am all for it, but I still think that we
should support the standard Properties object as a full functional
method of init.
The set-what-you-want-and-call-init method is quite simple....
> o Log4j: I would like to swtich to using log4j as it seems to be the most
> mature of the logging packages and the options provided by log4j
> are very desirable IMO. Rolling log files, or logging to a database (to
> go along with the data resource loader :-)), or logging via syslog. All
> these things are possible for minimal effort as log4j will do all the
> work :-)
can it be pluggable?
> o Get a copy of Alexandria running on the apache.org box so that we
> can have a link on our site to the javadocs. We can do this manually
> if necessary, but it would be nice to use Alexandria as that's what
> it's intended for. Hopefully Jeff Martin and Sam Ruby can help out
> with this so we will have Javadocs updated daily by the time we
> release.
Can we update javadocs whenever we want with that?
> o UML Diagrams: Even if they are quick it would be nice to have. I
> have asked a Turbiner (Ilkka Priha) if he could reverse engineer a
> set of diagrams like he did for Turbine.
>
> o Getting a mailing list archive working, or at least have a link
> to mail-archive.com at the bottom of the messages going out
> on the list.
>
> That's what I can think of off the top of my head. Just add what
> you feel is necessary and I will produce a todo from it
>
I'll dig up a bunch.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
