Project

General

Profile

Feature #1904

Feature #1901: modify the conversion process to properly run on Windows

update the chemtutor build.xml to handle conversion on Windows

Added by Greg Shah over 11 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
8.00 h
billable:
No
vendor_id:
GCD
version:

Related issues

Related to Conversion Tools - Feature #1905: why does P2J_HOME have to be explicitly set for running the conversion on Windows and not in Linux? fix this New
Related to Conversion Tools - Feature #1906: find a way to programmatically force file.encoding="UTF-8" for the entire JVM when running on Windows, without needing to specify it on the command line or in some configuration file New

History

#1 Updated by Greg Shah over 11 years ago

  • Estimated time changed from 4.00 to 8.00

Please see #1565 for details, but to summarize:

1. P2J_HOME had to be explicitly set via java -DP2J_HOME=.
2. The file encoding has to be explicitly set via java -Dfile.encoding="UTF-8"
3. Make sure logging for the build is implemented. We want output to both the console and to a conversion log file. In Linux we usually do this with "tee". Can we support this feature via ant in both Linux and Windows?
4. Any other changes (as shown in the .cmd scripts in #1565) needed to get conversion to run.

Don't forget to document all of these things in the Conversion Handbook.

#2 Updated by Greg Shah over 11 years ago

  • Parent task set to #1901

#3 Updated by Greg Shah over 7 years ago

  • Target version deleted (24)

Also available in: Atom PDF