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:31:51 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:31 -------
1) no
2) I raised the issue on the Ivy dev mailing list.
 >It sounds like Ivy needs to listen for build completion and purge its state when
 >a  build finishes
Yes I tried that (listening for subproject build ending and clearing
IvyContext) and it seems to work (I have problems with the ant cc for
smartfrog - 1) the system tests fail and 2) ivy 2.0.0 trunk sees
problems with the dependences (missing javadoc artifacts))

However there is another problem with the implementation of IvyContext
which I raised on the Ivy mailing list. The way it is implemented
means that sub-projects will wipe the context of master projects
(if the same classloader is used for ivy in the sub-projects).


-- 
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