Re: simplifying the wyona directory structure

Gregor J. Rothfuss wrote:

>here are some thoughts on the wyona directory structure,
>work in progress.
>
>we currently do have libraries under /libs and under
>/src/webapp/WEB-INF where shall they go?
>

within src/webapp/WEB-INF/lib/ are libraries which are patching Cocoon

within libs/  are libraries which are necessary for Wyona

I think it's good to have them separated, because you see better the 
dependencies,
but you're right the directory structure is not very straight forward

>
>same for docs. they are under /webapp/wyona/cms/docs and
>

these are XML and XSP needed by all publications, for instance 
authentication screen

>/webapp/wyona/cms/pubs/wyona-cms-docs/
>

That's documentation and therefore a publication

>
>the wyona menu is in the eth pub when it should go somewhere
>centrally, we need to make a system-wide css and image matcher
>(started in the root sitemap)
>

+1: webapp/wyona/cms/docs  resp. resources, resp. stylesheets

>
>the way how subsitemaps override features of the root sitemap
>has to be rethought, and made consistent. we are not sure if
>cocoon has all the power we want to factor out common functionality
>(menu, bitfluxeditor, scheduling, publishing, revision control etc)
>into the root sitemap, and make the publication sitemaps much simpler
>(and more consistent)
>

+1

>
>the directory structure inside a publication needs to be refined.
>we currently do not have a consistent place to put .xsp, neither
>do we have a /bin for publication-specific shell scripts
>

+1

>
>the goal is to make publications self-contained so that we can
>manage cvs better, and give our clients cvs access to their publication,
>but not the whole source tree. this requires a way to store the
>publication-specific classes inside the publication (/java maybe?) yet
>still be able to deal with the CLASSPATH in a sane way.
>

+1

>
>there are probably many hidden dependencies between various publications
>(they grew organically ..) so it would make sense to test them by
>removing other publications. 
>

+1

>
>in that vein, some of the older publications probably do not support all
>our new core features, and should either be updated to reflect the new
>functionality, or be dropped.
>

+1

>
>hm, after some discussions these items better go to the bugtracker i
>guess :)
>

+1

Thanks


Michael

>
>-gregor
>
>--
>Gregor J. Rothfuss   [email protected]  +41 1 272 9161
>Software Architect   Wyona AG, Hardstrasse 219, CH-8005 Zurich
>Open Source CMS      http://www.wyona.org http://www.wyona.com
>
>
>_______________________________________________
>WyonaCMS-dev mailing list
>[email protected]
>http://mail.wyona.org/cgi-bin/mailman/listinfo/wyonacms-dev
>  
>