> Sure, but you can regard the body of a target as having an
> implicit block.
yes
>
>
>
>
>
>
>
>
> you'll get the following dependencies among the _tasks_:
>
>
> taskb1: -none-
> taskb2: taskb1
> taskb3: taskb1
where is ? Just for annotating?
taskb1 : -none-
I tried that example and that redefines the existence .
You'll just earn a message ...
Jan
---8-<---8-<---8-<---8-<---8-<---8-<---8-<---8-<
Buildfile: build.xml
Trying to override old definition of task echo
[echo] hello
BUILD SUCCESSFUL
---8-<---8-<---
does it work if the name of the presetdef is the same name as the actual
task? I tried it some time ago - but with not much luck.
Also, the examples for presetdef show using it with a different name,
thanks,
Vijay
[EMAIL PROTECTED] wrote:
Jan
-Ursprüngliche Nachric
[EMAIL PROTECTED] wrote:
Usually tasks have to be processed sequentially.
Jan
Sure, but you can regard the body of a target as having an implicit
block.
e.g.
you'll get the following dependencies among the _tasks_:
taska1: -n
> sure. But if you would use and parallel execution
> of targets at the
> same time, you could end up in many more executing threads
> than the system can
> efficiently cope with (memory, CPU, I/O wise). One could try
> to break the target
> parallelism down to the task parallelism on the
>
[EMAIL PROTECTED] wrote:
Thinking a little bit more about the issue, I was wondering
whether it would be
a good idea to integrate the target-level parallelism (as
discussed here) and
the task-level parallelism (i.e.
task) into one beast, as such issues
like output handling and maximum number of
In the formula, the precedence order is the non parallel execution takes
precedence over the parallel execution. It will be necessary to document this
information.
The usage of math notation in the dependency list would seem to be a break from
the ant standard of using tags for everything. Per
Thanks ;)
On Dec 19, 2007 5:05 PM, <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
>
>
> Jan
>
> > -Ursprüngliche Nachricht-
> > Von: Dimitris Mouchritsas [mailto:[EMAIL PROTECTED]
> > Gesendet: Mittwoch, 19. Dezember 2007 15:56
> > An: Ant Users List
> > Betreff: Redefining a task
> >
> Thinking a little bit more about the issue, I was wondering
> whether it would be
> a good idea to integrate the target-level parallelism (as
> discussed here) and
> the task-level parallelism (i.e.
> task) into one beast, as such issues
> like output handling and maximum number of threads
Jan
> -Ursprüngliche Nachricht-
> Von: Dimitris Mouchritsas [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 19. Dezember 2007 15:56
> An: Ant Users List
> Betreff: Redefining a task
>
> Hi everyone, is there a way I can redefine a task to have some default
> attributes
Hi everyone, is there a way I can redefine a task to have some default
attributes?
For example I would like to redefine the javac task to use source="1.4",
target="1.4", debug="true" always
without needing to define them each time I call the task. Any other property
used should be passed to the
ori
The target "depends" attribute already gives all the information you need to be
able to determine which targets can be executed in parallel?
As I mentioned earlier the only road-block at the moment to a totally
transparent mechanism for supporting parallel execution is the dubious implicit
depe
The problem with giving a command line option is that ant is effectively a set
of rules. The rules form a tree and the dependencies give a list of targets
that are to be executed before the current target. There would have to be some
intelligence in the build file that would show ant which tarte
Antform is available on sourceforge. I use it to provide a form for users to
select options during the compile or to get the username and password for the
CM system.
SVN login
This puts a form up for user input. The problem would be that if the parallel
tasking redirects out
hi all
I need to includes a set of jars in WEB-INF/lib.
Actually I want to specify in a .properties file the dirset of my jars
(jars.folders=c:/foo/lib1;c:/foo/lib2;c:/foo/lib3)
and including in the war ant task.
Any help?
Regards
Giovanni
> It may be better to stay away from a grammar that gives the
> rules and use something like:
>
>
>...
>
>
You could provide another executor ;)
In my approach I dont want the user to change the buildfile. Just set
the property on command line.
ant -Dant.executor.class=ParallelEx
> As I understand it, the order is respected under
> simple circumstances, but ultimately the dependency
> graph is calculated such that a dependency is executed
> however early it must be to ensure that every target's
> dependencies precede it.
That is what I thought.
The contract is only that
Chuck Holzwarth wrote:
Perhaps the facility that spawns the targets could manage the screen/buffer
output. This would mean that some facility would have to exist similar to
named pipes in Unix. This way, console output would be directed from the
buffer (or pipe) that had first output while other
18 matches
Mail list logo
