So I'm getting ready to distribute some software written
using Velocity. Velocity is used as a sort of report
generator, my users can customize their reports by
changing velocity templates. I don't have any specific
questions, but if you have any general comments on this,
I'd like to hear them:
I plan to distribute this software as two jar files, one
containing my code/documentation/etc, and the other
containing jar files for all the 3rd party libraries required:
velocity, xerces, jdom, etc. Two advantages of this
scheme is that each jar file will fit on one floppy, and
(hopefully) the third party jar file will only change rarely.
Right now, I'm not including any velocity documentation, but
I do include links to the Velocity site. I may include
velocity documentation in the distribution if it is small enough
(distribution and docs).
I'm including velocity 1.0 (or maybe 0.72, I can't remember).
The next time I need to update the 3rd party jar file, I'll
include the most recent very stable velocity version. I'm
using very few features of velocity, and have not had problems
with bugs, so stablity is much more important to me than
getting the most recent release.
Anything I'm missing?
The exact product is aimed at a small niche.
It is a utility library to help people write Role Playing
Game software that helps Game Masters set up for a game.
If you don't know what "game master" or "role playing game"
means, you probably should not bother, but you can look at
the software here:
http://joshualevy.tripod.com/gmht/index.htm
http://groups.yahoo.com/group/gmht
(Although the current release is 0.5, previous releases did
not use Velocity.)
Joshua Levy
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
