Development Environment Setup Options
(Difference between revisions)
| Line 14: | Line 14: | ||
*The Alkacon way of developing modules: [[Developing_OpenCms_with_Eclipse]] | *The Alkacon way of developing modules: [[Developing_OpenCms_with_Eclipse]] | ||
*A Maven archetype and how to use it in Eclipse: [[Developing_OpenCms_with_Maven_%28inkl._Eclipse%29]] | *A Maven archetype and how to use it in Eclipse: [[Developing_OpenCms_with_Maven_%28inkl._Eclipse%29]] | ||
| + | *Another Maven Plugin that uses [[CmsShell]] to import modules automatically: [https://redmine.synyx.org/projects/maven-opencms-plugin] | ||
Revision as of 18:34, 13 April 2011
There is no one true way to develop modules with OpenCms. Several different solutions have been developed one can choose from.
The main difficulty is that all assets (at least JSPs) need to be stored in the virtual filesystem (VFS) and can not be edited in the normal filesystem (RFS).
- An Ant target that can be used to synchronize files from RFS with VFS: Synchronizing with Ant
- Using WebDAV to update files: OpenCms 7: WebDAV access to the OpenCms VFS
- One of the Maven options, using the OpenCms synchronization feature: Automated builds with OpenCms-Maven
- Eclipse integration options: Eclipse integration
- Eclipse Integration on the MAC
- A FTP-Module for accessing the files in VFS using FTP: Ftpd module
- The OpenCms synchronization feature in detail: Synchronization with external directories
- An Ant task to generate modules that can be imported in OpenCms: ManifestBuilder Task
- A Netbeans Plugin to upload files to OpenCms: [1]
- The Alkacon way of developing modules: Developing_OpenCms_with_Eclipse
- A Maven archetype and how to use it in Eclipse: Developing_OpenCms_with_Maven_(inkl._Eclipse)
- Another Maven Plugin that uses CmsShell to import modules automatically: [2]
