Java API extending - current change set displays last change set assets
Hi,
I am experiencing the following issue using the RTC 4.0.2 Java API. First, I deliver a project (folder structures and files) to the repository with a change set comment. It displays correctly in the Repository Files view in the Jazz Admin perspective. I then move a subfolder and file within that project and deliver that update to the repository. The moved subfolder and file display correctly in the Repository Files view, but the issue is that the moved subfolder and file also display in their original location, as if I did a copy and not a move. And if I delete a previously delivered file and update the project using the API the file still appears in the current change set.
If I repeat the same actions and perform the deliver using the RTC client then the dir/file moves and deletions display correctly.
My API code merely discovers the repoPath of each dir and file under the project parent dir and passes it to iconfig.resolvePath to discover if it exists or not in the component, then does creation or update based on the state of filePathHandle.
IVersionableHandle filePathHandle = iconfig.resolvePath(cmpntroot, repoPath, monitor);
Do I also need to discover what exists on the component side and delete on the component side if it does not exist in the current package I am delivering? Or is there some property I can set which specifies to not include earlier change set revisions in the latest change set I am delivering? Thanks in advance!
Peter
Comments
Remy Suen
Oct 29 '13, 10:55 a.m.Peter Moraza
Oct 29 '13, 5:08 p.m.Peter Moraza
Nov 04 '13, 8:42 p.m.Peter Moraza
Nov 04 '13, 9:07 p.m.Peter Moraza
Nov 04 '13, 9:20 p.m.Remy Suen
Nov 05 '13, 8:35 a.m.Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Nov 05 '13, 9:42 a.m.Peter Moraza
Nov 06 '13, 9:51 p.m.