From: Joachim Werner (joe_at_suse.de)
Date: Thu Nov 11 2004 - 11:36:11 CET
Message-ID: <4193409B.50502@suse.de> Date: Thu, 11 Nov 2004 11:36:11 +0100 From: Joachim Werner <joe@suse.de> Subject: Re: [taskjuggler] Nested tasks
Silvia Franceschi schrieb:
> I will attach this part of the code
> *****************************************************************************
> task start "Start of plan" {
> start 2004-11-01
> milestone
> flags hidden
> }
>
> task software "Software development" {
> depends !start
> priority 1000
>
> task gis "GIS development" {
> effort 1d
> allocate moovida, piso
> }
>
> task database "Database coupling" {
> effort 1d
> allocate moovida
> }
>
> task horton "Additional geomorphological tools" {
> effort 1d
> allocate cozzini
> }
>
> task peakflow "Hydrological tool" {
> effort 2d
> allocate piso
> }
>
> }
I've tried a similar example and don't see an issue. Of course those
tasks won't start all at the same time because in your example you have
moovida and piso working on GIS, so if you don't specify that they
shouldn't work full time on this their other tasks won't start.
In most of those cases you just have to be more specific if TaskJuggler
does the "wrong" thing. E.g. if you want that both moovida and piso
really share the work on GIS,
task gis "GIS development" {
effort 1d
allocate moovida {mandatory},
piso {mandatory}
}
would make sure that they only start working if both are available, and
always work together.
Cheers
Joachim
-- Joachim Werner SUSE RD-TPM -- 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 Nov 11 2004 - 11:36:15 CET