Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>While the javadoc for <code>IConfiguration.determineAncestorsInHistory</code> doesn't specify, the server side equivalent <code>IScmService.configurationDetermineAncestorsInHistory</code> (which is what ends up being called) says this in the javadoc:</p> <blockquote> <pre><code> * @param versionableItemHandles * a list of versionable items; only the item ids are needed; * must not be &lt;code&gt;null&lt;/code&gt; </code></pre> </blockquote> <p>Basically, the determineAncestorsInHistory is not looking at the state id on the file handles, it only looks at the item id.</p> <p>The particular state of the file that will be considered is determined by the configuration. This is mostly because while the state of the file in the changeset will tell you the name of that file, it does not tell you the name of the parent folder. That will depend on the state of the folder that is present in the workspace at a particular time and could be different for different workspaces </p> <p>You basically need to get an IConfiguration that represents your workspace at the time the change set was accepted/created. </p> <p>The way I see to do this is to get the <code>IWorkspaceConnection.changeHistory(component)</code> (this is actually defined on IFlowNodeConnection). You will need to walk back through the histories by calling <code>IChangeHistory.previousHistory(monitor)</code> until you find one that contains your changeset in <code>IChangeHistory.recent(monitor)</code>. Once you find the appropriate IChangeHistory use <code>IChangeHistory.configuration()</code> for the determineAncestorsInHistory call.</p> <p>Note that this configuration represents the state of the workspace at the end of that particular IChangeHistory, so to be completely accurate you would need to inspect the changesets that occur after your change in the IChangeHistory.recent to see if any of them modified your file name (or also any of the containing folders' file names).</p> <p>(Another alternative is to use the history configuration 1 previous to the history that contains your changeset, and then look at the effects of the changes that happen before your change)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload