It's all about the answers!

Ask a question

Accepting changes from multiple flow targets using Ant Tasks


Amos Baker (656) | asked May 14 '14, 3:54 p.m.
edited May 14 '14, 3:55 p.m.
Hi,

Trying to accept changes from multiple flow targets in order to create a conflict.  We are trying to accomplish this through JBE as well as using the teamAccept task definition provided with RTC, but we are getting the following error over and over again:

com.ibm.team.repository.common.TeamRepositoryException: Component XYZ is accepting changes from multiple flow targets
at com.ibm.team.build.internal.scm.SourceControlUtility.acceptAllIncoming(SourceControlUtility.java:1066)
at com.ibm.team.build.internal.scm.SourceControlUtility.acceptAllIncoming(SourceControlUtility.java:935)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.performAccept(JazzScmPreBuildParticipant.java:359)
at com.ibm.team.build.internal.engine.JazzScmPreBuildParticipant.preBuild(JazzScmPreBuildParticipant.java:176)
at com.ibm.team.build.internal.engine.BuildLoop.invokePreBuildParticipants(BuildLoop.java:933)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:739)
at java.lang.Thread.run(Thread.java:769) 

We are wondering if it is possible for JBE/RTC Ant Tasks to accept changes from multiple streams without having to complain about it.

Thank you.

One answer



permanent link
sam detweiler (12.5k6195201) | answered May 14 '14, 4:29 p.m.
 >We are wondering if it is possible for JBE/RTC Ant Tasks to accept changes from multiple streams without having to complain about it. 

I don't think so.. cause how should it do the process? which stream first? what to do about conflicts?

altho I have a question here too..  just cause I have multiple flow targets defined, why is it using more than one?
only one can be current at a time. 


Comments
Amos Baker commented May 15 '14, 11:00 a.m.

We don't mind creating a conflict -- this is what we actually want to occur.

Your answer


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.