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 siteAddress and
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
I have put a first cut at a mavenized lang site at
http://www.apache.org/~psteitz/docs/
There is nothing new or different in terms of content. Comments welcome.
There are a couple of errors that I know about -- the link in the upper
right does not work and should be replaced by the Commons
Commons Developers List
Subject: [lang] web site
I have put a first cut at a mavenized lang site at
http://www.apache.org/~psteitz/docs/
There is nothing new or different in terms of content. Comments welcome.
There are a couple of errors that I know about -- the link in the upper
right
__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 siteDirectory is correct in
I successfully performed a 'maven site:deploy' for [io] a few weeks ago
without a problem. As long at siteAddress and siteDirectory 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
Are we ready to move to the maven-generated site? If there are no
objections and no one more compe.. (er, I mean confident) wants to
step up, I will attempt the conversion. Ideas on how/what to improve
would be most welcome.
Phil
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