• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • violations-plugin
    • None

      Maven builds fail because of Violation plugin if there is submodules
      There is a missing slash in the submodule path when fetching Violations files

      For example, with a Maven project:

      • parent
        • service
        • presentation
          • webapp
        • dao
          Violation path is presentationwebapp instead of presentation/webapp

      FATAL: /home/workspace/hudson/jobs/esp/workspace/presentationwebapp does not exist.
      /home/workspace/hudson/jobs/esp/workspace/presentationwebapp does not exist.
      at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:474)
      at hudson.plugins.violations.ViolationsCollector.findFiles(ViolationsCollector.java:215)
      at hudson.plugins.violations.ViolationsCollector.doType(ViolationsCollector.java:166)
      at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:110)
      at hudson.plugins.violations.ViolationsCollector.invoke(ViolationsCollector.java:27)
      at hudson.FilePath.act(FilePath.java:756)
      at hudson.FilePath.act(FilePath.java:738)
      at hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end(ViolationsMavenReporter.java:96)
      at hudson.maven.Maven3Builder.end(Maven3Builder.java:207)
      at hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:626)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:417)
      at hudson.model.Run.run(Run.java:1362)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:400)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:145)

          [JENKINS-8452] Bad path for submodules

          Olivier Lamy added a comment -

          which hudson version are you using ? (1.391 ?)

          Olivier Lamy added a comment - which hudson version are you using ? (1.391 ?)

          aeris22 added a comment - - edited

          Same problem on 1.392 and your custom 1.393 (JENKINS-8362)
          Maven version is 3.0 (not try on 2.1.1)

          aeris22 added a comment - - edited Same problem on 1.392 and your custom 1.393 ( JENKINS-8362 ) Maven version is 3.0 (not try on 2.1.1)

          Olivier Lamy added a comment -

          You will have this with maven 2.2.1
          before 1.392 which version did you use ?
          I have reproduce with 1.391 too.

          Olivier Lamy added a comment - You will have this with maven 2.2.1 before 1.392 which version did you use ? I have reproduce with 1.391 too.

          aeris22 added a comment - - edited

          I use 1.382 and 1.386 before (2 hudson instances, same problem)
          And I try with a fresh 1.392 install, same problem too

          Globally, upgrade to or fresh install from 1.391 or upper break all builds, new Maven 3.0 jobs (seems «normal» considering young 3.X support) but (and it's very much blocking) old 2.X too (violations, mirrors, settings and cobertura problems in my cases)

          aeris22 added a comment - - edited I use 1.382 and 1.386 before (2 hudson instances, same problem) And I try with a fresh 1.392 install, same problem too Globally, upgrade to or fresh install from 1.391 or upper break all builds, new Maven 3.0 jobs (seems «normal» considering young 3.X support) but (and it's very much blocking) old 2.X too (violations, mirrors, settings and cobertura problems in my cases)

          Olivier Lamy added a comment -

          will be in 1.394

          Olivier Lamy added a comment - will be in 1.394

          dogfood added a comment -

          Integrated in hudson_main_trunk #422

          dogfood added a comment - Integrated in hudson_main_trunk #422

          Olivier Lamy added a comment -

          reopen as not fixed after more tests.

          Olivier Lamy added a comment - reopen as not fixed after more tests.

          dogfood added a comment -

          Integrated in hudson_main_trunk #427
          JENKINS-8452 Bad Path for submodules
          JENKINS-8452 really ensure we use the scm checkout path

          Olivier Lamy :
          Files :

          • maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java

          Olivier Lamy :
          Files :

          • maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java

          dogfood added a comment - Integrated in hudson_main_trunk #427 JENKINS-8452 Bad Path for submodules JENKINS-8452 really ensure we use the scm checkout path Olivier Lamy : Files : maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java Olivier Lamy : Files : maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java

            olamy Olivier Lamy
            aeris22 aeris22
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: