...

Install Eclipse & Plugins

Eclipse Indigo (3.7)

If you're at the Magnolia premises, a preinstalled eclipse for Mac OS X(Cocoa 64) called eclipse-indigo-macosx-cocoa-64.zip can be found at our file server under Product Development/Eclipse

The eclipse-indigo-macosx-cocoa-64.zip bundle was created on 3 August 2011 and consists of the latest core platform + integrated maven support + subclipse + AnyEdit Tools + Freemarker IDE + checkstyle plugin. For more information concerning the preinstalled software/plugins, please look at the Eclipse Installation Details.

• m2e 1.0 known issue:

Indigo introduces m2e (Maven 2 Eclipse) 1.0, which seems to cause some problems with plugins that are not "known" by m2e. This hits Magnolia with the setproperty Maven plugin. If you have m2e 1.0 installed you will likely get the following error upon importing a Maven project (i.e. a Magnolia module) into Eclipse: 

Image Added

No worries. Choose to resolve the issue later and import the project.

Now, in the Eclipse Markers view you should get the following Maven error preventing the project from building (you should also receive some negligible warnings about m2e ignoring some plugin's goals):

Again, no worries To get rid of the error and proceed with project build you'll need to add the following snippet to the pluginManagement/plugins section of your project's pom.xml

<plugin>
<!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself. -->
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
  <lifecycleMappingMetadata>
    <pluginExecutions>
      <pluginExecution>
        <pluginExecutionFilter>
          <groupId>info.magnolia</groupId>
          <artifactId>maven-setproperty-plugin</artifactId>
          <versionRange>[1.1.1,)</versionRange>
          <goals>
            <goal>set-property</goal>
          </goals>
        </pluginExecutionFilter>
        <action>
          <execute></execute>
        </action>
      </pluginExecution>
    </pluginExecutions>
  </lifecycleMappingMetadata>
</configuration>
</plugin>

Should your module inherit from *magnolia-parent-pom version 20*, then m2e should not cause any problem as the above fix was applied globally to our parent pom (see [http://jira.magnolia-cms.com/browse/BUILD-72]). This pom fix might not be needed in the future, as soon as this \[https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414\| m2e issue\] will be accepted and solved.

For some background info and the ratio behind this new behaviour in m2e, please read:

http://wiki.eclipse.org/M2E_plugin_execution_not_coveredhttp://dev.eclipse.org/mhonarc/lists/m2e-users/thrd7.html

http://dev.eclipse.org/mhonarc/lists/m2e-users/thrd7.html starting at http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00448.html

• magnolia-empty-webapp configuration

The new version of Maven integration For WTP plugin, will create a /target/m2e-wtp folder and serve project resources from there. This may cause issues when choosing to serve modules without publishing them in the Servers configuration. To solve this,

• go to project Properties -> Deployment Assembly
• remove the m2e-wtp folder
• add src/main/webapp folder and src/main/resources folders 

Your conguration should look similar to that of the screenshot below.
Image Added

Notice that when importing new modules which magnolia-empty-webapp depends on, the Deployment Assembly configuration will be automatically updated. In the example above, the magnolia-ui-admincentral module was imported after the magnolia-empty-webapp and is now directly served from the eclipse workspace instead of the local Maven repository jar.

Eclipse Helios (3.6)

If you're at the Magnolia premises, a preinstalled eclipse for Mac OS X(Cocoa 64) called eclipse-helios-macosx-cocoa-64.zip can be found at our file server under Product Development/Eclipse

...