0.9.5 Defining an xml list variable in called feature breaks dynamic scenario outline execution

[KostasKgr]

Calling a feature to set up some data to use in a https://github.com/intuit/karate#dynamic-scenario-outline

If the feature that gets called sets up an xml node list variable then this breaks the dynamic scenario invocation, even if that variable is not used at all.

Removing the definition makes everything work, but the definition is needed for the real computation that we are performing.

Example of a definition that can break things:

    # if this definition is in place, then
    #  * If the feature data_use feature is run from intellij, it hangs forever
    #  * If run throught he ExampplesRunner then the following is reported:
    #       java.lang.IllegalAccessError: class com.sun.org.apache.xerces.internal.dom.DocumentImplAccAccess tried to access protected field com.sun.org.apache.xerces.internal.dom.ParentNode.firstChild (com.sun.org.apache.xerces.internal.dom.DocumentImplAccAccess is in unnamed module of loader net.minidev.asm.DynamicClassLoader @389adf1d; com.sun.org.apache.xerces.internal.dom.ParentNode is in module java.xml of loader 'bootstrap')
    # Even though it is not used anywhere in that feature
    # If this def is uncommented, then everything works
    # Assume that this def is useful for the computation though..
    * def nodes = get xml //hello

Code to reproduce this: https://github.com/KostasKgr/karate-issues/blob/xml_list_variable_breaks_dynamic_scenario_calls/src/test/java/examples/data_use.feature

[ptrthomas]

0.9.6 released