Error: 'void net.sf.saxon.Configuration.setResourceResolver(net.sf.saxon.lib.ResourceResolver)'

[Debbie Redmond]

Hi,

  I updated DITA to 4.1.2, when I try to run

dita install

I get the error:
Error: 'void net.sf.saxon.Configuration.setResourceResolver(net.sf.saxon.lib.ResourceResolver)'

I've been fiddling for awhlie but not sure how to resolve the issue.

Any clues would be appreciated.

Thanks
Debbie

[Radu Coravu]

Hi Debbie,

How did you update to DITA OT 4.1.2? Did you attempt to merge an older DITA OT's libraries and plugins with the newer one's?

Can you double check that in the DITA OT "lib" folder you do not have duplicate Saxon libraries belonging to different Saxon library versions?

Regards,

Radu

--
You received this message because you are subscribed to the Google Groups "DITA-OT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dita-ot-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/dita-ot-users/1af06dec-8939-409b-b57d-f06e5c7a8b2dn%40googlegroups.com.

[Debbie Redmond]

Many thanks, yes I copied over top. I just removed the lib folder, deleted all plugins that have new versions (preserving my own), and then copied from the 4.1.2 package.  I can now run dita -install and it installs my plugin without issue but when I generate my pdf, I get:

C:\Users\dredmond\Documents\nymi_docs\docs\dita\bin>dita -p webapi_ios_only.xml
     [copy] Warning: C:\Users\dredmond\Documents\nymi_docs\dita\plugins\com.nymi.print.pdf\cfg does not exist.

The folder does exist, and the pdf is created without the customizations in my plugin.

Debbie

[Debbie Redmond]

Hi,

 I've resolved the error.  I overwrote the build.xml file dita directory.  I added the <target name=...> entry for my plugin into the file and all is now well.

Thanks

Debbie

On Friday, November 24, 2023 at 12:22:32 AM UTC-5 raduc...@gmail.com wrote:

[Radu Coravu]

Hi Debbie,

You should have probably run the "dita --install" after adding your plugins instead of making direct changes to the build.xml.

Usually a DITA OT update where the only changes are properly incorporated in custom added plugins would go like this:

Copy my custom plugins from the old DITA OT to the new DITA OT. 

Run the "dita --install" in the new DITA OT.

Regards,

Radu

To view this discussion on the web, visit https://groups.google.com/d/msgid/dita-ot-users/279976bf-a133-4316-8059-a56790ca4323n%40googlegroups.com.

[Debbie Redmond]

Hi Radu,

  I did run dita -install but it didn't update the build.xml file.

Here is what I did:

1. Deleted most plugins from the dita\plugins directory except my custom one and couple of other ones that weren't in the  new dita package. 
2. Deleted the dita\lib directory
3. Copied plugins and lib directory from Dita 4.1.2
4. Ran dita -install
When I create the pdf I get the warning:
c:\dita\bin>dita -p webapi_ios_only.xml
     [copy] Warning: C:\dita\plugins\com.nymi.print.pdf\cfg does not exist.
The pdf generated but not with my customizations.
I compared the C:\dita\build.xml file in the new dita package with the C:\dita\build.xml in  my dita 3.7.3 backup and noticed that it was missing these lines: 

<target name="dita2custpdf.init">
    <property name="customization.dir" location="${dita.dir}${file.separator}plugins${file.separator}myplugin${file.separator}cfg"/>
    <property name="pdf2.i18n.skip" value="true"/>  
  </target>
  <target name="dita2custpdf" depends="dita2custpdf.init, dita2pdf2"/> 

When I manually added them and saved the build.xml file, my customizations were applied when I ran the dita -p command.

Maybe the way that I set up my build environment is not standard?

Debbie