#: (Jean-Sebastien Bournival) changed the world a bit at a time by saying on
12/1/2005 7:20 PM :#
Hi, I'm new to Magnolia, and we are starting our first project using it. I
am trying to set up a development environment that is clean and functional.
I was wondering: how does many developers manages to update a common
repository with all their changes?
- I cannot set every workstation to point to the same repositories since
it's locked (.lock file) by the first one that boots its Tomcat.
- Also I do not want the developers to build something locally (template,
dialog and paragraph), and then repeating it on a possible integration
environment.
If anyone have a configuration that suits multiple developers, it would be
nice of you to share it.
Thanx!
JS.
I have been passing through this process of thinking some time ago; and currently the solution I am
using is quite simple. I will give here my working mode and some of the reasons:
- exporting every changes to XML
- these are versioned (through SVN or CVS)
This is the only way I can version my changes and guarantee that I can move back and forth at every
moment.
Moreover a smart integration server may be configured to erase and recreate the repository when some
of these changes are fetched.
In what regards the developers: they are using their one machines. Everything
else is a matter of
their experience to work inside a team :-).
./alex
--
.w( the_mindstorm )p.
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
