List Info

Thread: Don't copy modules?




Don't copy modules?
user name
2006-06-23 08:40:58
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-adminuni-due.de, Telefon: 0203/379-2736

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

Don't copy modules?
user name
2006-06-23 08:43:41
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.hartmannwyona.com                     andreasapache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )