-
This job:
2008-12-02 23:12:36 UTC in Oddjob
-
Make the various jobs smarter about naming themselves in the Explorer, so that for example the task will use the toString of it's child, and so that nearly all tasks will use their id (if present) when they have no name.
2008-12-02 03:30:09 UTC in Oddjob
-
Presently is documented as starting a job, and then returning a status based on the success/failure of the act of running the child job.
The only way to "call" a job is to use the task.
I suggest separating and functions, with behaving as presently behaves, while (or perhaps ) returns the result of its child, or an exception if the...
2008-12-02 03:27:03 UTC in Oddjob
-
Presently the property expansion parser for values expects to find strings like
"Header ${ref1} then ${ref2} then ${ref3} footer"
I'd like to be able to run something like:
So nested expansion is required...
2008-12-02 02:52:46 UTC in Oddjob
-
The current behavior of foreach is sequential. With a parallel inner block, some basic parallelism can be added.
I'm in a situation where I have some fixed and some list jobs, and I want to execute all the jobs in parallel.
I'd like to see something like:
...
2008-12-02 02:51:00 UTC in Oddjob
-
My top level oddjob.xml file contains
...
When I open this file in the Oddjob Explorer, the job tree shows a node called "client.xml" (the name of the file).
If I specify name="Client Workstation," shouldn't that take precedence over the filename?.
2008-11-26 22:43:58 UTC in Oddjob
-
My top level oddjob.xml file contains
...
When I open this file in the Oddjob Explorer, the job tree shows a node called "client.xml" (the name of the file).
If I specify name="Client Workstation," shouldn't that take precedence over the filename?.
2008-11-26 21:29:06 UTC in Oddjob
-
According to the manual, and to the behavior I've been able to map, the <if> job returns the "worst case of that of the child and the condition executed."
I believe this is inappropriate, since in my environment setting up an if/then/else does not prevent the system from stopping the job when the <if> guard returns false.
I believe that in the <if> case, the...
2008-11-25 21:08:17 UTC in Oddjob
-
I've added a bug report under the tracker.
If you aren't using the tracker (I'm the second) then let me know and I'll add them here instead.
=Austin.
2008-11-25 19:28:46 UTC in Oddjob
-
Running this job:
name = ${this.name}
Produces this output:
nullname = ${this.name}
Changing the job to:
name = ${this.name}
Produces this (correct) output:
name = ${this.name}
(The "this.name" thing is something I'm still trying to get right.)
I think that if is configured with inner text, it should be smarter...
2008-11-25 19:27:22 UTC in Oddjob
