https://bz.apache.org/bugzilla/show_bug.cgi?id=65336
--- Comment #13 from Felix Schumacher <[email protected]> --- Created attachment 37887 --> https://bz.apache.org/bugzilla/attachment.cgi?id=37887&action=edit Skip NAME when marking temporar props After further investigations, it seems this is a regression introduced in 2003 by commit 73ac1ed5c3ef9cde27a90e86222ef1f399f78d90. If a JMeterProperty is marked as temporary and it is a MultiProperty, every property of that MultiProperty is marked as temporary in a global Set. This is problematic at least in the case we see here, where one property is the StringProperty with the same key (AbstractTestElement.NAME) and value ("Mfg send MFC"). A simple (but probably not correct) fix would be to skip marking StringProperties with key AbstractTestElement.NAME. That way the plan in this issue works without problems. But we might miss marking properties, that should be cleaned up. I think about adding some kind of scope to the props of MultiProperties, that would allow us to correctly identify the inner props, that are temporary and those, that are not. So, I am glad, that you found a workaround and can hopefully live with it for a while. Changes here should probably not be taken lightly. -- You are receiving this mail because: You are the assignee for the bug.
