Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-19018

AbstractSingleValueCustomFieldSearchInputTransformer$NavigatorConversionResult.class and parent directories causes 'name too long' for Win32 NTFS

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Highest
    • None
    • 4.0
    • Installation

    • Windows Server 2003 R2 SP3, Intel 32bit x86, Sun JDK 6.0 1.6.0_16, Microsoft SQL Server 2005, QA-ENT-355

    Description

      A user will be unable to install JIRA 4.0 under any directory that already has 61 characters in it.

      The file AbstractSingleValueCustomFieldSearchInputTransformer$NavigatorConversionResult.class in atlassian-jira-enterprise-4.0-SNAPSHOT-standalone/atlassian-jira/WEB-INF/classes/com/atlassian/jira/issue/customfields/searchers/transformer/ creates a path that is too long for NTFS when there are already 61 characters in the path, see http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-7143 Can't unzip jira into directory with a long path name

          • Medium - Medium priority issues
          • Closed
          was cloned as

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-19022 Document AbstractSingleValueCustomFieldSearchInputTransformer$NavigatorConversionResult.class and parent directories causes 'name too long' for Win32 NTFS workaround in CAC

          • Medium - Medium priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              pdzwart PdZ (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: