On Sat, 5 Oct 2002 16:01:41 +0200, Aslak Hellesøy <[EMAIL PROTECTED]> wrote:
>
> The build process is currently quite complicated, and we have to improve
> that. The way I see it we have two options:
> a) Make a new branch in the xdoclet module and start on XDoclet 2 there.
> b) Make a new CVS module and code XDoclet 2 from scratch.
>
> With all the new initiatives (XGG, XRAI, more GUI plugins) + the various
> points in Mathias' list
> http://users.pandora.be/ees/xdoclet/development/design.html, I think we're
> better off going for alternative b). Tag handlers will disappear, we'll
Hi all,
If you decide to rewrite XDoclet please consider a strategy for
incorporating unit tests from the beginning. I much too often ran into
situations where parts of XDoclet didn't work any longer as expected
after checking out the latest stuff from CVS. It really bugged me up to
the point where I started writing some of the previously generated stuff
manually.
Httpunit, also on Sourceforge, is one of the best examples of how the
use of JUnit can be used to guarantee quality. I'm open to questions,
too.
Just my $0.02, tom
--
thomas quas | "The truth indeed has never been preached by the Buddha,
[EMAIL PROTECTED] | seeing that one has to realize it within oneself."
| -- Lamkara Sutra --
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
