[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ant-user
Subject:    Re: taskdef defined in project or target
From:       Simon Murcott <simon () flaxx ! net>
Date:       2012-05-17 6:00:42
Message-ID: 021BFA67-C698-407C-B4F1-12234C68BECC () flaxx ! net
[Download RAW message or body]

Generally speaking, one does not care about the memory usage of Ant unless you're \
working with a task that gets repeated a LOT.

Just out of interest, I tried the two scenarios whilst tracing the class loader. Yes \
in the case where the taskef is inside a target, the class gets loaded later. But \
since the initialisation of that task is done regardless, I cannot see this making a \
performance difference or memory difference. That is; unless your task spawns a new \
thread that is constantly churning.


Regards, Simon

On 17/05/2012, at 6:15 AM, "Perrier, Nathan" <nperrier@ptc.com> wrote:

> If I defined a <taskdef> for a custom task at the project-level (outside
> of a macro or target), does that consume a significant amount of memory?
> 
> 
> 
> 
> Would defining <taskdef> in a target and have the targets that use it
> depend on it (thus, the taskdef init would only run when the target
> runs) be a better optimization?
> 
> 
> 
> Thanks,
> 
> -Nathan
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]