From: h_dk (hanneloredk_at_yucom.be)
Date: Thu Aug 04 2005 - 18:38:20 CEST
From: h_dk <hanneloredk@yucom.be> Message-Id: <20050804163820.EB2FD2732454@einstein.suse.de> Date: Thu, 4 Aug 2005 18:38:20 +0200 (CEST) Subject: [taskjuggler] Re: Big project: define html reports in a common file for all projects?
Quote:
> Quote:
> > Hi Chris,
> > Current working directory should be the directory of the calling file, not the directory of the included file.
> >
> > I'll see if upgrading fixes this.
>
>
> That is unlikely. I've just looked at the 2.1.1 code in Report::open():
> ...
Sorry, I didn't mean this as a statement of how it ought to work.
This is what I understand from the following sentence in the manual:
Includes the specified file name as if its contents would be written instead of the include property.
I think I just found the exception that confirms the rule. :)
Quote:
> This is how the include mechanism work in other places. I'm not sure if this is the wisest thing to do, but I hesitate to change this behavior without very good reason as it would break compatibility with older versions.
I'm not a programmer, so I can't give you advice. But you must have guessed that by now. :d
Do you have any idea why the XML report behaves differently from the HTML reports?
Quote:
> But making the report definition a macro and calling it with a parameter for the file name should work in your case. But keep in mind that if it's not an absolute file name, the current working directory of the file where the report is defined will be prepended. In case of a macro this is the macro call, not the macro definition.
I don't quite follow what you mean, but I'll give it a shot.
Either way, I'll let you know what I find. Maybe someone else is interested in this information too.
I appreciate your help very much.
hdk
-- To unsubscribe, email the address listed in the List-Unsubscribe header For additional commands, email: taskjuggler-help@suse.com
This archive was generated by hypermail 2.1.7 : Thu Aug 04 2005 - 18:38:24 CEST