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
