You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Shapira, Yoav" <Yo...@mpi.com> on 2004/09/16 17:11:09 UTC
Maintenance approach of log4j site
Hi,
When adding to the log4j FAQ earlier today, I noticed
/www/logging.apache.org/log4j (where the log4j site is stored, on
minotaur.apache.org) is a simple copy of the files in the
logging-log4j/docs CVS module. While this is an OK approach, I'd like
to adopt a better one and one that is becoming a de-facto standard among
other ASF projects.
That approach is to make /www/logging.apache.org/log4j an anonymous CVS
checkout of the logging-log4j/docs CVS module. With this approach:
- To update the site, simply go to /www/logging.apache.org/log4j and
type "cvs update"
- The site is automatically kept in sync with the docs in CVS, reducing
the possibility of doc changes being lost because they were modified in
one place and not another
This is not a big deal, as the current approach works and has for a
while. But I think it's a nice little enhancement to better regulate
our web site. This CVS approach is also used by Tomcat, the various
Jakarta-Commons projects, and Geronimo, among others.
I'll volunteer to do the move. It's not much of an effort really. The
important thing is once I announced it's done, committers updating the
site should do so via a CVS update (so you must update the docs in CVS
first, and committ hem), not via a manual copy.
If there are any objections to this, speak up ;)
Yoav Shapira
Millennium Research Informatics
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Maintenance approach of log4j site
Posted by Ceki Gülcü <ce...@qos.ch>.
Hi Yoav,
Actually, what you describe is the recommended way for all Logger
Services projects, as described in
http://logging.apache.org/site/logging-site.html
If you decide to use CVS to copy your project's web pages to the
web-server, then the pages should pertain to your project's CVS module
and not to the logging-site module. For various reasons, the log4j
web-site files are copied to our Web server machine using scp and not
CVS, so we cannot user log4j as an example here.
I can't think any good reason not to use CVS for log4j pages as well.
Here are some (probably obvious) pointers you might find useful:
1) On minator, there are several folders under
/www/logging.apache.org/log4j/docs/ which contains large amount of
automatically generated data. For example, docs/api/ and
docs/api-1.3/. These should probably not be managed by CVS.
If you remove the existing docs/ directory keeps a copy of these
directories in order to place back them again under docs/.
The same probably applies to docs/webstart/.
2) It might be safer to keep a backup copy of docs/ for a few weeks
until we make sure that all the files are there.
3) Good luck and thank you.
At 05:11 PM 9/16/2004, you wrote:
>Hi,
>When adding to the log4j FAQ earlier today, I noticed
>/www/logging.apache.org/log4j (where the log4j site is stored, on
>minotaur.apache.org) is a simple copy of the files in the
>logging-log4j/docs CVS module. While this is an OK approach, I'd like
>to adopt a better one and one that is becoming a de-facto standard among
>other ASF projects.
>
>That approach is to make /www/logging.apache.org/log4j an anonymous CVS
>checkout of the logging-log4j/docs CVS module. With this approach:
>- To update the site, simply go to /www/logging.apache.org/log4j and
>type "cvs update"
>- The site is automatically kept in sync with the docs in CVS, reducing
>the possibility of doc changes being lost because they were modified in
>one place and not another
>
>This is not a big deal, as the current approach works and has for a
>while. But I think it's a nice little enhancement to better regulate
>our web site. This CVS approach is also used by Tomcat, the various
>Jakarta-Commons projects, and Geronimo, among others.
>
>I'll volunteer to do the move. It's not much of an effort really. The
>important thing is once I announced it's done, committers updating the
>site should do so via a CVS update (so you must update the docs in CVS
>first, and committ hem), not via a manual copy.
>
>If there are any objections to this, speak up ;)
>
>Yoav Shapira
>Millennium Research Informatics
>
>
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary and/or privileged. This e-mail is intended only for the
>individual(s) to whom it is addressed, and may not be saved, copied,
>printed, disclosed or used by anyone else. If you are not the(an)
>intended recipient, please immediately delete this e-mail from your
>computer system and notify the sender. Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-dev-help@logging.apache.org
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Maintenance approach of log4j site
Posted by Ceki Gülcü <ce...@qos.ch>.
A working copy can contain files which are not managed by CVS. So there is
no reason to move
/x1/www/logging.apache.org/log4j/docs/webstart/chainsaw/ elsewhere.
At 11:44 PM 9/16/2004, you wrote:
>+1
>
>Only thing I can think of is that the Chainsaw distribution is currently
>sitting here:
>
>/x1/www/logging.apache.org/log4j/docs/webstart/chainsaw
>
>This is obviously not part of the CVS module. Unfortunately if we move it,
>people who are using Chainsaw via webstart will be forced to redownload it.
>Actually we'll need to come up with a strategy for informing the users of
>the move. I would appreciate if we could keep a symbolic link or something
>in the interim until we can move everyone across to the new Chainsaw launch
>link.
>
>cheers,
>
>Paul Smith
--
Ceki Gülcü
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Maintenance approach of log4j site
Posted by Paul Smith <ps...@aconex.com>.
+1
Only thing I can think of is that the Chainsaw distribution is currently
sitting here:
/x1/www/logging.apache.org/log4j/docs/webstart/chainsaw
This is obviously not part of the CVS module. Unfortunately if we move it,
people who are using Chainsaw via webstart will be forced to redownload it.
Actually we'll need to come up with a strategy for informing the users of
the move. I would appreciate if we could keep a symbolic link or something
in the interim until we can move everyone across to the new Chainsaw launch
link.
cheers,
Paul Smith
> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: Friday, September 17, 2004 1:11 AM
> To: Log4J Developers List
> Subject: Maintenance approach of log4j site
>
>
>
> Hi,
> When adding to the log4j FAQ earlier today, I noticed
> /www/logging.apache.org/log4j (where the log4j site is stored, on
> minotaur.apache.org) is a simple copy of the files in the
> logging-log4j/docs CVS module. While this is an OK approach, I'd like
> to adopt a better one and one that is becoming a de-facto standard among
> other ASF projects.
>
> That approach is to make /www/logging.apache.org/log4j an anonymous CVS
> checkout of the logging-log4j/docs CVS module. With this approach:
> - To update the site, simply go to /www/logging.apache.org/log4j and
> type "cvs update"
> - The site is automatically kept in sync with the docs in CVS, reducing
> the possibility of doc changes being lost because they were modified in
> one place and not another
>
> This is not a big deal, as the current approach works and has for a
> while. But I think it's a nice little enhancement to better regulate
> our web site. This CVS approach is also used by Tomcat, the various
> Jakarta-Commons projects, and Geronimo, among others.
>
> I'll volunteer to do the move. It's not much of an effort really. The
> important thing is once I announced it's done, committers updating the
> site should do so via a CVS update (so you must update the docs in CVS
> first, and committ hem), not via a manual copy.
>
> If there are any objections to this, speak up ;)
>
> Yoav Shapira
> Millennium Research Informatics
>
>
>
>
>
> This e-mail, including any attachments, is a confidential
> business communication, and may contain information that is
> confidential, proprietary and/or privileged. This e-mail is
> intended only for the individual(s) to whom it is addressed, and
> may not be saved, copied, printed, disclosed or used by anyone
> else. If you are not the(an) intended recipient, please
> immediately delete this e-mail from your computer system and
> notify the sender. Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org