RE: [External] [xdi] xdi-spec and DITA and build.bat

["Barnhill, William [USA]" <barnhill_william@bah.com>]

Re-ran myself, and also get those warnings. They are a pain, but don't prevent creation of the document from the ditamap and dita topics, so freeze seems likely to be something else.  I don't have /./ in path, but if it works with %cd% then that's not the issue. Not sure what is.  Maybe out of memory issue.  Probably need to add echo in front of ant command in script, then re-run check command, and then run ant command directly using the stuff below from the OpenDITA toolkit project web site (http://dita-ot.sourceforge.net/1.5.4/userguide.html).   When you do that use the ant in ./DITA-OT1.5.4-ez/tools/ant).  There's also a new version 1.6 of DITA out that might fix it (or break it further), and the ant version is 1.7.1.  Current Ant now is 1.8.4, but I believe I tried an earlier 1.8.x and it broke the build.  Might be worth trying again.

Analyze messages in the log file

A log file in plain text format is generated in the log directory, which has a name combined with both input file name and transform type. You can open it and find more detailed information, which are helpful for solving problems. You can use the same way introduced above to analyze the messages and solve the problems.

The log directory can be specified by:

• using Ant, with argument -logfile=log-file
• using command-line tool, the parameter /logdir:log-dir.

Turn on debug mode

Under debug mode, diagnostic information, such as: environment variables, stack trace, will be logged into the log file. These information can help the user or developer to go deep into the problems and find the root cause.

By default, the debug mode is disabled. To turn on the debug mode on, you need to follow the usage below:

• Append -v and -Dargs.debug=yes in Ant command.
• Append /d or /debug in command-line tool.

Kind regards,

 

Bill Barnhill

Booz Allen Hamilton - Belcamp,MD

barnhill_william@bah.com

Cell: 1-443-924-0824

Desk: 1-443-861-9102

---

From: markus.sabadello@gmail.com [markus.sabadello@gmail.com] on behalf of Markus Sabadello [markus.sabadello@xdi.org]
Sent: Friday, November 23, 2012 8:23 AM
To: Barnhill, William [USA]
Cc: OASIS - XDI TC
Subject: Re: [External] [xdi] xdi-spec and DITA and build.bat

Made the change, but it makes no difference. Whether I use %cd% or . or nothing, it's always the same path.

I think the problem must be elsewhere.

BTW the errors (or rather warnings) are the same under Linux, only that it doesn't freeze there.

Markus

On Fri, Nov 23, 2012 at 12:43 PM, Barnhill, William [USA] <barnhill_william@bah.com> wrote:

Thanks Markus. I just took a look at setenv.bat and build.bat.  The only thing that pops to mind is the use of . to replace pwd.  Especially with this in the error: xdi-spec\.\DITA-OT. 

Instead, putting %cd% in every place that `pwd` is in the shell script might work.  If that didn't work, I'd try what you have now, without .\ at the front for the DITA DIR.

Kind regards,

 

Bill Barnhill

Booz Allen Hamilton - Belcamp,MD

barnhill_william@bah.com

Cell: 1-443-924-0824

Desk: 1-443-861-9102

---

From: xdi@lists.oasis-open.org [xdi@lists.oasis-open.org] on behalf of Markus Sabadello [markus.sabadello@xdi.org]
Sent: Thursday, November 22, 2012 5:41 PM
To: OASIS - XDI TC
Subject: [External] [xdi] xdi-spec and DITA and build.bat

I just had a quick Skype chat with Bill about writing the XDI spec.

You will recall that Bill had set up a Github repository for this, as well as a build environment to create the spec using the DITA tool:

https://github.com/OASIS-XDI-Technical-Committee/xdi-spec

Bill's original idea (feel free to correct me) was that after a proposal is approved, it would immediately be integrated with the draft spec, which grows as a result of this process.

I now feel that this makes total sense, but that we should get a small number of additional, fundamental proposals done first (e.g. the core graph model), before we begin transferring that initial set of approved proposals into the draft spec.

I worked on porting the build.sh script on Github from Linux to Windows, the result is a setenv.bat and build.bat file for building the spec.

Unfortunately, they don't work for some reason. I remember having tried this already a few months ago, without success.

I now get to the point where the DITA program executes, but it only outputs the following and then freezes:

Failed to read supported DITA topic extensions from configuration, using defaults.

Failed to read supported DITA map extensions from configuration, using defaults.

Failed to read supported image extensions from configuration, using defaults.

Failed to read supported HTML extensions from configuration, using defaults.

Failed to read supported resource file extensions from configuration, using defaults.

Buildfile: C:\Users\markus\workspace-xdi\xdi-spec\.\DITA-OT1.5.4-ez\build.xml

Not quite sure how to make it work. Myself I can also work with the Linux version, but I thought it would be nice to have it on Windows as well.

Markus