It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,882
×10,914
×1,201
×889
×233
×169
×43
×11

question asked: Aug 09 '16, 7:43 a.m.
question was seen: 2,828 times
last updated: Aug 09 '16, 9:54 a.m.

Related questions

Detection of conflicts before delivery (plain API)

0
Paul Schitz (11●1●2) | asked Aug 09 '16, 7:43 a.m.
edited Aug 09 '16, 9:54 a.m. by David Lafreniere (4.8k●7)
Hi Community,

I am searching for a solution to detect conflicts before deliver them to some other stream/workspace. As it is shown in the eclipse GUI for incoming conflicting changes even before I accept it.
At the moment our delivery fails if there is a change in the target component which is not coming from the source.

We would like to distinguish between a conflicting change and a non conflicting change.

We are using the plain API for our plugin.

Greetings Paul

Be the first one to answer this question!

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.