expath / xspec

Automatically exported from code.google.com/p/xspec
MIT License
39 stars 43 forks source link

BAT file uses incorrect file locations for XSL #41

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Go through tutorial with batch file
2.
3.

What is the expected output? What do you see instead?

C:\Users\jjmarti1\tutorial>c:\Tools\xspec\bin\xspec.bat escape-for-regex.xspec
Creating Test Stylesheet...
"C:\Users\jjmarti1\tutorial\xspec\escape-for-regex.xsl"
escape-for-regex.xspec
Stylesheet file c:\Tools\xspec\bin\generate-xspec-tests.xsl does not exist

Running Tests...
Stylesheet file C:\Users\jjmarti1\tutorial\xspec\escape-for-regex.xsl does not 
exist

Formatting Report...
Source file C:\Users\jjmarti1\tutorial\xspec\escape-for-regex-result.xml does 
not exist
'"C:\Users\jjmarti1\tutorial\xspec\escape-for-regex-result.html"' is not 
recognized as an internal or external command,
operable program or batch file.
Done.

What version of the product are you using? On what operating system?
0.3.0 on Windows 7 with Saxon 9.1.0.8

Please provide any additional information below.
i changed the lines below to fix the issue:

53: java -cp "%CP%" net.sf.saxon.Transform -o:%TEST_STYLESHEET% -s:%XSPEC% 
-xsl:"%~dp0\..\src\compiler\generate-xspec-tests.xsl"

77: java -cp "%CP%" net.sf.saxon.Transform -o:%HTML% -s:%RESULT% 
-xsl:"%~dp0\..\src\reporter\format-xspec-report.xsl"

Original issue reported on code.google.com by jeff@jeffmartin.com on 28 Oct 2011 at 8:47

GoogleCodeExporter commented 9 years ago
Thank you for the report!  Actually, I cannot find any difference between what 
you wrote and the actual file.  Are you sure you are using the latest source 
(those lines were touched for the last time on Sep. 26)?  You can find it there:

http://code.google.com/p/xspec/source/browse/trunk/bin/xspec.bat

Original comment by fgeorges on 29 Oct 2011 at 1:02

GoogleCodeExporter commented 9 years ago
Hi Jeff,

Could you please confirm your problem has been solved?  This is the last 
opportunity to fix it before the next release ;-)

Original comment by fgeorges on 23 Nov 2011 at 12:19

GoogleCodeExporter commented 9 years ago

Original comment by fgeorges on 23 Nov 2011 at 12:20