Labeled as potential idea - closing - lack of community interest

Sorry, I just checked code. You can actually do;
reportBuilder.toJrXml(outputStream). So that is possible.

There is also support to inherit jrxml document and customize from there. So you can also start from iReport, attach file which will be inherited by DynamicReports and use iDempiere reporting model to finish it up. Same file can be inherited in other similar reports.
I really like the chart support (a ton, including gannt chart, google-chart, maps etc).

Until iDempiere's reporting model is on par with what JasperReport is capable of, that is a disadvantage. Without such facility, when you hit with limitation of the current iDempiere reporting model, you will not be able to export it out as jrxml and do what's not possible using iReport.

After doing another evaluation, am comfortable using DynamicReports(more chart support, more up to date, more code examples, cleaner code).
I don't think not being able to export to jrxml should be a disadvantage.

For pluggability i suggest a reporting engine service interface if that is not already done so implemented engines can be swapped.

I don't know either well enough to make any recommendations. There's one thing I don't like about DynamicReports though - it seems there's no support to create jrxml file.

This needs to be done in a pluggable way so that we can continue to use the existing report engine while beta testing the new engine from this ticket.