Andi Vajda <va...@apache.org> wrote: > If Apache Forrest, which is used to produce the web site, can be used to > generate plain text, then this should be used for sure. What I don't want > to do is maintain two versions of the docs, even one pagers.
No, of course not. That's why I use ReST for the UpLib docs. I know nothing about Apache Forrest. > > 4. If there's a top-level "build.xml" file, lots of users (me, too :-) > > will think that they can just type "ant" to build the package. That > > should either "just work", or you should rename the build.xml file > > to something less obvious, like "to-be-invoked-by-the-Makefile.xml". > > Renaming build.xml to something more obscure could be done. > Would you like to send in a patch ? Didn't I just do that :-? No, I'll let you deal with it. > Sadly, the alternative here is autoconf. If you'd like to write an autoconf > script that works for all the variants of Python/Java/OS currently supported > in the Makefile, that would be excellent. Yes, I've already got most of that for UpLib. > Unless you're on Mac, editing JCC's setup.py is also required. If you write > an autoconf script for PyLucene, be sure to also include the generation of > JCC's setup.py, otherwise you've only addressed half of the problem. Right. > I expect that cracking the nut of finding the JDK on each and every Linux > distro is going to present a challenge. Providing command line arguments to > override what configure finds is probably a must. Exactly. Linux/Java is a mess -- whoops, I meant to say, a seething ferment of opportunity! I've got a script called "figure-linux-java.py". Bill
