The jibx compiler has an option to do a sanity check of the modified classes after jibx compilation - using the ant task, this is enabled by setting the parameter "load='true'". Recently, investigating some abnormally high build times and build memory requirements, I determined that disabling load='true' cuts our build time by a third and reduces the build-time memory requirement by more than half... with load='true' set, we were actually running into OutOfMemory conditions which cleared up when the parameter was set to false, which leads me to suspect a memory leak.
All of this was done using beta3c; I'm trying to verify this with rc0 to see if it's still an issue or not, but I thought it might be worth raising here to see if this is a known issue that anybody else might be looking into/experiencing. ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_idt12&alloc_id344&op=click _______________________________________________ jibx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jibx-users
