Try mvn -N install in the parent pom directory. Does that help?
Regards,
Anders
Rick McGuire wrote:
I think there may be a problem with this update. I'm getting the
following errors trying to build now:
C:\Yoko\builds\ns>mvn install
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.yoko:yoko-core
POM Location: C:\Yoko\builds\ns\core\pom.xml
Validation Messages:
[0] 'dependencies.dependency.version' is missing for junit:junit
[1] 'dependencies.dependency.version' is missing for
commons-logging:common
s-logging
[2] 'dependencies.dependency.version' is missing for
concurrent:concurrent
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(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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 vali
date POM
at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog
ic(DefaultMavenProjectBuilder.java:926)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def
aultMavenProjectBuilder.java:737)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
leInternal(DefaultMavenProjectBuilder.java:416)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave
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: < 1 second
[INFO] Finished at: Tue Jul 11 10:25:03 EDT 2006
[INFO] Final Memory: 1M/2M
[INFO]
------------------------------------------------------------------------
Anders Hessellund Jensen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/YOKO-77?page=all ]
Anders Hessellund Jensen closed YOKO-77:
----------------------------------------
Resolution: Fixed
Assign To: Anders Hessellund Jensen
$ svn commit -m 'YOKO-77: Versions of dependencies should be managed
in the parent POM'
Sending trunk/api/pom.xml
Sending trunk/bindings/pom.xml
Deleting trunk/core/.classpath
Sending trunk/core/pom.xml
Sending trunk/distribution/pom.xml
Sending trunk/maven-plugins/pom.xml
Sending trunk/pom.xml
Sending trunk/rmi/pom.xml
Sending trunk/tools/pom.xml
Transmitting file data ........
Committed revision 420846.
Versions of dependencies should be managed in the parent POM
------------------------------------------------------------
Key: YOKO-77
URL: http://issues.apache.org/jira/browse/YOKO-77
Project: Yoko - CORBA Server
Type: Bug
Reporter: Anders Hessellund Jensen
Assignee: Anders Hessellund Jensen
The versions of dependencies should be managed in the parent pom.
This can be done using the <dependencyManagement> section of the POM.
This should make it easier to change the versions of external
dependencies, as well as Yoko itself. Furthermore, it ensures that we
use the same versions across all sub-projects.
