probably only if one uses the embedding to actually build the project. Which I don't do in netbeans, only use it to load the MavenProject instance and resolve dependencies, effectively using the extensions only to resolve ArtifactHandlers I think. haven't yet observed a problem with extensions classloading in my scenarios, I'm mostly fighting with stuff like long living MavenProject instances dragging clouds of Model objects via ProjectBuildingRequest.. killing that gave me a lot of breathing space as far as heap memory goes..
Milos On Thu, Nov 29, 2012 at 9:23 AM, Kristian Rosenvold <[email protected]> wrote: > I just deployed classworlds 2.4.1 which uses the jdk7 "close" method > on the classloader (if available) in the classworlds "dispose" method. > It looks to me like this radically changes permgen/memory usage on > embedded scenarios (some of you "embedded" guys might want to give > this a spin to quantify the exact results); my observations are only > from yourkit but they seem to be fairly substantial. > > I "observed" that the extension classloaders are not being > disposed/closed; what is their intended scope ? (Are they supposed to > be disposed?) > > Kristian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
