evernat

@soenkekueper This PR can't be merged: 1. The remarks above are not answered. 2. In particular my last remark above should be noted: this PR breaks the compatibility with iText...

This is caused by an upgrade of hazelcast in bitbucket and so including the fix for this hazelcast issue: https://github.com/hazelcast/hazelcast/issues/20928 The problem is that Bitbucket has Xalan on the classpath...

@astaf89 bitbucket.properties is not for system properties. A system property can be written with `-D` before each in the jvm command line for _start_webapp.sh/.bat : `-Dhazelcast.ignoreXxeProtectionFailures=true`. You can put it...

@hqp468 you can complain to Atlassian about the old processor Xalan being present and active in Bitbucket. With no release since 2014 and probably no security reviews, perhaps the presence...

> I have also tested table-layout: fixed This would give the best wrap result, but it messes up the table layout Indeed. As you have shown in the screenshot and...

@rPraml do you want to replace `word-wrap` yourself or I can do it after merging the PR.

itext-rtf is used only in an almost obsolete part of javamelody (in the javamelody-swing module for the "Desktop" link in the monitoring report, to launch a Swing UI using JavaWebStart...

Given that: - compatibility of javamelody with openpdf is broken in openpdf 1.3.11 (https://github.com/LibrePDF/OpenPDF/issues/274) and it does not seem easy to fix, - if api compatibility between itext 2.1.7 and...

@andreasrosdal No news more than said above. itext 2.1.7 is an optional (not transitive) dependency of javamelody-core. The plan in javamelody is to keep compatibility with itext 2.1.7 since applications...

Hi @okohll @fhuschle and others, Would you be ok if javamelody html pages use a nonce for inline javascripts, instead of externalizing every bits of javascripts ? The nonce would...