You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2006/06/22 00:27:49 UTC
[1.4] Modules are built separately
Hi Lenya devs,
I updated the build process slightly, now modules are not compiled
together but separately.
The process is as follows:
- an Ant task generates a list of available modules
- the modules are ordered by dependency
- each module is compiled and a JAR file is generated
- when a module is compiled, only the modules it depends on are
added to the classpath
To have your modules compiled, you have to add a module
descriptor file:
<yourmodule>/module.xml
Here is an example:
<module xmlns="http://apache.org/lenya/module/1.0">
<id>org.apache.lenya.modules.jackrabbit</id>
<depends module="org.apache.lenya.modules.repository"/>
<depends module="org.apache.lenya.modules.jcr"/>
<package>org.apache.lenya.modules</package>
<version>0.1-dev</version>
<name>Jackrabbit Repository Module</name>
<lenya-version>@lenya.version@</lenya-version>
<description>Jackrabbit JCR Implementation (see org.apache.lenya.modules.jcr
Module)</description>
</module>
Versions are not considered yet by the build process, this might be
added in the future.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: trunk does not compile [ was: [1.4] Modules are built separately
]
Posted by Andreas Hartmann <an...@apache.org>.
Doug Chestnut wrote:
> Hi Jörn,
> Give the build a try now. A fresh checkout allowed me to build w/o errors.
Thanks a lot for the fix!
I guess I forgot a "build clean" before committing :/
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: trunk does not compile [ was: [1.4] Modules are built separately
]
Posted by Doug Chestnut <dh...@virginia.edu>.
Hi Jörn,
Give the build a try now. A fresh checkout allowed me to build w/o errors.
--Doug
Jörn Nettingsmeier wrote:
> it looks like the trunk got broken during this change:
>
> after a fresh checkout and rebuilding the compile-build-target classes
> (see other thread), i get this:
>
>
> compile-module-org.apache.lenya.modules.webdav:
> Created dir:
> /build/lenya/build/lenya/modules/org.apache.lenya.modules.webdav
> Compiling 5 source files to
> /build/lenya/build/lenya/modules/org.apache.lenya.modules.webdav
> /build/lenya/src/modules/webdav/java/src/org/apache/lenya/cms/usecases/webdav/FilePropfind.java:32:
> package org.apache.lenya.cms.site.usecases does not exist
> import org.apache.lenya.cms.site.usecases.SiteUsecase;
> ^
>
> and 70 more...
>
> BUILD FAILED
> /build/lenya/src/targets/webapp-build.xml:163: The following error
> occurred while executing this line:
> /build/lenya/src/targets/modules-build.xml:47: The following error
> occurred while executing this line:
> /build/lenya/build/lenya/temp/modules-build.xml:34: The following error
> occurred while executing this line:
> /build/lenya/build/lenya/temp/modules-build.xml:788: Compile failed; see
> the compiler error output for details.
>
> Total time: 52 seconds
>
> here's a search for the missing class on my system after the
> half-finished build:
>
> nettings@kleineronkel:/build/lenya> find -name SiteUsecase*
> ./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/props/SiteUsecase.java.svn-work
>
> ./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/text-base/SiteUsecase.java.svn-base
>
> ./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/prop-base/SiteUsecase.java.svn-base
>
> ./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/wcprops/SiteUsecase.java.svn-work
>
> ./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/SiteUsecase.java
>
> ./build/lenya/java/modules/org/apache/lenya/cms/site/usecases/SiteUsecase.java
>
> ./build/lenya/modules/org.apache.lenya.modules.sitemanagement/org/apache/lenya/cms/site/usecases/SiteUsecase.class
>
>
>
> this is probably a one-liner for andreas, but i'm a little out of my
> depth here...
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
trunk does not compile [ was: [1.4] Modules are built separately
]
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
it looks like the trunk got broken during this change:
after a fresh checkout and rebuilding the compile-build-target classes
(see other thread), i get this:
compile-module-org.apache.lenya.modules.webdav:
Created dir:
/build/lenya/build/lenya/modules/org.apache.lenya.modules.webdav
Compiling 5 source files to
/build/lenya/build/lenya/modules/org.apache.lenya.modules.webdav
/build/lenya/src/modules/webdav/java/src/org/apache/lenya/cms/usecases/webdav/FilePropfind.java:32:
package org.apache.lenya.cms.site.usecases does not exist
import org.apache.lenya.cms.site.usecases.SiteUsecase;
^
and 70 more...
BUILD FAILED
/build/lenya/src/targets/webapp-build.xml:163: The following error
occurred while executing this line:
/build/lenya/src/targets/modules-build.xml:47: The following error
occurred while executing this line:
/build/lenya/build/lenya/temp/modules-build.xml:34: The following error
occurred while executing this line:
/build/lenya/build/lenya/temp/modules-build.xml:788: Compile failed; see
the compiler error output for details.
Total time: 52 seconds
here's a search for the missing class on my system after the
half-finished build:
nettings@kleineronkel:/build/lenya> find -name SiteUsecase*
./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/props/SiteUsecase.java.svn-work
./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/text-base/SiteUsecase.java.svn-base
./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/prop-base/SiteUsecase.java.svn-base
./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/.svn/wcprops/SiteUsecase.java.svn-work
./src/modules-core/sitemanagement/java/src/org/apache/lenya/cms/site/usecases/SiteUsecase.java
./build/lenya/java/modules/org/apache/lenya/cms/site/usecases/SiteUsecase.java
./build/lenya/modules/org.apache.lenya.modules.sitemanagement/org/apache/lenya/cms/site/usecases/SiteUsecase.class
this is probably a one-liner for andreas, but i'm a little out of my
depth here...
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Jörn Nettingsmeier wrote:
>> Andreas Hartmann wrote:
>>> To have your modules compiled, you have to add a module
>>> descriptor file:
>>>
>>> <yourmodule>/module.xml
>>
>> i'm not really sure about this myself, but have you considered
>> <yourmodule>/config/module.xml instead?
>
> Well, IMO it's rather a descriptor than a configuration file.
> I think it should be as prominent as possible, thus the location
> should be the module root directory.
agreed.
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Andreas Hartmann <an...@apache.org>.
Jörn Nettingsmeier wrote:
> Andreas Hartmann wrote:
>> To have your modules compiled, you have to add a module
>> descriptor file:
>>
>> <yourmodule>/module.xml
>
> i'm not really sure about this myself, but have you considered
> <yourmodule>/config/module.xml instead?
Well, IMO it's rather a descriptor than a configuration file.
I think it should be as prominent as possible, thus the location
should be the module root directory.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> To have your modules compiled, you have to add a module
> descriptor file:
>
> <yourmodule>/module.xml
i'm not really sure about this myself, but have you considered
<yourmodule>/config/module.xml instead?
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Jörn Nettingsmeier wrote:
>> Andreas Hartmann wrote:
>
> [...]
>
>>> <module xmlns="http://apache.org/lenya/module/1.0">
>>> <id>org.apache.lenya.modules.jackrabbit</id>
>>> <depends module="org.apache.lenya.modules.repository"/>
>>> <depends module="org.apache.lenya.modules.jcr"/>
>>> <package>org.apache.lenya.modules</package>
>>> <version>0.1-dev</version>
>>> <name>Jackrabbit Repository Module</name>
>>> <lenya-version>@lenya.version@</lenya-version>
>>> <description>Jackrabbit JCR Implementation (see
>>> org.apache.lenya.modules.jcr Module)</description>
>>> </module>
>>>
>>>
>>> Versions are not considered yet by the build process, this might be
>>> added in the future.
>>
>> nice. we need a way to handle name clashes though. how about prefixing
>> modules with either "core-", "optional-" or "custom-", where custom is
>> always site-specific?
>
> We could add this to the module ID:
>
> <id>org.apache.lenya.modules.core.workflow-api</id>
ah, of course it belongs there. i had mistakenly thought that this was a
java classpath. (reading email too fast.)
>> core modules would be maintained and thoroughly tested all the time by
>> every lenya developer (i.e. must not be broken at any time, unless major
>> refactoring is under way, and then they must be fixed asap), optional
>> modules included in the tree but maintained by single people and thus
>> may be broken sometimes or remain in a proof-of-concept stage for a
>> while, and custom modules are out-of-tree modules created by users for
>> their own deployments.
>
> A general question:
> Can we enforce such guidelines in our community?
> If yes, should we add this to the project guidelines?
i would appreciate that.
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Andreas Hartmann <an...@apache.org>.
Jörn Nettingsmeier wrote:
> Andreas Hartmann wrote:
>> <module xmlns="http://apache.org/lenya/module/1.0">
>> <id>org.apache.lenya.modules.jackrabbit</id>
>> <depends module="org.apache.lenya.modules.repository"/>
>> <depends module="org.apache.lenya.modules.jcr"/>
>> <package>org.apache.lenya.modules</package>
>> <version>0.1-dev</version>
>> <name>Jackrabbit Repository Module</name>
>> <lenya-version>@lenya.version@</lenya-version>
>> <description>Jackrabbit JCR Implementation (see
>> org.apache.lenya.modules.jcr Module)</description>
>> </module>
>
> how about adding a maintainer field with a name and email address for
> optional, user-contributed modules?
> that way, lenya committers will know who to contact if a module gets
> broken due to core changes, or is suffering from bit-rot.
Fine with me for non-core modules, if the field is optional since we
have code collective ownership.
> it might even make sense for core modules. in theory, the maintenance
> burden of those should be divided among the entire committer community,
> but it's certainly nice to be able to find out who has the best insight
> and the "grand architectural vision" concerning a particular module.
I see the danger that people rely on a particular person to fix a bug.
That's why I'm rather -1 for explicit code ownership.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> <module xmlns="http://apache.org/lenya/module/1.0">
> <id>org.apache.lenya.modules.jackrabbit</id>
> <depends module="org.apache.lenya.modules.repository"/>
> <depends module="org.apache.lenya.modules.jcr"/>
> <package>org.apache.lenya.modules</package>
> <version>0.1-dev</version>
> <name>Jackrabbit Repository Module</name>
> <lenya-version>@lenya.version@</lenya-version>
> <description>Jackrabbit JCR Implementation (see
> org.apache.lenya.modules.jcr Module)</description>
> </module>
how about adding a maintainer field with a name and email address for
optional, user-contributed modules?
that way, lenya committers will know who to contact if a module gets
broken due to core changes, or is suffering from bit-rot.
it might even make sense for core modules. in theory, the maintenance
burden of those should be divided among the entire committer community,
but it's certainly nice to be able to find out who has the best insight
and the "grand architectural vision" concerning a particular module.
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Andreas Hartmann <an...@apache.org>.
Jörn Nettingsmeier wrote:
> Andreas Hartmann wrote:
[...]
>> <module xmlns="http://apache.org/lenya/module/1.0">
>> <id>org.apache.lenya.modules.jackrabbit</id>
>> <depends module="org.apache.lenya.modules.repository"/>
>> <depends module="org.apache.lenya.modules.jcr"/>
>> <package>org.apache.lenya.modules</package>
>> <version>0.1-dev</version>
>> <name>Jackrabbit Repository Module</name>
>> <lenya-version>@lenya.version@</lenya-version>
>> <description>Jackrabbit JCR Implementation (see
>> org.apache.lenya.modules.jcr Module)</description>
>> </module>
>>
>>
>> Versions are not considered yet by the build process, this might be
>> added in the future.
>
> nice. we need a way to handle name clashes though. how about prefixing
> modules with either "core-", "optional-" or "custom-", where custom is
> always site-specific?
We could add this to the module ID:
<id>org.apache.lenya.modules.core.workflow-api</id>
> core modules would be maintained and thoroughly tested all the time by
> every lenya developer (i.e. must not be broken at any time, unless major
> refactoring is under way, and then they must be fixed asap), optional
> modules included in the tree but maintained by single people and thus
> may be broken sometimes or remain in a proof-of-concept stage for a
> while, and custom modules are out-of-tree modules created by users for
> their own deployments.
A general question:
Can we enforce such guidelines in our community?
If yes, should we add this to the project guidelines?
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Hi Lenya devs,
>
> I updated the build process slightly, now modules are not compiled
> together but separately.
>
> The process is as follows:
>
> - an Ant task generates a list of available modules
> - the modules are ordered by dependency
> - each module is compiled and a JAR file is generated
> - when a module is compiled, only the modules it depends on are
> added to the classpath
>
>
> To have your modules compiled, you have to add a module
> descriptor file:
>
> <yourmodule>/module.xml
>
> Here is an example:
>
> <module xmlns="http://apache.org/lenya/module/1.0">
> <id>org.apache.lenya.modules.jackrabbit</id>
> <depends module="org.apache.lenya.modules.repository"/>
> <depends module="org.apache.lenya.modules.jcr"/>
> <package>org.apache.lenya.modules</package>
> <version>0.1-dev</version>
> <name>Jackrabbit Repository Module</name>
> <lenya-version>@lenya.version@</lenya-version>
> <description>Jackrabbit JCR Implementation (see
> org.apache.lenya.modules.jcr Module)</description>
> </module>
>
>
> Versions are not considered yet by the build process, this might be
> added in the future.
nice. we need a way to handle name clashes though. how about prefixing
modules with either "core-", "optional-" or "custom-", where custom is
always site-specific?
core modules would be maintained and thoroughly tested all the time by
every lenya developer (i.e. must not be broken at any time, unless major
refactoring is under way, and then they must be fixed asap), optional
modules included in the tree but maintained by single people and thus
may be broken sometimes or remain in a proof-of-concept stage for a
while, and custom modules are out-of-tree modules created by users for
their own deployments.
wdyt?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann wrote:
> Hi Lenya devs,
>
> I updated the build process slightly, now modules are not compiled
> together but separately.
>
> The process is as follows:
>
> - an Ant task generates a list of available modules
> - the modules are ordered by dependency
BTW, this is now handled using Ant target dependencies.
-- Andreas
> - each module is compiled and a JAR file is generated
> - when a module is compiled, only the modules it depends on are
> added to the classpath
>
>
> To have your modules compiled, you have to add a module
> descriptor file:
>
> <yourmodule>/module.xml
>
> Here is an example:
>
> <module xmlns="http://apache.org/lenya/module/1.0">
> <id>org.apache.lenya.modules.jackrabbit</id>
> <depends module="org.apache.lenya.modules.repository"/>
> <depends module="org.apache.lenya.modules.jcr"/>
> <package>org.apache.lenya.modules</package>
> <version>0.1-dev</version>
> <name>Jackrabbit Repository Module</name>
> <lenya-version>@lenya.version@</lenya-version>
> <description>Jackrabbit JCR Implementation (see
> org.apache.lenya.modules.jcr Module)</description>
> </module>
>
>
> Versions are not considered yet by the build process, this might be
> added in the future.
>
> -- Andreas
>
>
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Jörn Nettingsmeier wrote:
>> looks like there is still a problem with publication-specific modules:
>>
> Strange - I just did a clean build and it works for me.
>
> Is there something interesting in the logs?
sorry, false alarm. obviously, i introduced the bug with my
deny-by-default patch. my hacked UsecaseAuthorizer threw an NPE, and it
looked like it was in the homepage module, because that's what i saw at
the top of the trace...
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Andreas Hartmann <an...@apache.org>.
Jörn Nettingsmeier wrote:
> looks like there is still a problem with publication-specific modules:
>
> http://localhost:8888/default/authoring/index.html
>
> Unable to get transformer handler for
> cocoon://lenya-page/default/authoring/index.xml?doctype=homepage at
> <map:serialize type="xhtml"> -
> file:/srv/lenya/build/lenya/webapp/lenya/pubs/default/sitemap.xmap:256:50
> at <map:transform> -
> file:/srv/lenya/build/lenya/webapp/lenya/pubs/default/sitemap.xmap:236:91
> at <map:transform> -
> file:/srv/lenya/build/lenya/webapp/lenya/pubs/default/sitemap.xmap:229:164
> at <map:generate> -
>
> the index.html page in the default pub has the doctype "homepage", which
> is implemented as a publication-local module.
>
> this needs to be fixed, because the default pub is totally broken atm.
Strange - I just did a clean build and it works for me.
Is there something interesting in the logs?
> the question is whether we should rather get rid of publication-specific
> modules... but otoh, for trivial things like the homepage doctype, it
> might actually be justified.
Actually it shouldn't make a difference - all modules are handled in
the same way, only the path in local.build.properties counts.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] Modules are built separately
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
looks like there is still a problem with publication-specific modules:
http://localhost:8888/default/authoring/index.html
Unable to get transformer handler for
cocoon://lenya-page/default/authoring/index.xml?doctype=homepage at
<map:serialize type="xhtml"> -
file:/srv/lenya/build/lenya/webapp/lenya/pubs/default/sitemap.xmap:256:50
at <map:transform> -
file:/srv/lenya/build/lenya/webapp/lenya/pubs/default/sitemap.xmap:236:91
at <map:transform> -
file:/srv/lenya/build/lenya/webapp/lenya/pubs/default/sitemap.xmap:229:164
at <map:generate> -
the index.html page in the default pub has the doctype "homepage", which
is implemented as a publication-local module.
this needs to be fixed, because the default pub is totally broken atm.
the question is whether we should rather get rid of publication-specific
modules... but otoh, for trivial things like the homepage doctype, it
might actually be justified.
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: pol-admin@uni-due.de, Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org