2 Replies Latest reply on Apr 27, 2007 11:09 AM by Paul Gier

    Problem with the build?

    Adrian Brock Master

      Anybody else seeing this?

      Project ID: jboss:jboss-dependency
      POM Location: /home/ejort/microcontainer/dependency/pom.xml
      Validation Messages:
      
       [0] 'dependencies.dependency.version' is missing for jboss:jboss-logging-log4j
       [1] 'dependencies.dependency.version' is missing for jboss:jboss-logging-spi
      
      
      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(DelegatingMethodAccessorImpl.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 validate POM
       at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:926)
       at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:737)
       at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416)
       at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.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
      


        • 1. Re: Problem with the build?
          Adrian Brock Master

          V.Strange.

          I added versions to those dependencies did a clean and rebuild,
          then I reverted the change to the pom and now I no longer see the error?

          Why do we have dependencies without versions anyway in our poms,
          are these defined somewhere else?

          • 2. Re: Problem with the build?
            Paul Gier Master

            There are a few dependencies where the version is defined in the parent instead of in the individual modules. This way you can make sure that all the modules are using the same version of that dependency.

            That happened in the dependency module? It looks like it was picking up the wrong names too. For those dependencies they should be jboss-common-logging-spi and jboss-common-logging-jdk.