On 2017-04-19, Dominik Psenner wrote:
> I completely purged that mess from my memory. We need a solution that
> just works and links to generated code are not "the solution"©. :-)
> When I build log4net I get the following files:
> * log4net.dll
> * log4net.pdb
> * log4net.xml
> The latter is a
Hallo Thorsten
On 2017-04-19, Thorsten Schöning wrote:
> am Mittwoch, 19. April 2017 um 10:13 schrieben Sie:
>> As log4net uses maven to build the site as well, this could probably
>> solved by using the same skin (I've never tried to fiddle with that,
>> though).
> As log4cxx has done the same
Regarding the consistency with other log4 projects, I as a .NET
developer and log4net user, consider consistency with other .NET
documentation (aka MSDN-Style) much more important then with let's say
log4j.
I don't think either that we should re-style the SDK reference. The
issue we try to so
Dominik Psenner wrote on 19.04.2017 10:40:17:
>
> I completely purged that mess from my memory. We need a solution that
> just works and links to generated code are not "the solution"©. :-) When
> I build log4net I get the following files:
>
> * log4net.dll
> * log4net.pdb
> * log4net.xml
>
Guten Tag Stefan Bodewig,
am Mittwoch, 19. April 2017 um 10:13 schrieben Sie:
> As log4net uses maven to build the site as well, this could probably
> solved by using the same skin (I've never tried to fiddle with that,
> though).
As log4cxx has done the same by simply copying over templates and
On 2017-04-19 10:13, Stefan Bodewig wrote:
On 2017-04-19, Dominik Psenner wrote:
From a higher perspective I would also like to see all logging
subprojects to have one website style. Looking at the website of
log4net and log4j those projects appear to be unrelated, whereas the
log4cxx and log4
I completely purged that mess from my memory. We need a solution that
just works and links to generated code are not "the solution"©. :-) When
I build log4net I get the following files:
* log4net.dll
* log4net.pdb
* log4net.xml
The latter is a parseable output of all the classes, methods,
pro
On 2017-04-19, Dominik Psenner wrote:
> From a higher perspective I would also like to see all logging
> subprojects to have one website style. Looking at the website of
> log4net and log4j those projects appear to be unrelated, whereas the
> log4cxx and log4j websites are more alike. Any ideas ho
On 2017-04-18, Dominik Psenner wrote:
> We probably should at least add a remark that points readers to the
> SDK reference and avoid the double effort of maintaining the
> documentation on the website too.
Likely, in particular since we've broken it twice during the 2.0.x
release series. Looks a
I like the idea to generate parts of the website with stuff that comes
from the source code. However I can't see how the different sources
could all be assembled together. The sdk reference is already generated
from source, however that is already one step to far because we won't
get the styles
Asciidoc is much nicer than anything one can do in javadoc.
Sent from my iPhone
> On Apr 19, 2017, at 10:10, Gary Gregory wrote:
>
> Maybe from package level Javadocs?
>
> Gary
>
>> On Apr 18, 2017 5:56 PM, "Remko Popma" wrote:
>>
>> Asciidoc can include code snippets or whole files:
>> ht
Maybe from package level Javadocs?
Gary
On Apr 18, 2017 5:56 PM, "Remko Popma" wrote:
> Asciidoc can include code snippets or whole files:
> http://asciidoctor.org/docs/user-manual/#include-partial
>
> I'm not convinced that it's desirable to generate the user manual from
> javadoc though. They
Asciidoc can include code snippets or whole files:
http://asciidoctor.org/docs/user-manual/#include-partial
I'm not convinced that it's desirable to generate the user manual from javadoc
though. They usually target different audiences so the content is different.
Sent from my iPhone
> On Apr
When I worked on my Hibernate book, we had a system that would extract text
out of source files into the xhtml book source. All of the examples in the
book come from real code that gets compiled and tested before the book is
built. So it is all doable.
Gary
On Apr 18, 2017 4:37 PM, "Matt Sicker"
We have a similar issue in Log4j right now where documentation is mainly
maintained in the manual pages, but there are javadocs as well. Ideally,
I'd like to be able to generate the manual pages from the javadocs, but I
haven't really looked into how to do that yet. I've seen such a pattern
used wi
Hi,
We probably should at least add a remark that points readers to the SDK
reference and avoid the double effort of maintaining the documentation
on the website too.
Cheers,
Dominik
On 2017-04-18 17:09, Stefan Bodewig wrote:
Hi John
On 2017-04-18, John V wrote:
Please forward this if y
Hi John
On 2017-04-18, John V wrote:
> Please forward this if you are not the appropriate recipient.
Many thanks!
> I was browsing the documentation on the Log4Net website for a list of
> all of the formatting flags for the PatternLayout, but could not find
> one. I did discover some dead link
Please forward this if you are not the appropriate recipient.
I was browsing the documentation on the Log4Net website for a list of all of
the formatting flags for the PatternLayout, but could not find one. I did
discover some dead links on the manual's introduction page at
http://logging.apa
18 matches
Mail list logo
