Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Input line too long in a windows system

See original GitHub issue

Expected Behavior

DITA-OT outputs.

Actual Behavior

DITA-OT crashes right away with this error message:

C:\workspace\gradle\dita-transform\build\PI\build\ditaotPI>bin\dita.bat --input=C:\workspace\RDDOC_technical_documentation\DITA\E1007_PI_publi.ditamap --format=pi
La ligne entrée est trop longue.
"C:\workspace\gradle\dita-transform\build\PI\build\ditaotPI\bin\..\config\env.bat" était inattendu.

Which translates to

Input line is too long.
"C:\workspace\gradle\dita-transform\build\PI\build\ditaotPI\bin\..\config\env.bat" was unexpected.

Possible Solution

Use the script closer to C: but it sounds like a regression. Remove the need for env.at by adding the file in the classpath using gradle.

Steps to Reproduce

Launch DITA-OT deep into the filesystem of a windows machine.

Copy of the error message, log file or stack trace

Environment

DITA-OT version: 3.0
Operating system and version: Windows
How did you run DITA-OT? dita command
Transformation type: PDF

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:18 (16 by maintainers)

Top GitHub Comments

1reaction

raducoravucommented, Feb 27, 2018

Using our own class loader in the org.dita.dost.invoker.Main could also be useful if we want to isolate the JAR libraries contributed by a certain transtype. If a certain transtype is invoked, only its jar libraries and the common jar libraries could be loaded + the libraries from extra plugins this particular transtype depends on.

0reactions

thendarioncommented, Jan 21, 2021

or dita.bat could be replaced by dita.ps1 😄 PowerShell has better features than CMD