Andreas Hartmann wrote:
Michael Wechner schrieb:
Andreas Hartmann wrote:
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.
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
what about custom packages? I guess you still would have to build
them separately?
What do you mean with "custom packages"?
e.g. com.microsoft.lenya.modules.foo
IMO the convention makes sense independently from the javadocs. For
instance, you can tell from the declaration of a sitemap component
which module it belongs to.
can you give an example?
I guess we'd have to postpone this to the next major release,
though, because it would break backwards compatibility.
break backwards compatibility just because of javadocs?
Like I said, the change doesn't make sense in the stable branch.
I understood that, but I am not sure if it makes sense for a further
release in the future
Cheers
Michael
-- Andreas
--
Michael Wechner
Wyona - Open Source Content Management - Yanel, Yulup
http://www.wyona.com
[EMAIL PROTECTED], [EMAIL PROTECTED]
+41 44 272 91 61
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
