ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 42742] - big Ant/Ivy builds run out of permanent memory. Classloader leaks?
Date Wed, 19 Sep 2007 09:42:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42742>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42742





------- Additional Comments From peterreilly@apache.org  2007-09-19 02:42 -------
One way ant could help would be not to use a new classloader
in the case with the path for the new task/type definition is
the same as the current definition. At the moment this
is treated as a "similar" definition, which overrides the
current definition with a new classloader, but does not
inform the world:

  project.log("Trying to override old definition of "
          + (isTask ? "task " : "datatype ") + name, (def.similarDefinition(old,
           project)) ? Project.MSG_VERBOSE : Project.MSG_WARN);

The reason for using a new classloader is that some of the jars, directories
may have changed since the last <typedef/>, however I do not think
that this happens for real (and for windows changing the jar while is
is used in a classloader is not easy).

However, this will not solve the general problem as the master project
may not have loaded the tasks/types.
 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message