Re: [Wrapper-user] Wrapper on CruiseControl doesn't work

[Geoffrey M. <ga...@im...>]

I just avoid relative paths, which I generally think is a good idea 
anyway.  It's good to know that that property is there now, though.  I 
will probably make use of it in the future.  In my current 
implementation, I have hacked the wrapper script to not change the 
working directory, and it works great!

Leif Mortenson wrote:

> Geoffrey,
>
>> I know that Cruise and the wrapper both have some expectations 
>> regarding your current working directory (something I personally 
>> regard as a sin, but that's just my opinion).
>
> I actually agree with you.  But the problem is that the working 
> directory is not consistent
> between running as a console app and running as a service under 
> windows.   When run
> as a service, the working directory is always set to the system32 
> directory.   This means
> that relative paths in an application become pretty much impossible.   
> I always like being
> able to write apps that are deployed as a zip or tar file and then 
> unpackaged anyplace
> and run.   Having a known fixed working directory as a base makes 
> everything just work.
>