Q: Which OpenCms versions are supported by the OpenCms-Maven Plugin?
A: Currently OpenCms 11.0.2, 11.0.1, 11.0.0, 10.5.2, 10.0.1, 9.5.3, 9.5.2, 9.5.1, 9.0.1, 9.0.0, 8.5.2, 8.5.1, 7.5.2, 7.5, 7.0.5 and 7.0.3 are supported.
Q: Is it possible to synchronize properties of VFS resources?
A: Yes. The properties will be synchronized in a special file system tree called vfs-metadata
Q: What licence does OpenCms-Maven ship with?
A: OpenCms-Maven is shipped with the Lesser GNU public licence (LGPL)
Q: Where is my opencms.log?
A: If you did not specify a path in /WEB-INF/classes/log4j.properties, your opencms logfile will most likely be in the root folder of your Tomcat installation.
Q: How should be the project setup for developing custom modules with templates and Java classes?
A: Create two Maven artifacts. One of type pom, which uses the maven-vfs-plugin, and that includes the VFS-files and the opencms-module.xml file, like in the module system, but including directly the <module> element, taken from opencms-modules.xml. The other artifact is of type jar and will be referenced as dependency by the webapp module. This two artifacts will be referenced as modules by the parent project.
Q: How should 3rd party modules (like OAMP Webforms) be imported?
A: Create a new Maven module for the 3rd party OpenCms module like the one described in the previous answer. If you have the sources of the OpenCms module, you can also remove the jar corresponding to those sources, and generate this jar as an artifact in each Maven Build. So, the process should be to
1. Import the Module to a running OpenCms
2. Create a new module of type pom which includes the plugin in the build section, like this:
3. Call vfs:sync
4. The text taken from opencms-modules.xml, has to be written in /src/main/opencms-module/opencms-module.xml of your new module.
Q: Is it possible to debug JSP's?
A: About debugging JSP's, I would refer you to http://www.opencms-wiki.org/wiki/Remote_debugging_OpenCms_with_Eclipse_and_Netbeans.