Hi Olivier,
Your right, that extra lifecycleMapping extension point in my plugin.xml was just my attempt at trying to debug this and get things work. I removed that extention, so now my plugin.xml only looks like this:
<plugin>
<extension
point="org.eclipse.m2e.core.lifecycleMappingMetadataSource">
</extension>
<extension
point="org.eclipse.m2e.core.projectConfigurators">
<configurator
class="com.liferay.ide.maven.core.LiferayProjectConfigurator"
id="com.liferay.ide.maven.core.project.configurator"
name="Liferay Project Configurator"
secondaryTo="org.maven.ide.eclipse.configuration.wtp.configurator">
</configurator>
</extension>
</plugin>
And my lifecycle-mapping-metadata.xml looks like this:
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<versionRange>[2.0.1,)</versionRange>
<goals>
<goal>war</goal>
</goals>
</pluginExecutionFilter>
<action>
<configurator>
<id>com.liferay.ide.maven.core.project.configurator</id>
</configurator>
</action>
</pluginExecution>
<pluginExecution>
<pluginExecutionFilter>
<groupId>com.liferay.maven.plugins</groupId>
<artifactId>liferay-maven-plugin</artifactId>
<versionRange>[6.0.0,)</versionRange>
<goals>
<goal>build-css</goal>
<goal>build-ext</goal>
<goal>build-thumbnail</goal>
<goal>theme-merge</goal>
</goals>
</pluginExecutionFilter>
<action>
<configurator>
<id>com.liferay.ide.maven.core.project.configurator</id>
</configurator>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
But still no luck. Is there any chance that its the use of <goalPrefix> by the Liferay Maven Plugin?
