Developing OpenCms with Maven (inkl. Eclipse)
(Difference between revisions)
(→Developing OpenCms with Maven) |
(→Limitation) |
||
| Line 19: | Line 19: | ||
=== Limitation === | === Limitation === | ||
| − | * ArtifactId must be the OpenCms Module Name (This simplify the build-Process) | + | * ArtifactId must be the OpenCms Module Name (This simplify the build-Process). The OpenCms Modulename must be a valid classpath (This is the package where OpenCms search a message.properties at Startup). |
=== Recommendations === | === Recommendations === | ||
Revision as of 14:22, 13 June 2011
Contents |
Developing OpenCms with Maven
Creating the template of the Opencms-Module is as easy as executing:
mvn archetype:generate -DarchetypeCatalog=http://bp-cms-commons.sourceforge.net/m2repo
Select option 1, set properties and that's all!
See http://bp-cms-commons.sourceforge.net/m2site/infonova/archetypes/opencms-module-archetype/1.0.1/
Pros
- Build with Maven: you can use all Maven Plugins to analyze your code.
- The maven release plugin works also fine.
- Eclipse: create your Eclipse-config with "mvn eclipse:eclipse"
- UnitTests: Real OpenCms Unittest which starts an Opencms instance and reas OpenCms configurations already works.
Limitation
- ArtifactId must be the OpenCms Module Name (This simplify the build-Process). The OpenCms Modulename must be a valid classpath (This is the package where OpenCms search a message.properties at Startup).
Recommendations
For your own Project you should copy the parent pom.xml and modify it (at least SCM and distributionManagement section):
