It sounds like we should:
- Define a guideline for components to layout Javadoc
- Make it easy for component to implement, how? Right now it's another
manual step in an already lengthy and error prone release process. Ugh.
Gary
On Mon, Dec 2, 2013 at 4:07 AM, Jörg Schaible
wrote:
> Hi folks,
>
My fault. Just noticed that this is wrong list. Sorry.
On Mon, Dec 2, 2013 at 8:25 PM, Edward J. Yoon wrote:
> Anyone can answer?
>
> On Tue, Nov 19, 2013 at 6:38 PM, Edward J. Yoon wrote:
>> Hi,
>>
>> I'm just curious, since 2006, ApacheCon was never held in Asia again.
>> Is there any particul
Anyone can answer?
On Tue, Nov 19, 2013 at 6:38 PM, Edward J. Yoon wrote:
> Hi,
>
> I'm just curious, since 2006, ApacheCon was never held in Asia again.
> Is there any particular reason? Anybody can hold a conference?
>
> Thanks.
>
> --
> Best Regards, Edward J. Yoon
> @eddieyoon
--
Best Reg
Hi folks,
it seems we have currently a great diversity with the provided javadocs of
our components. Some provide the latest one from trunk only, some provide
also a link the the latest one released and some have links to the
individual releases. However, after updating some links in our Maven
