Fortunately they have updated those wrong 1.0 poms in the central
ibiblio repository, so the problem solved itself a different way.
Maybe one still reports this problem to the maven embedder project.
What version do you use? May maven command line is version 2.0.4, so
you probably have a newer maven embedder.
Alex
Am 29.01.2007 um 05:07 schrieb Eugene Kuleshov:
Well, Eclipse plugin is not reading these poms and instead
delegating to the Maven Embedder component, which is also used by
Maven's command line tool. I guess something had been changed in
Maven core, so it now fail on m1 poms...
regards,
Eugene
Alexander Klimetschek wrote:
As I wrote, the pom.xml for that geronimo project is a real 1.0
pom and it's not a typing error. Maven normally ignores 1.0 poms
that are incorrectly put into maven 2 repositories (which is the
case due to dependency resolving, so maven 2 automatically puts
those poms into my local repository after downloading them, i have
never seen or touched those poms before).
Alex
Am 27.01.2007 um 00:55 schrieb David Friedman:
I think it is modelVersion now insteadof "pomVersion" at least
for the
latest Maven POM format. I start my pom.xml file like so:
C:\something>more pom.xml
<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instanc
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
<modelVersion>4.0.0</modelVersion>
<groupId>com.somecompany</groupId>
<artifactId>something</artifactId>
<packaging>war</packaging>
...etc...
</project>
How does your pom.xml file begin? I wonder if this is a problem
with the
embedder having issues with older pom formats or if you have a
previously
un-noticed typing error.
Regards,
David
-----Original Message-----
From: Alexander Klimetschek
[mailto:[EMAIL PROTECTED]
Sent: Friday, January 26, 2007 7:41 AM
To: [email protected] <mailto:[email protected]>
Subject: [m2eclipse-user] Build fails with dependency on project
with
Maven 1.0 pom [new in 0.0.10]
Hi,
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>
Any workaround possible? I currently have to turn off m2eclipse and
go with "mvn eclipse:eclipse" on the cli.
Alex
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
Alexander Klimetschek
Chief Architect
Tel: +49 (331) 97992 221 | Mindquarry GmbH
Mobil : +49 (177) 629 51 72 | August-Bebel-Str. 88
Fax: +49 (331) 97992 229 | 14482 Potsdam
Web: http://www.mindquarry.com | Geschäftsführer: Stephan Voigt
Amtsgericht Potsdam, HRB 19640P | St.-Nr.: 046/114/03173 |
DE250472046
Mindqarry Blog: http://weblogs.goshaky.com/weblogs/mindquarry/
E-Mail: [EMAIL PROTECTED]
Skype: alexander.klimetschek
Jabber: [EMAIL PROTECTED]
OpenBC Profile: http://www.openbc.com/go/invite/3268380.32d2d4
LinkedIn Profile: http://www.linkedin.com/in/klimetschek
