On Mar 28, 2013, at 5:58 PM, Ralph Goers wrote:
>
> On Mar 28, 2013, at 7:53 AM, Gary Gregory wrote:
>
>> On Sun, Mar 24, 2013 at 4:08 AM, Nick Williams <
>> [email protected]> wrote:
>>
>>> I've been a Log4j 1 user for years and I love it. I'm currently writing a
>>> book for Java EE 7 + Spring Framework 4 development and one of my chapters
>>> is on application logging. I was going to cover Log4j 1 and then I stumbled
>>> upon Log4j 2. It looks like a serious improvement over Log4j 1 and I'm
>>> quite excited about it. There are three important things that I couldn't
>>> find on the site (I read the entire manual, and looked at what I thought
>>> were all of the pages, but it's possible I've missing something). I'm
>>> hoping someone here can sort it out for me:
>>>
>>> 1) How stable is the API at this point? I understand the hazards of beta
>>> software, but are we talking "it could be drastically different in six
>>> months" or "chances are it won't change much from here on out?" I don't
>>> expect a precise answer, just some guidance.
>>>
>>> 2) What is the /projected/ GA date? I know that dates are never certain
>>> with open source software, and I don't expect somebody to tell me that
>>> it'll be GA on July 21, 2013. But are we talking weeks, months, or upwards
>>> of a year? If my book goes to press in November of this year, do I risk
>>> that Log4j 2 isn't out by that time if I include it?
>>>
>>> 3) Where is the darned JavaDoc API documentation? I'm quite used to how
>>> easy it is to find in the Commons, on the Tomcat site, and on the Log4j 1
>>> site (there's a big link that says "JavaDoc" in the sidebar). But I was
>>> rather flabbergasted by the fact that I couldn't find any on the Log4j 2
>>> site. Specifically, I'm looking for the JavaDoc pages for the API, the
>>> Implementation, and the Commons Logging Bridge.
>>>
>>
>> I have to agree that we or Maven has shot ourselves in the foot with the
>> Javadoc. How am I supposed to know that I have to dig in a component, then
>> go under Project Reports to find the Javadoc. This is lame. As nick
>> mentions there should at LEAST be a link on the main page of at LEAST the
>> API Javadoc.
>>
>
> I'm not going to disagree. I have no problem with you fixing it ;-)
>
> Ralph
Should be pretty easy to fix. Just open /trunk/src/site/site.xml and within
<menu name="Manual"...></menu> (I'd recommend between <item name="Log4j 1.x
Migration".../> and <item name="API"...></item>) add this:
<item name="Javadoc" href="??what to put here??" collapse="true">
<item name="API" href="/log4j-api/apidocs/index.html"/>
<item name="Implementation" href="/log4j-core/apidocs/index.html"/>
...
<item name="Log4j Tag Library" href="/log4j-taglib/apidocs/index.html"/>
</item>
N
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
