[opencms-dev] OpenCMS Development in a team
Schliemann, Kai
K.Schliemann at comundus.com
Mon May 3 10:12:40 CEST 2010
Hi Thomas,
you might have a look at the OpenCms-Maven Plugin on http://opencms-maven.comundus.com/.
The plugin uses Maven to automatically build OpenCms projects. A maven-vfs-plugin retrieves the data from the vfs an writes them to the file system (actually it is doing a vfs sync). Now it is easy to use your versioning system to exchange your code changes between the developers.
If you have any further questions, please don't hesitate to ask.
Best regards
_________________________________________
Kai Schliemann
Senior IT-Berater
comundus GmbH
Schüttelgrabenring 3, D-71332 Waiblingen
Telefon +49 7151-50028-0
E-Mail k.schliemann at comundus.com <mailto:k.schliemann at comundus.com>
Internet www.comundus.com <http://www.comundus.com/>
Geschäftsführer Klaus Hillemeier
Amtsgericht Stuttgart, HRB 264290
comundus ist ein Unternehmen der IT EXCELLENCE Group
_________________________________________
Die Kundenzufriedenheit bei comundus wieder verbessert -
Durchschnittsnote jetzt 1,7.
Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Thomas Göttlich
Gesendet: Montag, 3. Mai 2010 10:03
An: opencms-dev at opencms.org
Betreff: [opencms-dev] OpenCMS Development in a team
Hi there,
we're currently starting our first bigger project based on OpenCMS.
However, we have some questions on how to setup a development environment that is suitable for developing in a team.
Thus, any help, ideas and suggestions are highly appreciated.
First, I'd like to give a quick overview on our current development process:
So far, we used a single shared database for development, so that any developer can use the same test data.
Development occured in otherwise isolated environments, i.e. each developer had her own JBoss, own working copy etc.
Source code distribution happened via Subversion whereas test data resided in the shared data base.
Additionally, we told JBoss where to find the application (especially the JSPs) in our working copy.
Thus we could just edit a JSP and immediately see the changes in the running application.
All this allowed us to code quickly, use the same test data without any hassle etc.
However, OpenCMS doesn't seem to support that approach.
As far as I know, OpenCMS needs all JSPs (and maybe the jars, too) to reside in the VFS which would make using a shared database for OpenCMS quite difficult.
Additionally, if we used a database per development machine, it would be difficult to distribute the test data.
The third point would be the instant editing of JSPs which doesn't seem to work, since we'd need synchronization with the VFS.
Do you have any ideas?
Or any hint on how you do OpenCMS development in a bigger team.
Thanks in advance,
Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20100503/413e9ef1/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4286 bytes
Desc: image001.jpg
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20100503/413e9ef1/attachment.jpg>
More information about the opencms-dev
mailing list