JMeter site

[Jordi Salvat i Alabart]

Hi.

As you may be aware of, I broke the way the JMeter site used to be published :-(

I still believe the approach of keeping in CVS only things that can't be obtained from source is cleaner, and better in the long term; but I need to reinstate a practical way to publish the docs.

Possible ways:
a/ Undo my change and add back the generated docs to CVS
b/ Have the nightly build republish the docs every day
c/ Have the nightly build create a docs distribution, which someone would need to pull and publish (just as we did when they were in CVS).
d/ �Other ideas?

a/ Has three problems:
1/ As said, needs "redundant" stuff to be kept in CVS. I don't like this -- although I admit it's a matter of taste.
2/ Requires developers to check-in produced docs in addition to the source xdocs whenever they make a change. Not a big deal, but it's easy to forget and may cause conflicts from time to time
3/ It's difficult to verify the content before publishing

b/ is great because it keeps things up-to-date and requires no invervention, but of course we may occasionally find our site totally broken.

c/ looks great, but I'm not sure how confortable it will be for whoever has to do the work -- and we'll make him responsible for the checking, which is probably unfair.

Anyone can think of a d/ or an e/? Arguments for or against each of the aproaches?

FYI, most --but not all-- jakarta projects use a/. I don't know exactly what the others (e.g. jakarta-oro) do.

Salut,

Jordi.


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>