Henri Yandell wrote:
The psteitz Lang docs aren't there anymore it seems. Do they completely
replicate the current Lang page for information?
Yes. I just copied lang.xml from the commons xdocs and adjusted a couple
of links. If you update lang to grab the /xdocs and run maven
site:generate locall
The psteitz Lang docs aren't there anymore it seems. Do they completely
replicate the current Lang page for information?
Hen
On Mon, 3 Nov 2003, __matthewHawthorne wrote:
> I successfully performed a 'maven site:deploy' for [io] a few weeks ago
> without a problem. As long at and are
> corre
I successfully performed a 'maven site:deploy' for [io] a few weeks ago
without a problem. As long at and are
correct, it should go smoothly. I would suggest doing it on
cvs.apache.org, since you'll avoid the overhead of copying the site
across the network - but either way works fine.
Eith
__matthewHawthorne wrote:
I don't think that the HTML for each commons project's site is stored in
CVS, only the main commons HTML. Log in to cvs.apache.org, cd to
/www/jakarta.apache.org/commons and do a 'cvs diff', you'll see what I
mean.
Also, as long as the is correct in lang's project.xm
Very nice!
One thing I have notices with Maven sites is that hyperlinks often include
the space AFTER a word end. Is that a bug in Maven or in the data you feed
it?
Gary
> -Original Message-
> From: Phil Steitz [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 02, 2003 23:10
> To: Jakar
Sounds like a good idea. I think that detailed descriptions and
examples for each package would be good additions to the Maven site...
creating a lightweight user manual of sorts.
It's always a hard choice to decide what to put in package.html and what
to put in a user manual. Maven seems gre
