It's very application specific, but it's "Object 'test' does not have a field named 'test1' c:/path/to/importTest", suggesting that it's not inferring the value of an 'I' parameter which should indicate a directory within which to search for a file called 'test' which included some trivial code that informs my test.
I tried substituting a batch file (this is on windows) with the single line in it, and get the same discrepency in behavior - the batch file works fine when invoked from the shell, but fails when called with sh. This suggest to me that it's nothing to do with clojure's processing of the arguments. Maybe this has something to do with how the environment is represented? I tried printing the value of sh/*sh-env* during my call, and it was 'nil', but in order to call the app at all, it must have some knowledge of the PATH. Does (null *sh-env*) then mean 'no changes to the default environment'? On Wednesday, July 11, 2012 3:53:48 PM UTC-7, Michael Klishin wrote: > > Eric in San Diego: > > > That's why I'm hoping there is some way I can compare and contrast the > actual inputs that get fed into the app. > > At least post your exception message. > > MK > > mich...@defprotocol.org > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
