Skip to content

Better handling of missing saxon jar #62

@GoogleCodeExporter

Description

@GoogleCodeExporter
I suggest that in "create-transform-script.ktr" you have a "detect empty 
stream" on the saxon jar and ABORT the process if it isnt found.

See attached as an example!
(Failing to find the saxon jar does seem to be a bit of an ongoing historic 
issue. Problem in PDI 5 is that it's now called saxon-9.<lots of version 
numbers>.jar!

Original issue reported on code.google.com by d.e.kee...@gmail.com on 18 Dec 2013 at 9:47

Attachments:

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions