[jira] Commented: (MECLIPSE-310) mvn eclipse:eclipse fails to generate .classpath files for some poms
[
http://jira.codehaus.org/browse/MECLIPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244139#action_244139
]
Marcel Patzlaff commented on MECLIPSE-310:
--
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 "true" 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).
> mvn eclipse:eclipse fails to generate .classpath files for some poms
>
>
> Key: MECLIPSE-310
> URL: http://jira.codehaus.org/browse/MECLIPSE-310
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Reporter: Brian DePradine
>
> 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:
> mar, an example pom is included below. If this line is
> removed then the all eclipse artifacts are generated as expected.
> 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";>
> 4.0.0
>
> org.apache.axis2
> axis2-parent
> SNAPSHOT
> ../parent/pom.xml
>
> addressing
> mar
> Apache Axis 2.0 - Addressing
> WS-Addressing implementation
>
>
> org.apache.axis2
> axis2-kernel
> ${version}
>
>
>
> src
> test
>
>
> conf
>
> **/*.properties
>
> false
>
>
> src
>
> **/*.java
>
>
>
>
>
> ../test-resources
> test-resources
>
> **/**
>
>
>
>
>
> maven-surefire-plugin
> true
>
> false
>
> **/*Util.java
>
>
>
>
> org.apache.axis2
> axis2-mar-maven-plugin
> ${version}
> true
>
>
> false
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-310) mvn eclipse:eclipse fails to generate .classpath files for some poms
[
http://jira.codehaus.org/browse/MECLIPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=187778#action_187778
]
Ostap Antonevych commented on MECLIPSE-310:
---
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
mar element.
> mvn eclipse:eclipse fails to generate .classpath files for some poms
>
>
> Key: MECLIPSE-310
> URL: http://jira.codehaus.org/browse/MECLIPSE-310
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Reporter: Brian DePradine
>
> 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:
> mar, an example pom is included below. If this line is
> removed then the all eclipse artifacts are generated as expected.
> 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";>
> 4.0.0
>
> org.apache.axis2
> axis2-parent
> SNAPSHOT
> ../parent/pom.xml
>
> addressing
> mar
> Apache Axis 2.0 - Addressing
> WS-Addressing implementation
>
>
> org.apache.axis2
> axis2-kernel
> ${version}
>
>
>
> src
> test
>
>
> conf
>
> **/*.properties
>
> false
>
>
> src
>
> **/*.java
>
>
>
>
>
> ../test-resources
> test-resources
>
> **/**
>
>
>
>
>
> maven-surefire-plugin
> true
>
> false
>
> **/*Util.java
>
>
>
>
> org.apache.axis2
> axis2-mar-maven-plugin
> ${version}
> true
>
>
> false
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-310) mvn eclipse:eclipse fails to generate .classpath files for some poms
[
http://jira.codehaus.org/browse/MECLIPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174913#action_174913
]
Peter Monks commented on MECLIPSE-310:
--
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.
> mvn eclipse:eclipse fails to generate .classpath files for some poms
>
>
> Key: MECLIPSE-310
> URL: http://jira.codehaus.org/browse/MECLIPSE-310
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Reporter: Brian DePradine
>
> 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:
> mar, an example pom is included below. If this line is
> removed then the all eclipse artifacts are generated as expected.
> 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";>
> 4.0.0
>
> org.apache.axis2
> axis2-parent
> SNAPSHOT
> ../parent/pom.xml
>
> addressing
> mar
> Apache Axis 2.0 - Addressing
> WS-Addressing implementation
>
>
> org.apache.axis2
> axis2-kernel
> ${version}
>
>
>
> src
> test
>
>
> conf
>
> **/*.properties
>
> false
>
>
> src
>
> **/*.java
>
>
>
>
>
> ../test-resources
> test-resources
>
> **/**
>
>
>
>
>
> maven-surefire-plugin
> true
>
> false
>
> **/*Util.java
>
>
>
>
> org.apache.axis2
> axis2-mar-maven-plugin
> ${version}
> true
>
>
> false
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-310) mvn eclipse:eclipse fails to generate .classpath files for some poms
[
http://jira.codehaus.org/browse/MECLIPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172457#action_172457
]
Arnaud Heritier commented on MECLIPSE-310:
--
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
> mvn eclipse:eclipse fails to generate .classpath files for some poms
>
>
> Key: MECLIPSE-310
> URL: http://jira.codehaus.org/browse/MECLIPSE-310
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Reporter: Brian DePradine
>
> 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:
> mar, an example pom is included below. If this line is
> removed then the all eclipse artifacts are generated as expected.
> 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";>
> 4.0.0
>
> org.apache.axis2
> axis2-parent
> SNAPSHOT
> ../parent/pom.xml
>
> addressing
> mar
> Apache Axis 2.0 - Addressing
> WS-Addressing implementation
>
>
> org.apache.axis2
> axis2-kernel
> ${version}
>
>
>
> src
> test
>
>
> conf
>
> **/*.properties
>
> false
>
>
> src
>
> **/*.java
>
>
>
>
>
> ../test-resources
> test-resources
>
> **/**
>
>
>
>
>
> maven-surefire-plugin
> true
>
> false
>
> **/*Util.java
>
>
>
>
> org.apache.axis2
> axis2-mar-maven-plugin
> ${version}
> true
>
>
> false
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-310) mvn eclipse:eclipse fails to generate .classpath files for some poms
[
http://jira.codehaus.org/browse/MECLIPSE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172433#action_172433
]
Brian DePradine commented on MECLIPSE-310:
--
This issue was resolved by moving to mvn 2.0.10.
> mvn eclipse:eclipse fails to generate .classpath files for some poms
>
>
> Key: MECLIPSE-310
> URL: http://jira.codehaus.org/browse/MECLIPSE-310
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
>Reporter: Brian DePradine
>
> 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:
> mar, an example pom is included below. If this line is
> removed then the all eclipse artifacts are generated as expected.
> 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";>
> 4.0.0
>
> org.apache.axis2
> axis2-parent
> SNAPSHOT
> ../parent/pom.xml
>
> addressing
> mar
> Apache Axis 2.0 - Addressing
> WS-Addressing implementation
>
>
> org.apache.axis2
> axis2-kernel
> ${version}
>
>
>
> src
> test
>
>
> conf
>
> **/*.properties
>
> false
>
>
> src
>
> **/*.java
>
>
>
>
>
> ../test-resources
> test-resources
>
> **/**
>
>
>
>
>
> maven-surefire-plugin
> true
>
> false
>
> **/*Util.java
>
>
>
>
> org.apache.axis2
> axis2-mar-maven-plugin
> ${version}
> true
>
>
> false
>
>
>
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
