I think it's about the same problem than described here : http://jasperforge.org/sf/go/artf1593?nav=1
I'm using Customizer class for my charts to overcome iReports limits. Problem is that if I recompile this Customizer class, I need to restart iReport to reload my external class and that's really a waste of time.
Can it be helped ? Maybe it's one of the program limits ; I guess it's not ressource-costless to reload the classes but why not reload if changes are detected in the classpath ? Maybe reload only files which changed ?
I would like to say too that since I'm using iReport, I have got this problem when changing something in classpath. I thought jacques koorts artifact (link at the beginning) would catch your attention... please reconsider this bug !