removing "use case"
"use case aspect" has been already removed from the menu of Requirements (from registerPrimaryPrototype) (see, how it was in "use case aspect.jpg").
Due to code freeze, there is no possibility to remove the respective GUI now.
It should be done in next release.
#7 Updated by Anonymous over 2 years ago
There is a package org.fortiss.af3.mira.model.usecase.impl which is the one that I think is obsolete.
However it is not marked as deprecated because some generated code is referring to it.
We might need to remove "usecase" from the mira model, see that nothing is broken, and then get rid of this classes.
#9 Updated by Anonymous over 2 years ago
- Status changed from Closed to In Progress
- Target version changed from AF4 Requirements to AF3 2.13 RC2 (Tested, Bug-free)
@Filip: I re-open this issue because Johannes explained me yesterday that this is not the correct way of doing this (I was having a similar problem after renaming testing.method.random).
The use case is part of the meta model and therefore present in every old project that was using it (as it was the case with simple traffic light).
If now someone tries to load an old project, it will not and the will go a null pointer in the console.
What it needs to be done is to write a migrator. Here there is a small explanation.
#10 Updated by Simon Barner over 2 years ago
- Target version changed from AF3 2.13 RC2 (Tested, Bug-free) to AF3 2.14 RC1 (Feature Freeze)
The metamodel has been restored (classes marked as deprecated), and the migrator is in place.
Moving the ticket to AF2.13 post release, so the migrator and the use case metamodel can be removed for good.