Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12113

Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • None
    • Jenkins 1.448
      Subversion Plugin 1.37
      Maven Integration Plugin 1.448
      Ant 1.1

      Maven is unable to work if in Subversion configuration parameters are used in Local module directory section.
      As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in Local module directory section. And when I run it - Maven failed (svn_maven_issue_02.PNG) with java.io.IOException.

          [JENKINS-12113] Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section

          Oleksandr Popov created issue -
          Oleksandr Popov made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]

          Any update on this?

          Oleksandr Popov added a comment - Any update on this?
          Oleksandr Popov made changes -
          Description Original: Maven is unable to work if in Subversion configuration parameters used in Local module directory section.
          As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in Local module directory section. And when I run it - Maven failed (svn_maven_issue_02.PNG) with java.io.IOException.
          New: Maven is unable to work if in Subversion configuration parameters are used in Local module directory section.
          As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in Local module directory section. And when I run it - Maven failed (svn_maven_issue_02.PNG) with java.io.IOException.

          kutzi added a comment -

          This sounds suspiciously like a dup of JENKINS-11798 - which you have created, too ...

          kutzi added a comment - This sounds suspiciously like a dup of JENKINS-11798 - which you have created, too ...
          kutzi made changes -
          Link New: This issue duplicates JENKINS-11798 [ JENKINS-11798 ]

          kutzi added a comment -

          Another question is, why do you expect the Maven plugin to work correctly, if the subversion plugin is already not able to resolve the $Branch parameter?

          kutzi added a comment - Another question is, why do you expect the Maven plugin to work correctly, if the subversion plugin is already not able to resolve the $Branch parameter?
          kutzi made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          @kutzi Subversion plugin has resolved it correctly. The only this is exeption which is given by Maven plugin. It tries to execute mvn command from directory with includes $Branch variable. But it does not resolves variable before execution. That is the reason.

          Oleksandr Popov added a comment - @kutzi Subversion plugin has resolved it correctly. The only this is exeption which is given by Maven plugin. It tries to execute mvn command from directory with includes $Branch variable. But it does not resolves variable before execution. That is the reason.

          Oleksandr Popov added a comment - - edited

          @kutzi I have closed JENKINS-11798 ticket cause it is not actual (Subversion plugin is not the root of the issue). This ticket actually is not duplicate but provides deeper investigation of the same issue

          Oleksandr Popov added a comment - - edited @kutzi I have closed JENKINS-11798 ticket cause it is not actual (Subversion plugin is not the root of the issue). This ticket actually is not duplicate but provides deeper investigation of the same issue

            kutzi kutzi
            pxantom Oleksandr Popov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: