Re: [papyrus-rt-dev] Plain UML states in RT state machines?

[Peter Cigéhn <peter.cigehn@xxxxxxxxx>]

Hi,

That sounds strange that we explicitly have a unit test checking that it must be allowed to create ordinary UML states in a UML-RT state-machine. If we allowed that by "accident" it would probably be okay, i.e. that the creation of ordinary UML states "slipped through", but that we explicitly have a unit test that checks that is must be allowed feels strange. I guess only Rémi that implemented these tests can answer that the reasoning behind it originally was.

Now when we have all the tooling in place and the manual application of UML-RT stereotypes no longer is needed, I guess there should never be a need for being able to add ordinary UML states to a UML-RT state-machine.

/Peter Cigéhn

On 16 June 2017 at 01:25, Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Team,

We have two tests that assert the successful creation of plain UML states (not UML-RT states with the «RTState» stereotype) in regions in UML-RT state machines (with the «RTStateMachine» stereotype).  Why?  It seems to me contrary to the structural requirements of our state machines, and in fact I have a pending change that fails these two tests:

https://hudson.eclipse.org/papyrus-rt/view/Master%20(Oxygen)/job/Papyrus-RT-Gerrit-Tooling/lastCompletedBuild/testReport/

Thanks,

Christian

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev