Migrating Gatling java from v3.9.5 to v3.10.5 results in a compilation error about gatling HOT 5 CLOSED

Please explain what you’re doing and why you feel this is a bug.

Reminder:
• you’re only supposed to explicitly pull the highcharts module, as demoed in our documentation and samples. The other ones must be pulled transitively.
• you’re supposed to use wildcards imports like documented.

Any other configuration is your decision and hence your responsibility.

from gatling.

@slandelle Apologies for not providing more context to the problem. Let me add more context:

We are using the below code to log the human-readable assertion text with printable() and values() methods, mentioned in my issue description, during the performance test run:

public static String toString(Assertion assertion) {
  var s = assertion.asScala();
  return s.path().printable() + ": "
    + s.target().printable() + " "
    + s.condition().printable() + " "
    + s.condition().values().mkString(", ");
}

The above code worked perfectly with version 3.9.5, but when I tried to migrate to version 3.10.5, the compiler could not find the printable() and values() methods.

When I analyzed the dependency tree, I found out that the issue happened because of the dependency change in version 3.10.5

Regarding your comments, I am adding my response inline:

• "you’re only supposed to explicitly pull the highcharts module, as demoed in our documentation and samples. The other ones must be pulled transitively."
  Yes this is what we are doing
• "you’re supposed to use wildcards imports like documented."
  The issue persists for both wildcard import and specific import

from gatling.

Hello,

Thanks, now I understand your issue.

Sorry, but you are not supposed to use these methods: asScala, printable(), etc. These are internals.
Only the types and methods documented in the official online documentation should be used by the end users.

from gatling.

@slandelle I see. Thanks for the clarification.

In that case, would you suggest an alternative for me to print the human-readable assertion text?

from gatling.

Sorry but this is not a feature we provide.
The assertions are meant to be generated internally by Gatling and printed in one of the official Gatling outputs (console, HTML reports, Gatling Enterprise).
I recommend that you stick to these.

from gatling.