ClearCase: custom element types are treated as binary files.

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 2.5.6
    • Affects Version/s: 2.4.3, 2.5.0
    • Component/s: None

      In ClearCase, users (admins really) can define custom element types. However, FishEye only considers the following element types as text files:

      • text_file
      • xml

      The fix would be to get details about (custom) file types by executing:

      cleartool lstype -l -kind -eltype -invob <vob>
      

      any types that have a supertype (or supertype of a supertype) that equals text_file or xml should be treated as text files.

      A workaround is to use only the built-in types text_file and xml.

            Assignee:
            Conor (Inactive)
            Reporter:
            Michael Heemskerk (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h
                1h