Hopefully got everything back in place. I'd avoid doing a general
"svn update" on all the log4j content since there hasn't been time
to review my changes: removing the ApacheCON US 2005 logo, updating
the copyright line and updating the log4j version to 1.3alpha-8 on
the documentation pa
On Jan 28, 2006, at 12:50 AM, Curt Arnold wrote:
Removed all the generated pages from the log4j SVN today. I was
running into problems when the Ant build would not regenerate the
web content after a fresh checkout and was baffled why generated
files were in the SVN. Just forgot about
On Jan 27, 2006, at 11:11 PM, Paul Smith wrote:
Err, i'm stuck.On people.apache.org, I go into /www/
logging./log4j.
But the docs directory is not under SVN control, so I can't seem to
update it.
Also, I can't check in the modified chainsaw.html file because it
is not under SVN
Err, i'm stuck.On people.apache.org, I go into /www/logging./
log4j.
But the docs directory is not under SVN control, so I can't seem to
update it.
Also, I can't check in the modified chainsaw.html file because it is
not under SVN control, so I obviously have to generate it somehow
Hi,
You also need to go to /www/logging.apache.org/log4j and issue an "svn
update" command ;)
Yoav
On 1/27/06, Paul Smith <[EMAIL PROTECTED]> wrote:
> Just wanted to check on the policy with respect to the log4j home
> page.I plan to make changes to the chainsaw page. I take it I
> just edit
Just wanted to check on the policy with respect to the log4j home
page.I plan to make changes to the chainsaw page. I take it I
just edit the XML, generate the html from the xdocs, and check both
xml & html into the source tree?
Do I also need to deploy the generated HTML, or does some
