Page History

...

1. cause: modules are not visible if the faceted build version of java doesn't match the current version or that used by the webapp project
2. solution: update project config and change java version

Module Dependency Exception

Symptom:

ERROR info.magnolia.init.MagnoliaServletContextListener : Oops, Magnolia could not be started
info.magnolia.module.model.reader.ModuleDependencyException: Module Magnolia Mail Module (version 4.5.0-SNAPSHOT) is dependent on myCoolModule version 4.5/*, which was not found.
   at info.magnolia.module.model.reader.DependencyCheckerImpl.checkSpecificDependency(DependencyCheckerImpl.java:79)

Solution: ensure that no resource is excluded under myCoolModule -> Build path -> Configure Build Path... This might happen when i.e. updating the Maven dependencies if the m2Eclipse plugin is installed.

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 target/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)
   • one last step can be added to the above Eclipse voodoo dance: ensure that no resource is excluded under