Github user pmouawad commented on the issue:
https://github.com/apache/jmeter/pull/300
Maybe we could change how dirty check works which I think was here because
there was no Redo/Undo Management.
Am I wrong to think dirty may be simpler to compute now ?
- Any change (Element addition/removal) on tree makes dirty = TRUE
- Any change in properties of Element makes dirty = TRUE
- When Doing/Undo => dirty = (dirty) ? (undohistory == empty ? TRUE :
FALSE) : TRUE
There is the more complex case of loading a Test plan in version N from a
JMeter in version N+X
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
