It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,629
×11,818
×1,193
×888
×20

question asked: Sep 08 '17, 12:58 p.m.
question was seen: 1,335 times
last updated: Sep 11 '17, 3:02 a.m.

Related questions

FAQ - How this Forum works

Accepting an incomplete change set that adds a new package to my workspace does not add the descendants

0
Chase Patterson (36●3) | asked Sep 08 '17, 12:58 p.m.
edited Sep 10 '17, 8:17 p.m. by David Lafreniere (4.8k●7)

 Hey there, 


I've noticed this a few times over the years and I just recently updated to RTC 6.0.4 and it continues to happen.  

If I am accepting a change set from someone that creates a new package, then the files underneath that package do not get created.  

Here are the steps:

  1. A developer creates a change set with an incomplete change.  This change set also adds a new package with some classes or other files underneath it. 
  2. As it's incomplete, it goes into "Pending Patches" under the "Pending Changes" view. 
  3. The first thing I notice is that "unresolved/UUID" shows up.  That ought to be the newly created package folder hierarchy, but instead it isn't resolved.  
  4. I attempt to auto-resolve the changes and everything is resolved except for the changes underneath the new package/folder. 

Is this a known limitation or should it be a defect?  What's the quickest workaround? I just manually created the files underneath that package.

Thanks,
Chase

Accepted answer

0
permanent link
David Lafreniere (4.8k●7) | answered Sep 10 '17, 8:16 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

It sounds like you might be hitting this defect:
Apply Patch fails to handle folder addition (100786)
Can you please read over the details in that defect, and if there is anything new with your situation, feel free to add a comment.

Michael Valenta selected this answer as the correct answer
Comments
Geoffrey Clemm commented Sep 11 '17, 3:02 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 Note that the key point here is that using "patch" to perform directory modifications (adding, removing, or renaming directory members) can encounter problems.   Instead, you should always accept completed change sets into your repository workspace, which avoids those problems with the "patch" mechanism.

Your answer

Register or to post your answer.