FpML Issues Tracker
closed
Block
Always
Coordination
apparry
BrianLynn
Summary
Marc Gratacos confirms that the FpML-5-0 trunk source code is being kept in the branch "FpML-5-0" within Subversion Source Control. This code does not build
C:svnfpmlbranchesFpML-5-0>do-all confirmation > do-all-confirmation.log
a copy of the build log is attached to this issue
Notes:
apparry
02/14/08 8:28 am
Attached copy of image of output folder for confirmation view. No confirmation view schema has been generated, child folders for each asset class have no xml sample files at all
mgratacos
02/14/08 9:17 am
I tested the build system in my machine, at least the copyXml.bat to create the view directories (schemas and examples) and it works in my machine. It works for both, the FpML-5-0 branch and the FpML-5-0-EQD that Andrew created. This indicates me that the problem is his configuration setup in terms of programs installed and classpath.
Three applications are used by the build system:
Java, xalan, and xerces.
this is my classpath set up for these apps:
CLASSPATH = C:Program FilesJavaxerces-2_6_2xercesImpl.jar;C:Program FilesJavaxerces-2_6_2xml-apis.jar;C:Program FilesJavaxerces-2_6_2xercesSamples.jar;C:Program FilesJavaxalan-j_2_6_0bin;
system Variables
JAVA_HOME = C:Javajdk1.5.0_05
PATH = %JAVA_HOME%bin;%SystemRoot%system32;%SystemRoot%;%SystemRoot%System32Wbem;
Obviously, this should have been documented in the README file, which is currently not.
apparry
02/14/08 10:28 am
A more robust solution is to
1. Check for the existence of required environment variables, if these are not set, and we provide the required tool, we should set the environment variable
REM Set the project home to the current directory.
for /f %%i in (“%0”) do set curpath=%%~dpi
set PROJECT_HOME=%curpath%
if not defined JAVA_HOME set JAVA_HOME=%PROJECT_HOME%toolsjdk1.5.0_07
2. Exit with explicit warning if these are not found
If the environment variable is not set, and we cannot set it, the build should abort with an explicit warning
mgratacos
02/19/08 8:53 am
I have updated the env.bat script to print an error message when it can’t find JAVA_HOME, rather than guessing. However, I don’t think that this is Andrew’s problem, as the log I get is different from what Andrew sees when I disable the JAVA_HOME setting.
There appears to be an issue with running the documentation scripts – fails for me with results similar to those in Andrew’s log. However, the xml directory appears to build fine. (In fact, it’s not clear from Andrew’s log what is failing, as there are no error messages at that part.)
I haven’t touched the doc scripts for some time – I think that Irina or maybe Marc was working on them. Perhaps one of you can look at that problem. Also, I do have Oxygen 8.2 installed, but I get a license failure when the script tries to run it. Any ideas what might cause this? However, I can’t duplicate the failure to produce the xml directory.
Regards,
Brian
lyteck
04/04/08 9:11 pm
See “generation_test-lyteck-20080404.doc” (test points to “%JAVA_HOME%)
mgratacos
05/23/08 2:54 pm
Updated the env.bat script to print an error message when it can’t find JAVA_HOME, rather than guessing.