Thorsten Scherler wrote:
[...]
Now that the build process generates a list of available modules
with their source directories, it would be quite easy to mount
the sitemaps directly instead of copying the modules to the webapp
directory.
WDYT, should we provide this option?
I think it will simplify development since the build process
is only necessary to compile classes + patch xconf files.
For production, the copying approach should still be available.
Big +1
Do you think that a locationmap is suitable for this purpose?
What we have now is something like
<?xml version="1.0" encoding="UTF-8"?>
<modules xmlns="http://apache.org/lenya/module-list/1.0";>
<module src="/Users/nobby/apache/clean/lenya/trunk/src/modules/bxe"/>
<module src="/Users/nobby/apache/clean/lenya/trunk/src/modules/cforms"/>
<module src="/Users/nobby/apache/clean/lenya/trunk/src/modules/fckeditor"/>
...
We could easily extend this to
<?xml version="1.0" encoding="UTF-8"?>
<modules xmlns="http://apache.org/lenya/module-list/1.0";>
<module shortcut="bxe" src=".../lenya/trunk/src/modules/bxe"/>
<module shortcut="cforms" src=".../lenya/trunk/src/modules/cforms"/>
...
which would be the basis for mounting the module sitemaps.
(I chose "shortcut" because "id" is the long form which is not used
for addressing at the moment.)
Could this be transformed to a location map, or should we generate
a sitemap with mount statements?
-- 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]
