well that's what I do - I store the files in cvs, check them out copy
to bootstrap/config deploy and all is there. but thats only one way.
when I finish work in the evening and I (or some hard-working
teammate) created 17 new templates I would like to have the ant task
to get the new config xml docs and throw them in my cvs synced
directory so I can commit my changes. same could (hypothetically) be
done with content. hence I need a way to trigger and store the xml
output in a backend manner.
I'll give sameers hint a shot tomorrow.
On Feb 8, 2006, at 15:43, Thomas Ferris Nicolaisen wrote:
If you are not working on an instance with existing content (which
you really don't have to when developing design), you can make an
ant-script that copies your own bootstrap xml files into magnolia.
As far as I know, there isn't any difference between bootstrap xml
files and files exported from magnolia. Don't know why I didn't
think of that earlier..
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
