Closed GoogleCodeExporter closed 9 years ago
I think this happens because of the way I try to detect saxon.
considering also issue 38, it may be a better idea to allow people to specify
saxon explicitly. The detection stuff should remain in place so the interface
to using kettle-cookbook remains the same (i.e. INPUT_DIR, OUTPUT_DIR, and
nothing more), but we could add an optional parameter for saxon which, when
specified, would lift the dependency on running kettle from within its
installation directory.
Original comment by roland.bouman
on 10 Feb 2011 at 4:46
I think the only reason why one couldn't run cookbook from another dir, is that
saxon couldn not be found. In r71, the location of saxon can be explicitly
specified with a SAXON top-level parameter. This parameter has a default that
should make everything work as before if you don't need to fiddle with the dir
from where you run cookbook.
Also see issue #38
Original comment by roland.bouman
on 3 Apr 2011 at 9:41
Original issue reported on code.google.com by
TomBarbe...@googlemail.com
on 22 Dec 2010 at 9:38