Page 1 of 1

DITA Map Metrics Report transform fails

Posted: Mon May 11, 2020 12:47 pm
by Anne
Hi,

I tried running the DITA Map Metrics Report transform on the main map of my doc set, and got the following error:

System ID: <path to my .ditamap>
Scenario: DITA Map Metrics Report
Input file: <path to my .ditamap>
Document type: DITA Map
Engine name: DITA-OT
Severity: fatal
Description: Transformation failed. C:\Program Files\Oxygen XML Editor 22\frameworks\dita\DITA-OT3.x\plugins\com.oxygenxml.dita.metrics.report\build_metrics.xml:5: input file <path to my maps dir>\${args.input} does not exist

Tried to run it on a map in the Oxygen sample project with the same result.

What seems to be missing?

Thanks IA
Anne

Re: DITA Map Metrics Report transform fails

Posted: Tue May 12, 2020 8:05 am
by Radu
Hi Anne,

What Oxygen version are you using? Did you make any changes to the DITA-OT3.x publishing engine folder bundled with Oxygen?
If you open a DITA Map in the DITA Maps Manager view and use the "Configure Transformation Scenarios" toolbar button there is a predefined DITA Map Metrics Report transformation scenario there and you can apply it. Is it similar to the way in which you are running the transformation?
After the transformation fails, there should be an extra "DITA OT" console tab view at the bottom of Oxygen with lots of logging information obtained from the DITA OT process. Can you maybe copy all the content inside that DITA OT tab view to the forum as a reply? Or send us an email with the contents of that DITA OT tab view attached to it? Maybe it will give us more information about why this fails on your side.

Regards,
Radu

Re: DITA Map Metrics Report transform fails

Posted: Tue May 12, 2020 9:50 am
by Anne
Hi Radu,

Yes, that's how I run the transform.
The log file is a bit long to post here, so I'd rather send it by email, just tell me the address.

Thanks,
Anne

Re: DITA Map Metrics Report transform fails

Posted: Tue May 12, 2020 9:58 am
by Radu
Hi,

You can send an email to "support@oxygenxml.com". In the email body maybe you can add a link to this forum thread in order for us to better identify the situation.

Regards,
Radu