On Thu, Dec 1, 2011 at 4:54 AM, Senaka Fernando <[email protected]> wrote:

> Hi Azeez,
>
> This was fixed for 3.x.y, and has been reintroduced with the Maven3
> migration on the trunk.


Can you please provide some pointers as to what the fix was? Then we can
fix this on trunk.


> IsuruW, can you check into fixing this issue as well? I believe that you
> might need to check into the way in which the documentation stuff has been
> defined in carbon root poms and also on how its being inherited into the
> registry bundles.
>
> Thanks,
> Senaka.
>
>
> On Wed, Nov 30, 2011 at 3:19 PM, Afkham Azeez <[email protected]> wrote:
>
>> This has been reported some time back and is still not fixed. I'm
>> planning to remove the Javadoc generation & committing the POM file!
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * <http://www.apache.org/>**
>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Senaka Fernando*
> Product Manager - WSO2 Governance Registry;
> Associate Technical Lead; WSO2 Inc.; http://wso2.com*
> Member; Apache Software Foundation; http://apache.org
>
> E-mail: senaka AT wso2.com
> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
> Linked-In: http://linkedin.com/in/senakafernando
>
> *
> Lean . Enterprise . Middleware
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to