Re: Module packages and javadocs

Andreas Hartmann schrieb:
> Hi Lenya devs,
> 
> ATM we build the javadocs for all modules separately.
This wouldn't be 
> necessary if all modules used a package convention,
e.g.

OTOH, maybe it's better to keep the javadocs separate
anyway. The major 
reason that I raised this question was that maintaining an
API link for 
each module on the website is cumbersome. But maybe we can
generate a 
page with links automatically.

Apart from that, I still think that the convention makes
sense, since it 
simplifies finding the location of a class or interface.

-- Andreas


> 
>   API:  org.apache.lenya.modules.foo
>         org.apache.lenya.modules.foo.util
>         org.apache.lenya.modules.foo.xyz
> 
>   Impl: org.apache.lenya.modules.foo.impl
>         org.apache.lenya.modules.foo.util.impl
>         org.apache.lenya.modules.foo.xyz.impl
> 
> I guess we'd have to postpone this to the next major
release, though, 
> because it would break backwards compatibility.
> 
> WDYT?
> 
> -- Andreas
> 
> 


-- 
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org