Integrator fails using DITA-OT 2.3.1

shudson310
Posts: 149
Joined: Sat Feb 26, 2005 12:09 am
Location: USA
Contact:

Integrator fails using DITA-OT 2.3.1

Post by shudson310 » Thu Jul 07, 2016 5:46 pm

I cannot integrate my DITA-OT plugins using the latest DITA-OT release (v2.3.1):
Executing:
"c:\program files\oxygen xml editor 17\jre/bin/java" "-Dhttp.proxySet=true" "-Dhttp.proxyHost=ipv4.169.143.0.105.webdefence.global.blackspider.com" "-Dhttps.proxyHost=ipv4.169.143.0.105.webdefence.global.blackspider.com" "-Dhttp.proxyPort=80" "-Dhttps.proxyPort=80" -Xmx256m -classpath "C:\Program Files\Oxygen XML Editor 17\tools\ant/lib/ant-launcher.jar" "-Dant.home=C:\Program Files\Oxygen XML Editor 17\tools\ant" org.apache.tools.ant.launch.Launcher -lib "C:\SVN\ptd\content\trunk\dita-ot-2.3.1\lib\commons-io.jar" -lib "C:\Program Files\Oxygen XML Editor 17\frameworks\dita\DITA-OT2.x\lib\commons-io-2.4.jar" -f "C:\SVN\ptd\content\trunk\dita-ot-2.3.1/integrator.xml" "-Dstrict=true" "-Dwebhelp.trial.license=no"

Buildfile: C:\SVN\ptd\content\trunk\dita-ot-2.3.1\integrator.xml

strict:

integrate:

BUILD FAILED
C:\SVN\ptd\content\trunk\dita-ot-2.3.1\integrator.xml:66: The following error occurred while executing this line:
C:\SVN\ptd\content\trunk\dita-ot-2.3.1\integrator.xml:44: java.lang.NoClassDefFoundError: com/google/common/collect/ImmutableSet
I'm running into problems with v2.2.5 where keys are not resolving. With v2.2.5, I get:
[DOTX031E]: The file ../contentmodels/gl_title.dita is not available to resolve link information.
Thought I'd try v2.3 to see if it fixed key resolution.

I have a map with these definitions:

Code: Select all

<!-- Reference to all document variables. -->
<mapref format="ditamap" href="m_variables.ditamap" processing-role="resource-only" scope="local"/>
<mapref format="ditamap" href="m_acronyms.ditamap" processing-role="resource-only" scope="local"/>
<mapref format="ditamap" href="m_elements.ditamap" processing-role="resource-only" scope="local" />

In m_elements.ditamap, I have:

Code: Select all

 <glossref print="yes" keys="gl_title" href="./contentmodels/gl_title.dita"/>
Which appears to be one of the key(s) that is not getting resolved.
Scott Hudson
Staff Content Engineer
Site: docs.servicenow.com

shudson310
Posts: 149
Joined: Sat Feb 26, 2005 12:09 am
Location: USA
Contact:

Re: Integrator fails using DITA-OT 2.3.1

Post by shudson310 » Thu Jul 07, 2016 6:42 pm

I had to explicitly add

Code: Select all

${configured.ditaot.dir.url}/lib/guava-19.0.jar
to the libraries in the ant scenario.
Scott Hudson
Staff Content Engineer
Site: docs.servicenow.com

shudson310
Posts: 149
Joined: Sat Feb 26, 2005 12:09 am
Location: USA
Contact:

Re: Integrator fails using DITA-OT 2.3.1

Post by shudson310 » Thu Jul 07, 2016 6:45 pm

I still get an error about not being able to resolve the link information, but it actually appears to have worked. Not sure why the false error, but v2.3.1 does appear to resolve the keys better than v.2.2.5.
Scott Hudson
Staff Content Engineer
Site: docs.servicenow.com

Radu
Posts: 7540
Joined: Fri Jul 09, 2004 5:18 pm

Re: Integrator fails using DITA-OT 2.3.1

Post by Radu » Fri Jul 08, 2016 7:53 am

Hi Scott,

I answered you here:

https://github.com/dita-ot/dita-ot/issues/2426

Maybe you can close that issue when you have the time.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

Radu
Posts: 7540
Joined: Fri Jul 09, 2004 5:18 pm

Re: Integrator fails using DITA-OT 2.3.1

Post by Radu » Fri Jul 08, 2016 7:54 am

About the keyref problem, if you can put together a sample DITA project we can look into it. Usually problems occur when you use chunking or when you refer to resources outside of the folder where the main DITA Map is located.

Regards,
Radu
Radu Coravu
<oXygen/> XML Editor
http://www.oxygenxml.com

shudson310
Posts: 149
Joined: Sat Feb 26, 2005 12:09 am
Location: USA
Contact:

Re: Integrator fails using DITA-OT 2.3.1

Post by shudson310 » Fri Jul 08, 2016 5:11 pm

It's definitely related to common glossary terms that are in a folder at a higher level than the bookmap. This is the only way to share common glossary terms across multiple product manuals. We use fix.external.refs.com.oxygenxml="true" to address this, but still get the errors in the log.
Scott Hudson
Staff Content Engineer
Site: docs.servicenow.com

Post Reply