> (i) in order to generate the complete API documentation (currently the
> tools packages are missing) I'd suggest to apply the following diff:
I don't want API documentation generated for classes that aren't APIs ...
ie. interfaces that I want to be able to freely change without impacting
user code. Its actually extremely confusing for users to see a million
packages and try and figure out which ones they should consider amenable to
extension. (On the other hand, it probably wouldn't be such a bad idea to
JavaDoc the tools package).
> (ii) I found it somewhat inconvienient that the build file generates the
> documentation and libs and stuff in a separate directory
> (../hibernate-<version>). IMHO, this introduces unncessesary hassle with
> IDE paths as soon as I update my sandbox after a version change; I'd
> rather see the generated stuff stay in the sandbox. Is there any chance
> we can change this? I could help out.
I'm selfishly designing the build script to make it as convenient as
possible for _me_ to do a binary file release from CVS. You should be able
to accommodate different needs by setting build properties.
peace
Gavin
|
