You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rick McGuire (JIRA)" <ji...@apache.org> on 2006/11/01 19:06:17 UTC
[jira] Resolved: (GERONIMO-2217) Missing versions for dependencies
in modules/mail/pom.xml
[ http://issues.apache.org/jira/browse/GERONIMO-2217?page=all ]
Rick McGuire resolved GERONIMO-2217.
------------------------------------
Resolution: Cannot Reproduce
This is working properly now. I suspect the problem was the need to get the root pom.xml into the repository using mvn -N first so that the module build could locate the version information.
> Missing versions for dependencies in modules/mail/pom.xml
> ---------------------------------------------------------
>
> Key: GERONIMO-2217
> URL: http://issues.apache.org/jira/browse/GERONIMO-2217
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: buildsystem
> Environment: Maven 2.0.4, JDK 1.4.2_08, Geronimo trunk
> Reporter: Fredrik Westermarck
> Assigned To: Rick McGuire
>
> The versions for geronimo-javamail_1.3.1_spec and org.apache.geronimo.javamail is missing in modules/mail/pom.xml. This makes the validation of the poms made by maven when building modules to fail.
> The following is the output from maven:
> D:\apache\geronimo\modules>mvn
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
> Project ID: org.apache.geronimo.modules:geronimo-mail
> POM Location: D:\apache\geronimo\modules\mail\pom.xml
> Validation Messages:
> [0] 'dependencies.dependency.version' is missing for org.apache.geronimo.j
> vamail:geronimo-javamail_1.3.1_provider
> Reason: Failed to validate POM
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Failed to validate POM
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to val
> date POM
> at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLo
> ic(DefaultMavenProjectBuilder.java:926)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(De
> aultMavenProjectBuilder.java:737)
> at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceF
> leInternal(DefaultMavenProjectBuilder.java:416)
> at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMav
> nProjectBuilder.java:192)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
> at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
> at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:491)
> at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
> ... 11 more
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5 seconds
> [INFO] Finished at: Sat Jul 22 12:45:34 CEST 2006
> [INFO] Final Memory: 3M/6M
> [INFO] ------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira