Or maybe we could just have a central Magnolia instance running in an
integration environment; and 

Every developer sets this central instance as a subscriber to its own local
instance.  

So, each time a developer creates content assets (dialog etc), he needs only
to activate it so it gets propagated to the central instance.  

How does this sounds to you?

JS.

Note: But then again, if two developers are updating the same content asset,
overwrite problems might occur.  I need to think about this sort of
situation, and find a way to merge both developer's version. 

-----Message d'origine-----
De : [email protected] [mailto:[EMAIL PROTECTED] 
Envoyé : 1 décembre 2005 14:29
À : [email protected]
Objet : [magnolia-user] AW: [magnolia-user] Multiple developers


> I was wondering:  how does many developers manages to update a common 
> repository with all their changes?

hi js! 

oh yes! i have exactly the same problem. at this time i turned to jackrabbit
ressources to find hints and code/conf-snippets to solve it:
http://incubator.apache.org/jackrabbit/doc/arch/deploy.html (scroll down)
http://incubator.apache.org/jackrabbit/doc/arch/deploy/howto-model3.html

the solution might be to set up a remote repository component accessible by
rmi. rmi is said to be slow, but for running some local author instances
using that common remote repository it may do the job (you wont need it
anymore for the live deployment). in jackrabbits svn trunk in the contrib
folder there is code: 
http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/contrib/

i am trying to integrate it with magnolia. lets keep in touch... 
- or, guys, am i totally wrong with this approach?

bye
j


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to