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 Curt Arnold <ca...@apache.org> on 2007/08/31 00:08:45 UTC
Eliminating PluginConfigurator
PluginConfiguration was getting a little stale relative to 1.2.15's
DOMConfigurator. I could have updated PluginConfigurator or added a
dependency to extras and replaced PluginConfigurator with
org.apache.log4j.extras.DOMConfigurator, however the value of using
component with pre-1.2.15 versions of log4j seems pretty small, so
made component depend on log4j 1.2.15 and removed the
PluginConfigurator and related code from component. Chainsaw had a
dependency on PluginConfigurator, but since it already had a log4j
1.2.15 dependency, just switched it over the the log4j 1.2.15
DOMConfigurator.
The new web site is live and log4j 1.2.15 and extras appear to have
propagated to the mirrors, but are not yet in the ibiblio
repository. Will need to get an official announcement out.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Eliminating PluginConfigurator
Posted by Curt Arnold <ca...@apache.org>.
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
> Great!
>
> One thing I notice: the path to Chainsaw is a bit different now.
> That's
> not a bad thing, but could we redirect the old site & Chainsaw
> webstart
> link to the new locations?
It wasn't intentional, but looks like I just overlooked the log4j/
docs part of the URL. Also, looks like I didn't realized the
dependencies that the Webstart file had. I'll try to put it together
at the old place. When we get ready to release Chainsaw, then I'll
add a rewrite rules to redirect to the new place.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Eliminating PluginConfigurator
Posted by Scott Deboy <sd...@comotivsystems.com>.
Apologies - the old Chainsaw URL was http://logging.apache.org/log4j/docs/chainsaw.html, which now redirects as expected.
Re: dependency listings - on page: http://logging.apache.org/chainsaw/dependencies.html
The first entry in the 'Dependency Listings' section is for Chainsaw 'companion' at: http://logging.apache.org:80/log4j/companions/chainsaw
Which doesn't exist. The other links work.
Thanks
Scott
-----Original Message-----
From: Curt Arnold [mailto:carnold@apache.org]
Sent: Fri 8/31/2007 10:39 PM
To: Log4J Developers List
Subject: Re: Eliminating PluginConfigurator
On Aug 31, 2007, at 9:23 PM, Scott Deboy wrote:
> It looks like Chainsaw is still at:
> http://logging.apache.org/chainsaw/download.html
That is expected. The "new" Maven generated chainsaw content is
below http://logging.apache.org/chainsaw.
On http://logging.apache.org/chainsaw/download.html, the links are to
the old locations. That should change when we get Maven building the
webstart stuff. Then we'd have redirects at the old locations
pointing to the new locations.
>
> instead of:
> http://logging.apache.org/log4j/docs/chainsaw/download.html
>
I've put the old content up on http://people.apache.org/~carnold/
log4j/docs/index.html.
I reviewed the old site source and I didn't see that URL. There was
http://logging.apache.org/log4j/docs/chainsaw.html and http://
logging.apache.org/log4j/docs/install-chainsaw.html (which might have
been blank). I've added redirects for log4j/docs/chainsaw.html and
log4j/docs/install-chainsaw.html to redirect to l.a.o/chainsaw/
index.html and for index.html, manual.html and download to redirect
to the corresponding log4j/1.2 documents.
> I also noticed the dependency listings at http://logging.apache.org/
> chainsaw/dependencies.html don't resolve correctly.
Could you be specific? The only thing I noticed is that the URL's
had the :80 port specifier that I used as a kludge to get the Maven
breadcrumbs to distinguish between links within the release and the
parent links (for example, without the :80 the links in the log4j
distribution would assume that the LS web site was just one directory
up and log4cxx up and over instead of on http://logging.apache.org).
I noticed that distributionnotes.html and zeroconf.html did not
contain the links from chainsaw.html, so I updated those. I also
fixed a typo in the sample XML document and switch site-deploy to use
file protocol instead of scp in the site-deploy process.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Eliminating PluginConfigurator
Posted by Curt Arnold <ca...@apache.org>.
On Aug 31, 2007, at 9:23 PM, Scott Deboy wrote:
> It looks like Chainsaw is still at:
> http://logging.apache.org/chainsaw/download.html
That is expected. The "new" Maven generated chainsaw content is
below http://logging.apache.org/chainsaw.
On http://logging.apache.org/chainsaw/download.html, the links are to
the old locations. That should change when we get Maven building the
webstart stuff. Then we'd have redirects at the old locations
pointing to the new locations.
>
> instead of:
> http://logging.apache.org/log4j/docs/chainsaw/download.html
>
I've put the old content up on http://people.apache.org/~carnold/
log4j/docs/index.html.
I reviewed the old site source and I didn't see that URL. There was
http://logging.apache.org/log4j/docs/chainsaw.html and http://
logging.apache.org/log4j/docs/install-chainsaw.html (which might have
been blank). I've added redirects for log4j/docs/chainsaw.html and
log4j/docs/install-chainsaw.html to redirect to l.a.o/chainsaw/
index.html and for index.html, manual.html and download to redirect
to the corresponding log4j/1.2 documents.
> I also noticed the dependency listings at http://logging.apache.org/
> chainsaw/dependencies.html don't resolve correctly.
Could you be specific? The only thing I noticed is that the URL's
had the :80 port specifier that I used as a kludge to get the Maven
breadcrumbs to distinguish between links within the release and the
parent links (for example, without the :80 the links in the log4j
distribution would assume that the LS web site was just one directory
up and log4cxx up and over instead of on http://logging.apache.org).
I noticed that distributionnotes.html and zeroconf.html did not
contain the links from chainsaw.html, so I updated those. I also
fixed a typo in the sample XML document and switch site-deploy to use
file protocol instead of scp in the site-deploy process.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Eliminating PluginConfigurator
Posted by Scott Deboy <sd...@comotivsystems.com>.
Correction - only http://logging.apache.org/log4j/companions/chainsaw is not resolving.
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell: 503.997.1367
Fax: 503.222.0185
sdeboy@comotivsystems.com
www.comotivsystems.com
-----Original Message-----
From: Scott Deboy [mailto:sdeboy@comotivsystems.com]
Sent: Fri 8/31/2007 7:23 PM
To: Log4J Developers List
Subject: RE: Eliminating PluginConfigurator
It looks like Chainsaw is still at:
http://logging.apache.org/chainsaw/download.html
instead of:
http://logging.apache.org/log4j/docs/chainsaw/download.html
I also noticed the dependency listings at http://logging.apache.org/chainsaw/dependencies.html don't resolve correctly.
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell: 503.997.1367
Fax: 503.222.0185
sdeboy@comotivsystems.com
www.comotivsystems.com
-----Original Message-----
From: Curt Arnold [mailto:carnold@apache.org]
Sent: Fri 8/31/2007 3:37 PM
To: Log4J Developers List
Subject: Re: Eliminating PluginConfigurator
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
> Great!
>
> One thing I notice: the path to Chainsaw is a bit different now.
> That's
> not a bad thing, but could we redirect the old site & Chainsaw
> webstart
> link to the new locations?
>
>
> Scott Deboy
>
Chainsaw downloads should be fixed now. The log4j 1.2.15 jars have
made it to the ibiblio repo. I think everything is now set for an
announcement.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Eliminating PluginConfigurator
Posted by Scott Deboy <sd...@comotivsystems.com>.
It looks like Chainsaw is still at:
http://logging.apache.org/chainsaw/download.html
instead of:
http://logging.apache.org/log4j/docs/chainsaw/download.html
I also noticed the dependency listings at http://logging.apache.org/chainsaw/dependencies.html don't resolve correctly.
Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Telephone: 503.224.7496
Cell: 503.997.1367
Fax: 503.222.0185
sdeboy@comotivsystems.com
www.comotivsystems.com
-----Original Message-----
From: Curt Arnold [mailto:carnold@apache.org]
Sent: Fri 8/31/2007 3:37 PM
To: Log4J Developers List
Subject: Re: Eliminating PluginConfigurator
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
> Great!
>
> One thing I notice: the path to Chainsaw is a bit different now.
> That's
> not a bad thing, but could we redirect the old site & Chainsaw
> webstart
> link to the new locations?
>
>
> Scott Deboy
>
Chainsaw downloads should be fixed now. The log4j 1.2.15 jars have
made it to the ibiblio repo. I think everything is now set for an
announcement.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Eliminating PluginConfigurator
Posted by Curt Arnold <ca...@apache.org>.
On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:
> Great!
>
> One thing I notice: the path to Chainsaw is a bit different now.
> That's
> not a bad thing, but could we redirect the old site & Chainsaw
> webstart
> link to the new locations?
>
>
> Scott Deboy
>
Chainsaw downloads should be fixed now. The log4j 1.2.15 jars have
made it to the ibiblio repo. I think everything is now set for an
announcement.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Eliminating PluginConfigurator
Posted by Scott Deboy <sd...@comotivsystems.com>.
Great!
One thing I notice: the path to Chainsaw is a bit different now. That's
not a bad thing, but could we redirect the old site & Chainsaw webstart
link to the new locations?
Scott Deboy
-----Original Message-----
From: Curt Arnold [mailto:carnold@apache.org]
Sent: Thursday, August 30, 2007 3:09 PM
To: Log4J Developers List
Subject: Eliminating PluginConfigurator
PluginConfiguration was getting a little stale relative to 1.2.15's
DOMConfigurator. I could have updated PluginConfigurator or added a
dependency to extras and replaced PluginConfigurator with
org.apache.log4j.extras.DOMConfigurator, however the value of using
component with pre-1.2.15 versions of log4j seems pretty small, so
made component depend on log4j 1.2.15 and removed the
PluginConfigurator and related code from component. Chainsaw had a
dependency on PluginConfigurator, but since it already had a log4j
1.2.15 dependency, just switched it over the the log4j 1.2.15
DOMConfigurator.
The new web site is live and log4j 1.2.15 and extras appear to have
propagated to the mirrors, but are not yet in the ibiblio
repository. Will need to get an official announcement out.
---------------------------------------------------------------------
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