Apparently the clean way to do this is to write a custom module that
contains all your customizations. All you need to do then is to toss
one jar into WEB-INF/lib of a plain vanilla Magnolia instance and
start it up. I've not done it myself yet, but have tested the
bootstrapping of such custom modules recently.
AFAIK the documentation on this is a bit slim yet though, especially
since the module stuff has changed a bit in 3.5, right? So if you
figure it out, it would be great if you could write a short tutorial
and place it here:
http://www.magnolia.info/wiki/Wiki.jsp?page=Magnolia3.1
(which should be Magnolia3.5 btw)
Cheers,
Will
On 08.01.2008, at 11:41, Allan, CJ (Chris) wrote:
Hi,
We are using magnolia Enterprise 3.52. I have made a number of
customisations to magnolia, including new paragraphs, modified
paragraphs (jsps, and dialogs), including additional js and css files
and references to these in the siteDesigner head.jsp file.
When trying to set up a new instance of magnolia with all these
changes
included, it is a big hassle trying to remember everything that has
been
changed/added. Is there a convenient way of packaging up all (or most)
of these changes, so that a vanilla magnolia instance can be quickly
changed to our modified instance? (I am fine with altering how we have
done things as well e.g. I don't mind whether our references to cs and
js files are in the head.jsp are somewhere else etc)
Cheers for all help and suggestions!
Chris
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
