[mng] build fails with dependency on project with Maven 1.0 pom

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 0.0.10
  • Fix Version/s: None
  • Component/s: Maven Embedder
  • Labels:
    None
  • Environment:
    Eclipse 3.2.1, MaxOS X 10.4.8

Description

I switched from 0.0.9 to 0.0.10 and now face a serious problem: our project has transitive dependencies to modules with an old Maven 1.0 POM in the local repository (geronimo-spec-javamail/1.3.1-rc3 and geronimo-spec-jms/1.1-rc4). Upon building in Eclipse the m2eclipse plugin now stops the build when it comes to those POMs and throws those errors:

<snip>

26.01.07 13:18:22 CET: Parsing error /Users/alex/.m2/repository/geronimo-spec/geronimo-spec-javamail/1.3.1-rc3/geronimo-spec-javamail-1.3.1-rc3.pom; org.codehaus.plexus.util.xml.pull.XmlPullParserException: Unrecognised tag: 'pomVersion' (position: START_TAG seen .../3.0.0 http://maven.apache.org/maven-v3_0_0.xsd">\n <pomVersion>... @30:17)
26.01.07 13:18:22 CET: Unable to read model from /mindquarry-teamspace/pom.xml; org.eclipse.core.runtime.CoreException: Parsing error /Users/alex/.m2/repository/geronimo-spec/geronimo-spec-javamail/1.3.1-rc3/geronimo-spec-javamail-1.3.1-rc3.pom; org.codehaus.plexus.util.xml.pull.XmlPullParserException: Unrecognised tag: 'pomVersion' (position: START_TAG seen .../3.0.0 http://maven.apache.org/maven-v3_0_0.xsd">\n <pomVersion>... @30:17)

</snip>

Then it marks the pom.xml in the project inside Eclipse as erroneous and stops resolving the other dependencies, which leads to lots of build errors due to missing imports.

This has worked with the previous version 0.0.9 (the geronimo dependencies did not change) and it works with a normal mvn call on the command line, where it just prints out a warning:

<snip>

[WARNING] POM for 'geronimo-spec:geronimo-spec-javamail:pom:1.3.1-rc3:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
[WARNING] POM for 'geronimo-spec:geronimo-spec-jms:pom:1.1-rc4:compile' is invalid. It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.

</snip>

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Alexander Klimetschek added a comment -

Sorry, i cannot provide a test project for reproducing the error. Simply add a reference to geronimo-spec:geronimo-spec-javamail:pom:1.3.1-rc3 or geronimo-spec:geronimo-spec-jms:pom:1.1-rc4 in your pom.

M2Eclipse or the MavenEmbedder should not stop at the Exception but ignore the problem/pom and continue the build.

Show
Alexander Klimetschek added a comment - Sorry, i cannot provide a test project for reproducing the error. Simply add a reference to geronimo-spec:geronimo-spec-javamail:pom:1.3.1-rc3 or geronimo-spec:geronimo-spec-jms:pom:1.1-rc4 in your pom. M2Eclipse or the MavenEmbedder should not stop at the Exception but ignore the problem/pom and continue the build.
Hide
Permalink
Eugene Kuleshov added a comment -

Fail on first error is a known issue, but why on Earth would you put m1 poms into the local m2 repository?

Show
Eugene Kuleshov added a comment - Fail on first error is a known issue, but why on Earth would you put m1 poms into the local m2 repository?
Hide
Permalink
Alexander Klimetschek added a comment -

Its a dependency of a dependency of a dependency.... Maven put this into my local m2 repository. Ask the developers of geronimo why they don't like maven 2... Well, command line maven is able to ignore this wrong pom, so why not let m2eclipse behave the same way?

Show
Alexander Klimetschek added a comment - Its a dependency of a dependency of a dependency.... Maven put this into my local m2 repository. Ask the developers of geronimo why they don't like maven 2... Well, command line maven is able to ignore this wrong pom, so why not let m2eclipse behave the same way?
Hide
Permalink
Eugene Kuleshov added a comment -

Alexander, plugin supposed to use the same Maven component as the command line. It sounds like some Embedder issue.

Jason, can you please take a look at this.

Show
Eugene Kuleshov added a comment - Alexander, plugin supposed to use the same Maven component as the command line. It sounds like some Embedder issue. Jason, can you please take a look at this.
Hide
Permalink
Chris Frohoff added a comment -

This would really help organizations using eclipse with a lot of proprietary maven 1.x artifacts/libraries migrate to maven 2.x piecemeal.

Show
Chris Frohoff added a comment - This would really help organizations using eclipse with a lot of proprietary maven 1.x artifacts/libraries migrate to maven 2.x piecemeal.
Hide
Permalink
Jacob Robertson added a comment -

+1 from my company. Some of us have been working on projects that are all maven2. Now that we've started working on some other projects that use maven1 artifacts, we are all rolling back m2eclipse to use 0.0.9 which is very sad because 0.0.11 fixed some other headaches we were having.

Show
Jacob Robertson added a comment - +1 from my company. Some of us have been working on projects that are all maven2. Now that we've started working on some other projects that use maven1 artifacts, we are all rolling back m2eclipse to use 0.0.9 which is very sad because 0.0.11 fixed some other headaches we were having.
Hide
Permalink
Eugene Kuleshov added a comment -

Jacob, are you willing to provide test project that would allow to reproduce and further debug this issue?

Show
Eugene Kuleshov added a comment - Jacob, are you willing to provide test project that would allow to reproduce and further debug this issue?
Hide
Permalink
Chris Frohoff added a comment -

I've had success using a local apache proxy configured to just block the download of 1.x POMs as workaround until this gets fixed.

Show
Chris Frohoff added a comment - I've had success using a local apache proxy configured to just block the download of 1.x POMs as workaround until this gets fixed.
Hide
Permalink
Jacob Robertson added a comment -

I would have sent this when requested, but failed to watch this topic so I didn't see your request until today...

I have attached a zip with two eclipse projects in it. One is a maven-1-project, and one is a maven-2- project. Just follow the instructions outlined in the Readme.txt (also pasted here) to see the behavior.

Preconditions:
have both maven1 and maven2 ("remote") repos setup with deploy permissions to the maven1 repo
your build.properties points correctly to that maven1 repo
your settings.xml points to both repos (using <layout>legacy</layout> and <layout>default</layout> respectively)

Step 1: run "maven jar:deploy" on maven-1-project
This will compile it and put it out in your maven1 repo

Step 2: run "mvn compile" on maven-2-project (from command line)
This is what should happen:
It will download the maven-1-project, and put it into your local maven2 repo
It will successfully compile, but with warnings.

Step 3: open up a new eclipse workspace and import the 2 projects.

Step 4: build maven-2-project in eclipse
Will "fail" for the reasons outlined in MNGECLIPSE-257
Oddly enough, in my workspace it's still compiling the class to the bin directory, but the SomeChild.java and pom.xml still
have quite a bit of red markup on them.

Show
Jacob Robertson added a comment - I would have sent this when requested, but failed to watch this topic so I didn't see your request until today... I have attached a zip with two eclipse projects in it. One is a maven-1-project, and one is a maven-2- project. Just follow the instructions outlined in the Readme.txt (also pasted here) to see the behavior. Preconditions: have both maven1 and maven2 ("remote") repos setup with deploy permissions to the maven1 repo your build.properties points correctly to that maven1 repo your settings.xml points to both repos (using <layout>legacy</layout> and <layout>default</layout> respectively) Step 1: run "maven jar:deploy" on maven-1-project This will compile it and put it out in your maven1 repo Step 2: run "mvn compile" on maven-2-project (from command line) This is what should happen: It will download the maven-1-project, and put it into your local maven2 repo It will successfully compile, but with warnings. Step 3: open up a new eclipse workspace and import the 2 projects. Step 4: build maven-2-project in eclipse Will "fail" for the reasons outlined in MNGECLIPSE-257 Oddly enough, in my workspace it's still compiling the class to the bin directory, but the SomeChild.java and pom.xml still have quite a bit of red markup on them.

People

  • Assignee:
    Unassigned
    Reporter:
    Alexander Klimetschek
Vote (4)
Watch (5)

Dates

  • Created:
    Updated: