You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@logging.apache.org by Stefan Bodewig <bo...@apache.org> on 2012/06/10 11:18:19 UTC
Steps for Producr Sites? (was Re: Logging web sites)
Hi all,
On 2012-06-10, Ralph Goers wrote:
> We really don't need to use the maven publish plugin as I've checked
> in the each project in its own release directly and then used a
> symlink to point the project site to the specific release. Each of
> the other sub-sites should do the same thing.
I missed most of the thread, been busy elsewhere, sorry. I'd like to
add log4net to the site "the right way", what do I need to do?
This is my understanding
(1) check in the log4net site wherever I want
(2) create a symlink from where I commited the site to content/log4net
(3) un-indent log4net in extpath.txt
Is this correct?
Problems I currently see:
* the log4net site is generated by Maven and has inconsistent line-ends,
is there any better way than Ant's fixcrlf task to fix that? Our
build already includes NAnt and Maven, I'd prefer to avoid adding a
third build tool 8-)
Mid-term log4net may be better off using the CMS directly, but that's
something we need to discuss.
* I don't know how and where to perform step (2) from above.
Stefan
Re: Steps for Producr Sites? (was Re: Logging web sites)
Posted by Christian Grobmeier <gr...@gmail.com>.
>> until I manually promote it to production, right?
>> How can I promote a site?
>
> No. The sub-projects go directly from your local area into the production site. They do not get committed to staging. The staging site is used only by stuff that directly uses the CMS build process. The ext paths.txt file identifies the directories in the production site that are to be ignored by the CMS system.
>
OK. In this case we might consider implementing a mvn site:stage which
"deploys" a test site to p.a.o or somewhere else.
I think this is useful for voting
Re: Steps for Producr Sites? (was Re: Logging web sites)
Posted by Ralph Goers <ra...@dslextreme.com>.
On Jun 12, 2012, at 4:33 AM, Christian Grobmeier wrote:
> On Tue, Jun 12, 2012 at 8:57 AM, Ralph Goers <ra...@dslextreme.com> wrote:
>> Well, I use mvn site:stage-deploy for Log4j 2 to get the full site content. But that is required for a multi-project site. So, yes, you are correct. If mvn site:deploy could deploy directly into svn we could then use it.
>
>
> OK cool. When I committed the site, then it can be seen here:
> loggingtest.staging.apache.org
>
> until I manually promote it to production, right?
> How can I promote a site?
No. The sub-projects go directly from your local area into the production site. They do not get committed to staging. The staging site is used only by stuff that directly uses the CMS build process. The ext paths.txt file identifies the directories in the production site that are to be ignored by the CMS system.
Ralph
Re: Steps for Producr Sites? (was Re: Logging web sites)
Posted by Christian Grobmeier <gr...@gmail.com>.
On Tue, Jun 12, 2012 at 8:57 AM, Ralph Goers <ra...@dslextreme.com> wrote:
> Well, I use mvn site:stage-deploy for Log4j 2 to get the full site content. But that is required for a multi-project site. So, yes, you are correct. If mvn site:deploy could deploy directly into svn we could then use it.
OK cool. When I committed the site, then it can be seen here:
loggingtest.staging.apache.org
until I manually promote it to production, right?
How can I promote a site?
Cheers
>
> Ralph
>
>
>
> On Jun 11, 2012, at 11:38 PM, Christian Grobmeier wrote:
>
>> Thank you Ralph for this excellent guide.
>>
>> Do I understand correctly - so far we cannot use something like "mvn
>> site:deploy". We bascially need to generate the site locally and copy
>> the content locally to a new repository (the cms one). Is that
>> correct?
>>
>> Cheers
>>
>> On Mon, Jun 11, 2012 at 7:18 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>> See http://wiki.apache.org/logging/ManagingTheWebSite
>>>
>>> Ralph
>>>
>>> On Jun 10, 2012, at 8:58 AM, Ralph Goers wrote:
>>>
>>> I plan to document this on the wiki when I get home later today. The process
>>> isn't quite as you have listed.
>>>
>>> 1. Check out the production web site.
>>> 2. Create a log4xxx directory adjacent to the log4j directory,
>>> 3. Underneath that directory create a directory for the releases of the
>>> component such as log4xxx-1.8.
>>> 4. Copy the release website into that directory.
>>> 5. In your log4xxx directory create a symlink of 1.x to log4xxx-1.8. "ln -s
>>> log4xxx-1.8 1.x" on a Mac or unix system. Windows doesn't support links
>>> afaik.
>>> 6. Make sure all that is added to svn and commit it.
>>> 7. In the main web site check that index.twig and the navbar template
>>> reference your component as "log4xxx/1.x".
>>> 8. Unindent your component in extpaths.txt.
>>>
>>> If you want to use the CMS directly it is certainly easy to do.
>>>
>>> Sent from my iPad
>>>
>>> On Jun 10, 2012, at 2:18 AM, Stefan Bodewig <bo...@apache.org> wrote:
>>>
>>> Hi all,
>>>
>>>
>>> On 2012-06-10, Ralph Goers wrote:
>>>
>>>
>>> We really don't need to use the maven publish plugin as I've checked
>>>
>>> in the each project in its own release directly and then used a
>>>
>>> symlink to point the project site to the specific release. Each of
>>>
>>> the other sub-sites should do the same thing.
>>>
>>>
>>> I missed most of the thread, been busy elsewhere, sorry. I'd like to
>>>
>>> add log4net to the site "the right way", what do I need to do?
>>>
>>>
>>> This is my understanding
>>>
>>>
>>> (1) check in the log4net site wherever I want
>>>
>>>
>>> (2) create a symlink from where I commited the site to content/log4net
>>>
>>>
>>> (3) un-indent log4net in extpath.txt
>>>
>>>
>>> Is this correct?
>>>
>>>
>>> Problems I currently see:
>>>
>>>
>>> * the log4net site is generated by Maven and has inconsistent line-ends,
>>>
>>> is there any better way than Ant's fixcrlf task to fix that? Our
>>>
>>> build already includes NAnt and Maven, I'd prefer to avoid adding a
>>>
>>> third build tool 8-)
>>>
>>>
>>> Mid-term log4net may be better off using the CMS directly, but that's
>>>
>>> something we need to discuss.
>>>
>>>
>>> * I don't know how and where to perform step (2) from above.
>>>
>>>
>>> Stefan
>>>
>>>
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>
--
http://www.grobmeier.de
https://www.timeandbill.de
Re: Steps for Producr Sites? (was Re: Logging web sites)
Posted by Ralph Goers <ra...@dslextreme.com>.
Well, I use mvn site:stage-deploy for Log4j 2 to get the full site content. But that is required for a multi-project site. So, yes, you are correct. If mvn site:deploy could deploy directly into svn we could then use it.
Ralph
On Jun 11, 2012, at 11:38 PM, Christian Grobmeier wrote:
> Thank you Ralph for this excellent guide.
>
> Do I understand correctly - so far we cannot use something like "mvn
> site:deploy". We bascially need to generate the site locally and copy
> the content locally to a new repository (the cms one). Is that
> correct?
>
> Cheers
>
> On Mon, Jun 11, 2012 at 7:18 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>> See http://wiki.apache.org/logging/ManagingTheWebSite
>>
>> Ralph
>>
>> On Jun 10, 2012, at 8:58 AM, Ralph Goers wrote:
>>
>> I plan to document this on the wiki when I get home later today. The process
>> isn't quite as you have listed.
>>
>> 1. Check out the production web site.
>> 2. Create a log4xxx directory adjacent to the log4j directory,
>> 3. Underneath that directory create a directory for the releases of the
>> component such as log4xxx-1.8.
>> 4. Copy the release website into that directory.
>> 5. In your log4xxx directory create a symlink of 1.x to log4xxx-1.8. "ln -s
>> log4xxx-1.8 1.x" on a Mac or unix system. Windows doesn't support links
>> afaik.
>> 6. Make sure all that is added to svn and commit it.
>> 7. In the main web site check that index.twig and the navbar template
>> reference your component as "log4xxx/1.x".
>> 8. Unindent your component in extpaths.txt.
>>
>> If you want to use the CMS directly it is certainly easy to do.
>>
>> Sent from my iPad
>>
>> On Jun 10, 2012, at 2:18 AM, Stefan Bodewig <bo...@apache.org> wrote:
>>
>> Hi all,
>>
>>
>> On 2012-06-10, Ralph Goers wrote:
>>
>>
>> We really don't need to use the maven publish plugin as I've checked
>>
>> in the each project in its own release directly and then used a
>>
>> symlink to point the project site to the specific release. Each of
>>
>> the other sub-sites should do the same thing.
>>
>>
>> I missed most of the thread, been busy elsewhere, sorry. I'd like to
>>
>> add log4net to the site "the right way", what do I need to do?
>>
>>
>> This is my understanding
>>
>>
>> (1) check in the log4net site wherever I want
>>
>>
>> (2) create a symlink from where I commited the site to content/log4net
>>
>>
>> (3) un-indent log4net in extpath.txt
>>
>>
>> Is this correct?
>>
>>
>> Problems I currently see:
>>
>>
>> * the log4net site is generated by Maven and has inconsistent line-ends,
>>
>> is there any better way than Ant's fixcrlf task to fix that? Our
>>
>> build already includes NAnt and Maven, I'd prefer to avoid adding a
>>
>> third build tool 8-)
>>
>>
>> Mid-term log4net may be better off using the CMS directly, but that's
>>
>> something we need to discuss.
>>
>>
>> * I don't know how and where to perform step (2) from above.
>>
>>
>> Stefan
>>
>>
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
Re: Steps for Producr Sites? (was Re: Logging web sites)
Posted by Christian Grobmeier <gr...@gmail.com>.
Thank you Ralph for this excellent guide.
Do I understand correctly - so far we cannot use something like "mvn
site:deploy". We bascially need to generate the site locally and copy
the content locally to a new repository (the cms one). Is that
correct?
Cheers
On Mon, Jun 11, 2012 at 7:18 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> See http://wiki.apache.org/logging/ManagingTheWebSite
>
> Ralph
>
> On Jun 10, 2012, at 8:58 AM, Ralph Goers wrote:
>
> I plan to document this on the wiki when I get home later today. The process
> isn't quite as you have listed.
>
> 1. Check out the production web site.
> 2. Create a log4xxx directory adjacent to the log4j directory,
> 3. Underneath that directory create a directory for the releases of the
> component such as log4xxx-1.8.
> 4. Copy the release website into that directory.
> 5. In your log4xxx directory create a symlink of 1.x to log4xxx-1.8. "ln -s
> log4xxx-1.8 1.x" on a Mac or unix system. Windows doesn't support links
> afaik.
> 6. Make sure all that is added to svn and commit it.
> 7. In the main web site check that index.twig and the navbar template
> reference your component as "log4xxx/1.x".
> 8. Unindent your component in extpaths.txt.
>
> If you want to use the CMS directly it is certainly easy to do.
>
> Sent from my iPad
>
> On Jun 10, 2012, at 2:18 AM, Stefan Bodewig <bo...@apache.org> wrote:
>
> Hi all,
>
>
> On 2012-06-10, Ralph Goers wrote:
>
>
> We really don't need to use the maven publish plugin as I've checked
>
> in the each project in its own release directly and then used a
>
> symlink to point the project site to the specific release. Each of
>
> the other sub-sites should do the same thing.
>
>
> I missed most of the thread, been busy elsewhere, sorry. I'd like to
>
> add log4net to the site "the right way", what do I need to do?
>
>
> This is my understanding
>
>
> (1) check in the log4net site wherever I want
>
>
> (2) create a symlink from where I commited the site to content/log4net
>
>
> (3) un-indent log4net in extpath.txt
>
>
> Is this correct?
>
>
> Problems I currently see:
>
>
> * the log4net site is generated by Maven and has inconsistent line-ends,
>
> is there any better way than Ant's fixcrlf task to fix that? Our
>
> build already includes NAnt and Maven, I'd prefer to avoid adding a
>
> third build tool 8-)
>
>
> Mid-term log4net may be better off using the CMS directly, but that's
>
> something we need to discuss.
>
>
> * I don't know how and where to perform step (2) from above.
>
>
> Stefan
>
>
--
http://www.grobmeier.de
https://www.timeandbill.de
Re: Steps for Producr Sites? (was Re: Logging web sites)
Posted by Ralph Goers <ra...@dslextreme.com>.
See http://wiki.apache.org/logging/ManagingTheWebSite
Ralph
On Jun 10, 2012, at 8:58 AM, Ralph Goers wrote:
> I plan to document this on the wiki when I get home later today. The process isn't quite as you have listed.
>
> 1. Check out the production web site.
> 2. Create a log4xxx directory adjacent to the log4j directory,
> 3. Underneath that directory create a directory for the releases of the component such as log4xxx-1.8.
> 4. Copy the release website into that directory.
> 5. In your log4xxx directory create a symlink of 1.x to log4xxx-1.8. "ln -s log4xxx-1.8 1.x" on a Mac or unix system. Windows doesn't support links afaik.
> 6. Make sure all that is added to svn and commit it.
> 7. In the main web site check that index.twig and the navbar template reference your component as "log4xxx/1.x".
> 8. Unindent your component in extpaths.txt.
>
> If you want to use the CMS directly it is certainly easy to do.
>
> Sent from my iPad
>
> On Jun 10, 2012, at 2:18 AM, Stefan Bodewig <bo...@apache.org> wrote:
>
>> Hi all,
>>
>> On 2012-06-10, Ralph Goers wrote:
>>
>>> We really don't need to use the maven publish plugin as I've checked
>>> in the each project in its own release directly and then used a
>>> symlink to point the project site to the specific release. Each of
>>> the other sub-sites should do the same thing.
>>
>> I missed most of the thread, been busy elsewhere, sorry. I'd like to
>> add log4net to the site "the right way", what do I need to do?
>>
>> This is my understanding
>>
>> (1) check in the log4net site wherever I want
>>
>> (2) create a symlink from where I commited the site to content/log4net
>>
>> (3) un-indent log4net in extpath.txt
>>
>> Is this correct?
>>
>> Problems I currently see:
>>
>> * the log4net site is generated by Maven and has inconsistent line-ends,
>> is there any better way than Ant's fixcrlf task to fix that? Our
>> build already includes NAnt and Maven, I'd prefer to avoid adding a
>> third build tool 8-)
>>
>> Mid-term log4net may be better off using the CMS directly, but that's
>> something we need to discuss.
>>
>> * I don't know how and where to perform step (2) from above.
>>
>> Stefan
Re: Steps for Producr Sites?
Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-06-11, Ralph Goers wrote:
> On Jun 10, 2012, at 11:23 PM, Hervé BOUTEMY <he...@free.fr> wrote:
>> Le dimanche 10 juin 2012 22:22:06 Ralph Goers a écrit :
>> As for symbolic links, I'll have to look at the svn documentation but
>> I'm pretty sure there is a way to create the link in svn without
>> doing it on your local file system. However, on unix-based systems
>> an svn commit propagates the links automatically into svn.
>> I fear it's not as easy as expected: when I worked on it for Maven,
>> Daniel gave me a complex magic recipe with svnmucc and opened an
>> issue in svnmucc to add native support for it see
>> http://subversion.tigris.org/issues/show_bug.cgi?id=4142
>> But this hasn't been implemented yet, and last time I tried to use
>> the magic recipe, I couldn't make it work...
> Wonderful. During this process someone else mentioned svnmucc but it
> isn't installed on my Mac and I couldn't find it in any of the
> downloads.
Let's not make this a blocker.
Yes, most of log4net's development will happen on Windows but right now
this is not an issue as I can deal with the docs and my primary platform
is Linux. Once we need a Windows solution, svnmucc may be ready.
Stefan
Re: Steps for Producr Sites?
Posted by Ivan Habunek <iv...@gmail.com>.
On 11 June 2012 16:20, Christian Grobmeier <gr...@gmail.com> wrote:
>> Wonderful. During this process someone else mentioned svnmucc but it isn't installed on my Mac and I couldn't find it in any of the downloads.
>
> hm, i found the source here:
> http://opensource.apple.com/source/subversion/subversion-44/subversion/tools/client-side/svnmucc/svnmucc.c
>
> but not here:
> http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/
My windows distribution (SilkSVN) has svnmucc included.
You should look through the SVN OSX binary distributions linked on the
official site:
http://subversion.apache.org/packages.html#osx
Regards,
Ivan
Re: Steps for Producr Sites?
Posted by Christian Grobmeier <gr...@gmail.com>.
On Mon, Jun 11, 2012 at 4:10 PM, Ralph Goers <rg...@apache.org> wrote:
> On Jun 10, 2012, at 11:23 PM, Hervé BOUTEMY <he...@free.fr> wrote:
>
>> Le dimanche 10 juin 2012 22:22:06 Ralph Goers a écrit :
>> As for symbolic links, I'll have to look at the svn documentation but I'm pretty sure there is a way to create the link in svn without doing it on your local file system. However, on unix-based systems an svn commit propagates the links automatically into svn.
>>
>>
>> I fear it's not as easy as expected: when I worked on it for Maven, Daniel gave me a complex magic recipe with svnmucc and opened an issue in svnmucc to add native support for it
>> see http://subversion.tigris.org/issues/show_bug.cgi?id=4142
>>
>> But this hasn't been implemented yet, and last time I tried to use the magic recipe, I couldn't make it work...
>>
>
> Wonderful. During this process someone else mentioned svnmucc but it isn't installed on my Mac and I couldn't find it in any of the downloads.
hm, i found the source here:
http://opensource.apple.com/source/subversion/subversion-44/subversion/tools/client-side/svnmucc/svnmucc.c
but not here:
http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/
> Ralph
--
http://www.grobmeier.de
https://www.timeandbill.de
Re: Steps for Producr Sites?
Posted by Ralph Goers <rg...@apache.org>.
On Jun 10, 2012, at 11:23 PM, Hervé BOUTEMY <he...@free.fr> wrote:
> Le dimanche 10 juin 2012 22:22:06 Ralph Goers a écrit :
> As for symbolic links, I'll have to look at the svn documentation but I'm pretty sure there is a way to create the link in svn without doing it on your local file system. However, on unix-based systems an svn commit propagates the links automatically into svn.
>
>
> I fear it's not as easy as expected: when I worked on it for Maven, Daniel gave me a complex magic recipe with svnmucc and opened an issue in svnmucc to add native support for it
> see http://subversion.tigris.org/issues/show_bug.cgi?id=4142
>
> But this hasn't been implemented yet, and last time I tried to use the magic recipe, I couldn't make it work...
>
Wonderful. During this process someone else mentioned svnmucc but it isn't installed on my Mac and I couldn't find it in any of the downloads.
Ralph
Re: Steps for Producr Sites?
Posted by Hervé BOUTEMY <he...@free.fr>.
Le dimanche 10 juin 2012 22:22:06 Ralph Goers a écrit :
As for symbolic links, I'll have to look at the svn documentation but I'm
pretty sure there is a way to create the link in svn without doing it on your
local file system. However, on unix-based systems an svn commit propagates the
links automatically into svn.
I fear it's not as easy as expected: when I worked on it for Maven, Daniel
gave me a complex magic recipe with svnmucc and opened an issue in svnmucc to
add native support for it
see http://subversion.tigris.org/issues/show_bug.cgi?id=4142
But this hasn't been implemented yet, and last time I tried to use the magic
recipe, I couldn't make it work...
Regards,
Hervé
Re: Steps for Producr Sites?
Posted by Ralph Goers <ra...@dslextreme.com>.
On Jun 10, 2012, at 9:28 PM, Stefan Bodewig wrote:
> On 2012-06-11, Stefan Bodewig wrote:
>
>> On 2012-06-10, Ralph Goers wrote:
>
>>> 1. Check out the production web site.
>
>> Please remember to put the svn URL here.
>
> I think it is
> <https://svn.apache.org/repos/infra/websites/production/loggingtest/content/>
>
> Stefan
Yes, that is the production url. To edit the stuff managed by the CMS you want https://svn.apache.org/repos/asf/logging/site/branches/cms/trunk/. Every time you edit something there the CMS will rebuild the staging site. You can use https://cms.apache.org/#bookmark to view the staging site, edit content and promote to production.
As for symbolic links, I'll have to look at the svn documentation but I'm pretty sure there is a way to create the link in svn without doing it on your local file system. However, on unix-based systems an svn commit propagates the links automatically into svn.
Ralph
Re: Steps for Producr Sites?
Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-06-11, Stefan Bodewig wrote:
> On 2012-06-10, Ralph Goers wrote:
>> 1. Check out the production web site.
> Please remember to put the svn URL here.
I think it is
<https://svn.apache.org/repos/infra/websites/production/loggingtest/content/>
Stefan
Re: Steps for Producr Sites?
Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-06-10, Ralph Goers wrote:
> I plan to document this on the wiki when I get home later today.
Many thanks.
> The process isn't quite as you have listed.
Good I haven't done much, yet 8-)
> 1. Check out the production web site.
Please remember to put the svn URL here.
> 2. Create a log4xxx directory adjacent to the log4j directory,
> 3. Underneath that directory create a directory for the releases of
> the component such as log4xxx-1.8.
> 4. Copy the release website into that directory.
> 5. In your log4xxx directory create a symlink of 1.x to
> log4xxx-1.8. "ln -s log4xxx-1.8 1.x" on a Mac or unix system. Windows
> doesn't support links afaik.
Not a problem for me, but may be problematic for future log4net release
managers. Windows is certainly the "natural" development environment
there.
> 6. Make sure all that is added to svn and commit it.
> 7. In the main web site check that index.twig and the navbar template
> reference your component as "log4xxx/1.x".
> 8. Unindent your component in extpaths.txt.
Thanks
Stefan
Re: Steps for Producr Sites? (was Re: Logging web sites)
Posted by Ralph Goers <rg...@apache.org>.
I plan to document this on the wiki when I get home later today. The process isn't quite as you have listed.
1. Check out the production web site.
2. Create a log4xxx directory adjacent to the log4j directory,
3. Underneath that directory create a directory for the releases of the component such as log4xxx-1.8.
4. Copy the release website into that directory.
5. In your log4xxx directory create a symlink of 1.x to log4xxx-1.8. "ln -s log4xxx-1.8 1.x" on a Mac or unix system. Windows doesn't support links afaik.
6. Make sure all that is added to svn and commit it.
7. In the main web site check that index.twig and the navbar template reference your component as "log4xxx/1.x".
8. Unindent your component in extpaths.txt.
If you want to use the CMS directly it is certainly easy to do.
Sent from my iPad
On Jun 10, 2012, at 2:18 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi all,
>
> On 2012-06-10, Ralph Goers wrote:
>
>> We really don't need to use the maven publish plugin as I've checked
>> in the each project in its own release directly and then used a
>> symlink to point the project site to the specific release. Each of
>> the other sub-sites should do the same thing.
>
> I missed most of the thread, been busy elsewhere, sorry. I'd like to
> add log4net to the site "the right way", what do I need to do?
>
> This is my understanding
>
> (1) check in the log4net site wherever I want
>
> (2) create a symlink from where I commited the site to content/log4net
>
> (3) un-indent log4net in extpath.txt
>
> Is this correct?
>
> Problems I currently see:
>
> * the log4net site is generated by Maven and has inconsistent line-ends,
> is there any better way than Ant's fixcrlf task to fix that? Our
> build already includes NAnt and Maven, I'd prefer to avoid adding a
> third build tool 8-)
>
> Mid-term log4net may be better off using the CMS directly, but that's
> something we need to discuss.
>
> * I don't know how and where to perform step (2) from above.
>
> Stefan
Re: Logging site
Posted by Christian Grobmeier <gr...@gmail.com>.
On Tue, Jun 12, 2012 at 6:19 AM, Stefan Bodewig <bo...@apache.org> wrote:
>> I'd really like to have all the sub projects added as once they are
>> all there then we can simply ask Infra to replace the existing site
>> with the new one. I've been waiting for that to do the first Log4j 2
>> release.
>
> OK, if this is holding up the release then I'll simply tar up the
> existing site and add it to svn - I can figure out a better way to do it
> later.
Nice option. Probably we should do that for log4cxx
Cheers
Christian
>
> Stefan
--
http://www.grobmeier.de
https://www.timeandbill.de
Re: Logging site
Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-06-12, Ralph Goers wrote:
> On Jun 11, 2012, at 9:19 PM, Stefan Bodewig wrote:
>> OK, if this is holding up the release then I'll simply tar up the
>> existing site and add it to svn - I can figure out a better way to do
>> it later.
> Yes, that is an option. However, I think it is important that we all
> get a feel for how this works.
The site building process in log4net is too brittle anyway, it involves
creating API docs which I currently don't manage to do at all. Fixing
that is so far down on my TODO list that it would have delayed the log4j
release for an unaceptable time.
Stefan
Re: Logging site
Posted by Ralph Goers <ra...@dslextreme.com>.
On Jun 11, 2012, at 9:19 PM, Stefan Bodewig wrote:
> On 2012-06-12, Ralph Goers wrote:
>
>> I should have added that I'd appreciate you adding log4net to the
>> site.
>
> Understood, and yes, I'll do that. It's only a matter of solving a few
> problems and finding the time to do so. Can't promise I'll be able to
> get around to it before the weekend.
>
>> I'd really like to have all the sub projects added as once they are
>> all there then we can simply ask Infra to replace the existing site
>> with the new one. I've been waiting for that to do the first Log4j 2
>> release.
>
> OK, if this is holding up the release then I'll simply tar up the
> existing site and add it to svn - I can figure out a better way to do it
> later.
Yes, that is an option. However, I think it is important that we all get a feel for how this works. That said, I almost did that for Log4j 1.2 if I hadn't been able to run mvn site on the last release tag an upload that. Since each release will exist as its own directory in the new site (hopefully deleting old releases after some time) it should be fairly simple to use whatever you want to generate the site.
Ralph
Re: Logging site
Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-06-12, Stefan Bodewig wrote:
> OK, if this is holding up the release then I'll simply tar up the
> existing site and add it to svn - I can figure out a better way to do it
> later.
Done.
The log4net site now appears on loggingtest, but there are some issues.
One is that http://logging.apache.org/log4net/ would no longer be the
canonical entry point. I plan to add a .htaccess to send people to the
1.x directory from there. Too many existing links to leave it the way
it is.
In a similar way I'll have to go through the log4net site looking for
links to other parts of logging, in particular log4j but also chainsaw,
and adapt them.
Stefan
Re: Logging site
Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-06-12, Ralph Goers wrote:
> I should have added that I'd appreciate you adding log4net to the
> site.
Understood, and yes, I'll do that. It's only a matter of solving a few
problems and finding the time to do so. Can't promise I'll be able to
get around to it before the weekend.
> I'd really like to have all the sub projects added as once they are
> all there then we can simply ask Infra to replace the existing site
> with the new one. I've been waiting for that to do the first Log4j 2
> release.
OK, if this is holding up the release then I'll simply tar up the
existing site and add it to svn - I can figure out a better way to do it
later.
Stefan
Logging site
Posted by Ralph Goers <ra...@dslextreme.com>.
I should have added that I'd appreciate you adding log4net to the site. I'd really like to have all the sub projects added as once they are all there then we can simply ask Infra to replace the existing site with the new one. I've been waiting for that to do the first Log4j 2 release.
Ralph
On Jun 10, 2012, at 2:18 AM, Stefan Bodewig wrote:
> Hi all,
>
> On 2012-06-10, Ralph Goers wrote:
>
>> We really don't need to use the maven publish plugin as I've checked
>> in the each project in its own release directly and then used a
>> symlink to point the project site to the specific release. Each of
>> the other sub-sites should do the same thing.
>
> I missed most of the thread, been busy elsewhere, sorry. I'd like to
> add log4net to the site "the right way", what do I need to do?
>
> This is my understanding
>
> (1) check in the log4net site wherever I want
>
> (2) create a symlink from where I commited the site to content/log4net
>
> (3) un-indent log4net in extpath.txt
>
> Is this correct?
>
> Problems I currently see:
>
> * the log4net site is generated by Maven and has inconsistent line-ends,
> is there any better way than Ant's fixcrlf task to fix that? Our
> build already includes NAnt and Maven, I'd prefer to avoid adding a
> third build tool 8-)
>
> Mid-term log4net may be better off using the CMS directly, but that's
> something we need to discuss.
>
> * I don't know how and where to perform step (2) from above.
>
> Stefan