Issue transforming v16 project in v17

[wkellett]

I recently upgraded from v16 to v17. Ditamaps that transformed cleanly in v16 now give me errors in v17.1. There seem to be a couple of different kinds:

I/O error reported by XML parser processing file:/${dita.input.valfile.url}: \${dita.input.valfile.url} (The system cannot find the file specified) Cause: java.io.FileNotFoundException: \${dita.input.valfile.url} (The system cannot find the file specified)

I/O error reported by XML parser processing file:/C:/DocSource/temp/webhelp/oxygen_dita_temp/Tasks/t_register.dita.indexterms: C:\DocSource\temp\webhelp\oxygen_dita_temp\Tasks\t_register.dita.indexterms (The system cannot find the file specified) Cause: java.io.FileNotFoundException: C:\DocSource\temp\webhelp\oxygen_dita_temp\Tasks\t_register.dita.indexterms (The system cannot find the file specified)

The transformation still runs error-free in v16. Anyone have any insight?

Thanks,
Will K.

[bogdan_cercelaru]

Hello,

A new maintenance build of oXygen 17.1, 2015111718 has been released on November 19th and it contains fixes for this issues.

You can download it from our web site:
Download oXygen XML Editor, Author, or Developer for Windows, Mac, and Linux

The list of bug-fixes can be found here:
Build History of Editor, Developer, and Author Releases

You can follow the release/build RSS feed here:
http://www.oxygenxml.com/rssBuildID.xml

Let us know if you encounter further problems with this new build.

Regards,
Bogdan

[malkaivijetha]

Hi,

I am using the latest 19.1 version and trying to transform a ditamap (using an old version, not sure which) in v19.1.

I am also observing java.io.FileNotFoundException: <path to the map> (The system cannot find the file specified) error.

How do I resolve this error?

Best regards,
Vijetha

[Radu]

Hi Vijetha,

Usually after the transformation fails, at the bottom of Oxygen there is a "DITA OT" console view containing lots of logging details. Pasting in a codeblock that content should give us more details.
The problem might be that your DITA content has a certain DITA DTD specialization which was not installed by you in the DITA Open Toolkit publishing engine bundled with Oxygen 19.1. In the Oxygen Preferences->DITA page you can see the default used DITA Open Toolkit.
https://www.oxygenxml.com/doc/versions/ ... ation.html

Regards,
Radu