From: Dick Kniep (dick.kniep_at_lindix.nl)
Date: Wed Mar 17 2004 - 18:04:34 CET
From: Dick Kniep <dick.kniep@lindix.nl> Date: Wed, 17 Mar 2004 18:04:34 +0100 Message-Id: <200403171804.34387.dick.kniep@lindix.nl> Subject: [taskjuggler-devel] priority and conflicts
Hi list,
The python frontend is to be published shortly and is working OK for me. But I
do have some questions on the use of taskjuggler with generated tjp files.
As you may have experienced yourself, when you define a tjp spec file the
results are not always as you would expect at first sight. Sometimes
taskjuggler schedules a task outside the project boundaries, which results in
errors. By adding priority to those tasks the problem goes away. I have added
some code in the frontend that recognizes this situation, and returns the
offending tasks to the calling application. In the calling application I
increase the priority of the task, and rerun taskjuggler.
Off course, I consider this an ugly hack. Included is a spec file that
demonstrates the problem. The file called problem.tjp gets a scheduling error
for the task, while the other one doesn't. (There are still some other
errors, but they do not bother me so much, because they are an inherent
result of a data problem in my database)
Now if someone knows a better solution (or I made a silly mistake in the
generation of the tjp file) I would be very happy as I expect the system to
contain many thousands of tasks and hundreds of reources in the future (so
the spec file will become very large), which will inevitably lead to
performance problems.
-- Cheers, D.J. Kniep Lindix BV Tel. 036-5215580
-- To unsubscribe, email: taskjuggler-devel-unsubscribe@suse.com For additional commands, email: taskjuggler-devel-help@suse.com
This archive was generated by hypermail 2.1.7 : Thu Mar 18 2004 - 13:23:23 CET