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

Mavem module symlinks in builds history are invalid under Windows 7

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • maven-plugin
    • None
    • OS: Windows 7 Professional SP1
      JDK: 1.6.0_16

      The links to module directories in builds history are created as invalid symlinks with wrong relative path (directory separator "/" is used instead of "\").

      23.05.2013  00:10    <SYMLINKD>     my.groupid$my-artifactid [../../modules/my.groupid$my-artifactid/builds/2013-05-23_00-06-06]

      This problem seems to be similar to JENKINS-17681 but is not fixed in version 1.515.

          [JENKINS-18072] Mavem module symlinks in builds history are invalid under Windows 7

          Jesse Glick added a comment -

          See comments in JENKINS-17681 after it was reopened.

          Jesse Glick added a comment - See comments in JENKINS-17681 after it was reopened.

          Joe Knudsen added a comment - - edited

          Still having this problem with Maven on 1.509.4 I am using Window Server 2008 R2. Seems like a new feature in Maven to add Module Builds time is causing this. The files include a $ symbol which in Windows has a special meaning.

          Joe Knudsen added a comment - - edited Still having this problem with Maven on 1.509.4 I am using Window Server 2008 R2. Seems like a new feature in Maven to add Module Builds time is causing this. The files include a $ symbol which in Windows has a special meaning.

          Jesse Glick added a comment -

          @jknudsen sounds like your issue is unrelated to this one, so please file it separately with any steps you have to reproduce.

          Jesse Glick added a comment - @jknudsen sounds like your issue is unrelated to this one, so please file it separately with any steps you have to reproduce.

            Unassigned Unassigned
            ddbear Volodja Medvid
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: