On Mon, 04 Aug 2003 22:31:12 -0700, Kimbro Staken wrote:
> OK, this has been bugging me for a while so I have to ask. What is the
> logic behind the way Xindice is being packaged now? There's a Jar file and
> a war. I know what the war file is for, but why is it packaged with no
> documentation at all? And I'm completely befuddled by the jar file. What
> happened to actually shipping something that was useful and at least made
> an attempt to explain how to use it? Why were all the supporting files
> stripped out of the builds? Or are the builds just not being packaged
> properly?
I was just thinking along the same lines. I've been trying to figure out
what packages should be in dist. Off the top of my head I see the
following components to the dist.
server: a packaged version configured so you can unpack and run xindice.{sh,bat}
(which I think should be renamed to xindice-server.{sh,bat}) and have a
standalone server. It would be even nicer if you could just run something
like java -jar xindice-server.jar.
client: the command line tool packaged and able to run with something like
java -jar xindice-client.jar.
war: The war file for distribution, we should verify that it installs and
deploys in jetty and tomcat ... others?
src: a grab of the source tree, with enough contents to build server,
client and war.
examples: the examples packaged with source and binaries
docs: api, user and developer documentation.
anything else?
-k.
