From: wiz21 (champailler_at_octalis.com)
Date: Fri Aug 19 2005 - 19:56:33 CEST
From: wiz21 <champailler@octalis.com> Message-Id: <20050819175633.B6835273043C@einstein.suse.de> Date: Fri, 19 Aug 2005 19:56:33 +0200 (CEST) Subject: [taskjuggler] Unbreakable tasks
Dear All,
I'm stuck on something that looks simple, but somehow, I can't get around it. I'd like to define an "unbreakable" task. That is, a task that TJ cannot split. Here's why :
vacation "15 Aout" 2005-8-15
resource dev "Developers" {
resource AM "Albert" {}
resource OS "Olivier" {}
flags hidden
}
task AllProjects "All Projects" {
task dvbs2 "Alpha" {
task mpe9d "Create User Mode " {
priority 500
start 2005-8-8
effort 7d
allocate OS
}
task mpe9e "Integrate user mode and web service" {
priority 400
start 2005-8-16
effort 8d
allocate AM,OS
}
}
}
Basically, what happens here is that task mpe9d is split by TJ (2.1.1 btw). I would need TJ to actually start mpe9e with AM only and, as soon as OS is done with mpe9d, OS starts working on mpe9e together with AM. Doing so, both tasks would be completed faster. Since TJ splits, everything ends later.
I've tried plenty of things but no way. It splits. The only solution I see is to split mpe9e to enforce TJ's behaviour, but that's not clean. Having a natural way to say a task can not be split would be nicer... (well, to me at least :))
Any suggestion ?
Thanks,
stF
-- 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 : Fri Aug 19 2005 - 19:56:38 CEST