A very time-consuming part during migrations is to resolve classloading issues. this is where tattletale is really a great help. Experience tells that the not very experienced users do not know about this option or what the benefit of that might be. Experienced users analysing apps for an EAP migration usually enable it but would obviously benefit from having it on by default.

Enabling it by default most certainly makes sense.

This affects a couple of areas where sub-tasks probably should be created:

• CLI: add an option to disable tattletale, having both options is mutually exclusive and should lead to an error message as early as possible
• Eclipse: pass the enableTattletale option if disableTattletale is not set
• web-console: when the EAP transformation path is selected, the option should be set automatically unless disableTattletale is passed in the advanced options block
• doc: when describing the reports we should mention the article https://access.redhat.com/solutions/800073 and that the tattletale report basically provides the information needed to resolve this issue
• tattletale report: add the standard header we have in all the other reports (if possible), and add some basic explanation in the tooltip

the reason for not simply changing enableTattletale to disableTattletale:
we won't be incompatible (it's a minor version after all) to previous versions and therefore don't break existing pipelines out there.