Jörn Nettingsmeier wrote:
one thing i don't understand:
currently we have the long name as used in the "id" field, which is also
used for copying the module java code into the build directory (which is
questionable imho - why not create a folder hierarchy and put the
classes there? in build, we don't need to separate the modules from each
other, and getting the classes would become a lot more efficient if they
share a common tree).
IMO it makes sense to compile each module in a separate directory,
because this allows to generate separate JAR files.
and there is also the short name, used for the source directory and for
calling the module via lenya://modules/<shortname>/... how is the
mapping done?
ATM this is just the name of the directory the module resides in.
IMO it should be allowed to use shortcuts to reference modules
to keep the code simple, but the build process should check for
collisions.
This could be solved by a module declaration file, which would be
quite useful anyway to exclude/include single modules from the
build process:
<modules>
<module id="org.apache.lenya.modules.sitetree" shortcut="sitetree"/>
<module id="com.myproject.sitetree" shortcut="my-sitetree"/>
<!-- currently not used
<module id="..."/>
-->
...
</modules>
WDYT?
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
