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/23 10:32:38 UTC
[1.4] [RT] Don't copy modules?
Hi Lenya devs,
I guess Thorsten will like the idea:
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.
-- 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] [RT] Don't copy modules?
Posted by Andreas Hartmann <an...@apache.org>.
Jörn Nettingsmeier wrote:
> Andreas Hartmann wrote:
>> Hi Lenya devs,
>>
>> I guess Thorsten will like the idea:
>>
>> 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.
>
> i like it. but since it's not exactly consistent (core code is still
> copied),
I hope the core will be split up into modules.
> it should be off-by-default and documented prominently.
That's fine with me.
> can this approach be extended to publications?
I hope so, IIRC this was already requested a long time ago.
-- 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] [RT] Don't copy modules?
Posted by Jörn Nettingsmeier <po...@uni-duisburg.de>.
Andreas Hartmann wrote:
> Hi Lenya devs,
>
> I guess Thorsten will like the idea:
>
> 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.
i like it. but since it's not exactly consistent (core code is still
copied), it should be off-by-default and documented prominently.
can this approach be extended to publications? right now, when i work on
pubs, the content is already being read from the "source" publication
directory thanks to redirection, but e.g. the sitemaps are not, which is
a nuisance, since after tweaking them in the live tree you need to
remember to copy the changes back to the publication source dir.
--
"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] [RT] Don't copy modules?
Posted by Thorsten Scherler <th...@wyona.com>.
El vie, 23-06-2006 a las 11:44 +0200, Andreas Hartmann escribió:
> 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?
I am not sure whether the location map does bring more value to this
specific issue.
The location map is an easy way to have multiple location configured as
fallback on the one hand and on the other hand the location map makes it
easy to change the location on a publication base.
I will look into extend 1.4. that we can use the location map. I reckon
we can reuse lot of code from forrest ant targets to activate the
location map in lenya core and publications.
...but yeah we can transform this above list to something like:
<match pattern="module.shortcut.**">
<location
src="/Users/nobby/apache/clean/lenya/trunk/src/modules/{1}" />
</match>
and one can access it like:
lm://module.shortcut.bxe/sitemap.xmap
That has the benefit that one can access *all* files in the module
directly. Like
lm://module.shortcut.opendocument/xslt/opendocument2xhtml.xsl.
That may as well solve the resource-module problem.
salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] [RT] Don't copy modules?
Posted by Andreas Hartmann <an...@apache.org>.
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
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] [RT] Don't copy modules?
Posted by Thorsten Scherler <th...@apache.org>.
El vie, 23-06-2006 a las 10:32 +0200, Andreas Hartmann escribió:
> Hi Lenya devs,
>
> I guess Thorsten will like the idea:
:)
I love it!
>
> 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
Regarding the concerns of Jörn, I think step by step lenya is becoming
copyless. See the external content dir, now modules, ...
The biggest (!!!) advantage of copyless is that development time of new
components that are not java based will be cut down significant since we
have a change/refresh cycle and not a change/build/refresh.
Thanks Andreas, that is awesome news.
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: [1.4] [RT] Don't copy modules?
Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann wrote:
> Andreas Hartmann wrote:
>> Hi Lenya devs,
>>
>> I guess Thorsten will like the idea:
>>
>> 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.
>
> The problem is that this doesn't work with fallback out of the box.
> Any ideas how to solve this in a simple way?
I've added the option if modules should be copied.
You can set it in local.build.properties.
The (Template)FallbackSourceFactory had to be modified, maybe
we can find a more orthogonal way to handle this 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] [RT] Don't copy modules?
Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann wrote:
> Hi Lenya devs,
>
> I guess Thorsten will like the idea:
>
> 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.
The problem is that this doesn't work with fallback out of the box.
Any ideas how to solve this in a simple way?
-- 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