Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

Install Eclipse & Plugins

A preinstalled eclipse can be found at our files server Software:/MacOSX/Software/Eclipse

Install Eclipse (3.3.2)

Download the Java EE edition. It must include WTP.

Subversive (Subversion Plugin)

Register the following URLs in Help / Software Updates

Maven integration

Register the following URLs in Help / Software Updates

JIRA integration

  • Check Mylyn Extras and select JIRA integration

FreeMarker IDE

Register the following URLs in Help / Software Updates

Setup Project(s)

Single Module


  1. open "SVN Repository" perspective (Window -> Open perspective)
  2. select module to check out
  3. click "Check out" in the context menu

Enable Maven Dependency Management

Configure Project to use the eclipse maven profile

Importing a already checked out project from file system

Sometimes it is more convenient to checkout a project manually and then use the eclipse import function. This is especially helpful if the module to be imported has submodules.

  1. File -> Import
  2. in the import dialog select 'Maven Projects'
  3. configure the wizard to use the profile eclipse (advanced settings)

Using SCM checkout wizard

Create New Project

Select New / Other (not Project) 

Select Maven checkout from SCM

Provide subversion URL


2. Enable eclipse profile in the advanced settings

Check if you got all the projects (the sub modules)

Setup the Container (Tomcat for instance)

Create a Server

If not yet done create a server.

Deploy the Webapp project

Open Server Edit Pane

Doubleclick on the server item 

Disable publishing

Make sure that the option Serve modules without publishing is selected. This ensures that the classes are taken from the target directories. 

Freemarker specific settings

FreeMarker won't search the classpath for finding the tlds but uses only WEB-INF/lib and the entries defined in web.xml directly. There exist mainly the following two workarounds:

A) register the tlds in web.xml

edit web.xml and add the following lines:


And copy the files to webapp/WEB-INF

B) put minimal jars into WEB-INF/lib

1. in the webapp folder execute:

  mvn war:inplace

2. delete all jars except the taglib jars in src/main/webapp/WEB-INF/lib

3. minimize the taglib jar

 zip -d magnolia-taglib-cms-4.1.1-SNAPSHOT.jar /info/*
 zip -d magnolia-taglib-utility-4.1.1-SNAPSHOT.jar /info/*

Configure Code Style

If you are an internal developer or a contributor please follow the instructions found here: Code style

Tips and Tricks

Get the sources or a linked jar / module

  • select the jar (in the Maven Dependencies library)
  • right click -> Maven -> Download Sources


The dependencies are resolved inside the workspace. This is quite helpful. But this will only work if the version you reference in the project and the version of the module you checked out has the same version. In some cases you will have to adapt the pom files locally (to point to the current snapshot for instance).

Known Problems

Wrong maven version is used for dependency checks

If the project can't build because of the following message (printed in Maven Console)

[WARN] Rule 0: org.apache.maven.plugin.enforcer.RequireMavenVersion failed with message: Detected Maven Version: 2.1-SNAPSHOT is not in the allowed range [2.0.9,2.0.9].

The expected stacktrace on startup is:

SEVERE: Exception sending context initialized event to listener instance of class info.magnolia.cms.servlets.MgnlServletContextListener
	at info.magnolia.cms.beans.config.PropertiesInitializer.loadAllModuleProperties(
	at info.magnolia.cms.beans.config.PropertiesInitializer.loadAllProperties(
	at info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(
	at org.apache.catalina.core.StandardContext.listenerStart(
	at org.apache.catalina.core.StandardContext.start(

You can either add the following to the pluginManagement section if your main project pom to disable the enforcer plugin or select the eclipse profile:


Then clean all projects

To ensure that everything is fine you have to check if magnolia-core/target/classes/ exist.

Freemarker can't find tags (tlds)

See #Freemarkerspecificsettings

Project contains duplicate entry

Sometimes the same jar is references twice (by maven and EAR dependencies). This sometimes happens if you open eclipse freshly. To make the project compile again you must remove the ear dependency:

  • right click project -> Java EE -> Update EAR libraries

Class Cast Exception: info.magnolia.cms.filters.MgnlMainFilter


SEVERE: Exception starting filter magnoliaFilterChain
java.lang.ClassCastException: info.magnolia.cms.filters.MgnlMainFilter
	at org.apache.catalina.core.ApplicationFilterConfig.getFilter(
	at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(
	at org.apache.catalina.core.ApplicationFilterConfig.<init>(
	at org.apache.catalina.core.StandardContext.filterStart(
	at org.apache.catalina.core.StandardContext.start(
	at org.apache.catalina.core.ContainerBase.start(

Solution: exclude the servlet api jar. Verify that you don't have the servlet api jar in your maven dependencies.



Webapp project doesn't work

  1. make sure that you have only one webapp project open
  2. add the pom dependency (not only the war dependency) otherwise the dependencies defined in the referenced war file won't be seen
  3. use war:inplace to overlay the webapp project
    • ensure that you delete WEB-INF/lib afterwards

Trouble shooting step by step

  1. check if there are any build issues denoted in the problem view
  2. check if there are any problems denoted in the pom.xml (missing parents, ..)
  3. check if the project builds in the terminal (by using mvn only)
    • are the parent poms available?
  4. check the maven log in eclipse (select the maven console in the console view)
    • are the logs fine?
    • verify that there is no version conflict thrown by the enforcer plugin
      • if so configure the project to use the eclipse profile in the project settings (maven tab)
  5. clean the project
    • this ensures that maven is used to build the resources
    • verify that the resources have been built (module descriptor in taget/classes/META-INF/magnolia
  6. update project configuration
    • right click project -> maven -> update project configuration
    • check the maven console (some errors are not reported to the GUI)
  • No labels