Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cant assume Saxon script found is from EXPath #49

Open
GoogleCodeExporter opened this issue Jun 8, 2015 · 4 comments
Open

Cant assume Saxon script found is from EXPath #49

GoogleCodeExporter opened this issue Jun 8, 2015 · 4 comments
Labels
auto-migrated Milestone-Release0.4 Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

What steps will reproduce the problem?
1.Run the 0.4.0rc1 on Fedora Core 16

What do you see instead?
Creating Test Stylesheet...
Command line option -x requires a value


What version of the product are you using? On what operating system?
0.4.0rc1 on Fedora Core 16 AMD64

Please provide any additional information below.
The problem is at line 56 of the xspec.sh script. You cannot assume that if you 
find an executable called 'saxon' then it is from the EXPath project. In the 
case of Fedora 16, there is a 'saxon' executable installed in /usr/bin which is 
Saxon8 and is installed by YUM as a system package.

Cheers Adam.

Original issue reported on code.google.com by [email protected] on 14 May 2012 at 11:25
innovimax pushed a commit to innovimax/xspec that referenced this issue Jan 17, 2017
remove -j option in tests expath#39 (expath#49)
1a92c65 
* remove -j option in tests for shell and batch scripts expath#39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-Release0.4 Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter