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

ccm finduse in synergy plugin does not work for subprojects

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • synergy-plugin
    • None
    • Platform: All, OS: All

      I am using the synergy SCM plugin to manage a project hierarchy that contains a
      number of subprojects. One of the steps that the plugin takes is to find where
      certain objects are being used and in particular it looks for the usage of the
      subprojects. However, the plugin is using the wrong form of the 'ccm finduse'
      command as the following excerpt from the log illustrates:

      [workspace] $ ccm query -u -f %displayname "cvtype='project' and is_member_of
      ('Server,intc_nsk_09.2')"
      bu,intc_nsk_09.2
      fn,intc_nsk_09.2
      if,intc_nsk_09.2
      metadh,intc_nsk_09.2
      sis_x,intc_nsk_09.2
      stlport,intc_nsk_09.2
      system,intc_nsk_09.2
      xml4c_x,nsk_1.01_20061013

      [workspace] $ ccm delim
      ,

      [workspace] $ ccm finduse system,intc_nsk_09.2
      Referenced object version could not be identified: 'system,intc_nsk_09.2'
      Warning: Could not identify object 'system,intc_nsk_09.2'

      [workspace] $ ccm finduse stlport,intc_nsk_09.2
      Referenced object version could not be identified: 'stlport,intc_nsk_09.2'
      Warning: Could not identify object 'stlport,intc_nsk_09.2'

      ......

      When using the ccm finduse command for a project the option '-p' must be
      included before the project spec. The form that the plugin currently uses only
      works for non-project objects.

      It is not clear to me exactly why the plugin is doing the finduse command,
      other than to display where newly included objects are being used, so the fact
      that the command is failing in this case may not really matter. However, it is
      not correct.

      Best wishes

      Stuart Barry

            jribette jribette
            swbarry swbarry
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: