Maven 2.x Eclipse Plugin

mvn eclipse:eclipse fails to generate .classpath files for some poms

Details

  • Number of attachments :
    0

Description

Some modules in the Apache Axis2 project do not generate .classpath files. The common factor appears to be those modules that are packaged as MAR (Module ARchive) files. These pom for these modules all contain the following:
<packaging>mar</packaging>, an example pom is included below. If this line is removed then the all eclipse artifacts are generated as expected.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2-parent</artifactId>
<version>SNAPSHOT</version>
<relativePath>../parent/pom.xml</relativePath>
</parent>
<artifactId>addressing</artifactId>
<packaging>mar</packaging>
<name>Apache Axis 2.0 - Addressing</name>
<description>WS-Addressing implementation</description>
<dependencies>
<dependency>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2-kernel</artifactId>
<version>${version}</version>
</dependency>
</dependencies>
<build>
<sourceDirectory>src</sourceDirectory>
<testSourceDirectory>test</testSourceDirectory>
<resources>
<resource>
<directory>conf</directory>
<excludes>
<exclude>*/.properties</exclude>
</excludes>
<filtering>false</filtering>
</resource>
<resource>
<directory>src</directory>
<excludes>
<exclude>*/.java</exclude>
</excludes>
</resource>
</resources>
<testResources>
<testResource>
<targetPath>../test-resources</targetPath>
<directory>test-resources</directory>
<includes>
<include>*/*</include>
</includes>
</testResource>
</testResources>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<inherited>true</inherited>
<configuration>
<skip>false</skip>
<excludes>
<exclude>**/*Util.java</exclude>
</excludes>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.axis2</groupId>
<artifactId>axis2-mar-maven-plugin</artifactId>
<version>${version}</version>
<extensions>true</extensions>
<configuration>
<includeDependencies>false</includeDependencies>
</configuration>
</plugin>
</plugins>
</build>
</project>

Activity

Hide
Brian DePradine added a comment -

This issue was resolved by moving to mvn 2.0.10.

Show
Brian DePradine added a comment - This issue was resolved by moving to mvn 2.0.10.
Hide
Arnaud Heritier added a comment -

I think that a workaround for older maven versions is to set the packaging settings in the eclipse plugn to jar.
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#packaging

Show
Arnaud Heritier added a comment - I think that a workaround for older maven versions is to set the packaging settings in the eclipse plugn to jar. http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#packaging
Hide
Peter Monks added a comment -

This is still occurring with mvn 2.0.10, although in my case the module I'm working on is being packaged as an AMP (Alfresco Module Package - see http://wiki.alfresco.com/wiki/AMP_Files and http://repository.sourcesense.com/maven2-sites/maven-amp-plugin/). I also tried the workaround described above (force packaging=jar for the eclipse plugin) but that didn't change the behaviour.

Show
Peter Monks added a comment - This is still occurring with mvn 2.0.10, although in my case the module I'm working on is being packaged as an AMP (Alfresco Module Package - see http://wiki.alfresco.com/wiki/AMP_Files and http://repository.sourcesense.com/maven2-sites/maven-amp-plugin/). I also tried the workaround described above (force packaging=jar for the eclipse plugin) but that didn't change the behaviour.
Hide
Ostap Antonevych added a comment -

It still not works with mar packages:

mvn -version
Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
Java version: 1.5.0_11
Java home: C:\Programme\Java\jdk1.5.0_11\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

I get .classpath generated if I rename mar into jar in <packaging>mar</packaging> element.

Show
Ostap Antonevych added a comment - It still not works with mar packages: mvn -version Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100) Java version: 1.5.0_11 Java home: C:\Programme\Java\jdk1.5.0_11\jre Default locale: de_DE, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" I get .classpath generated if I rename mar into jar in <packaging>mar</packaging> element.
Hide
Marcel Patzlaff added a comment -

This problem is not fixed.
The maven-eclipse-plugin cannot resolve the component registry of the plugin extensions. In my case it is a midlet plugin and the packaging type is "midlet". With the "<extensions>true</extensions>" flag properly set in the build section all default goals (clean, compile, ...) can resolve the LifecycleMapping for "midlet".
But "eclipse:eclipse" can't and I don't know why.
From the sources I know, that the modules lifecycle mapping is used to obtain the packaging type (and to decide whether it is a Java module or not).

Show
Marcel Patzlaff added a comment - This problem is not fixed. The maven-eclipse-plugin cannot resolve the component registry of the plugin extensions. In my case it is a midlet plugin and the packaging type is "midlet". With the "<extensions>true</extensions>" flag properly set in the build section all default goals (clean, compile, ...) can resolve the LifecycleMapping for "midlet". But "eclipse:eclipse" can't and I don't know why. From the sources I know, that the modules lifecycle mapping is used to obtain the packaging type (and to decide whether it is a Java module or not).

People

Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: