On Nov 27, 2007 12:18 PM, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
> ...i'm strongly against removing the class files from the repository. > from my experience it is very valuable if you can remove the classes > remotely.... Do you need to be able to remove individual class files from the repository? If you can live with a "delete all compiled JSP classes" function, we can probably find another solution, like a utility that can be called from a script to do that. Deleting JSPs is a development/debugging concern, having to call a script (via a URL) to do that is not harder than having to know where and when to delete stuff in the repository. > >...I'm all for using a standard version, and forget about > > having classes in the repository, at least for now. > > i would not care. i reckon the changes are not very complicated and > can easily be reapplied to a new jasper version.... Sure, but it's easy to lose track, and I don't think we have a comprehensive set of automated tests for Jasper. Besides, having our own fork of Jasper bloats Sling and might make people wary of why we have that - all kinds of warnings go off in my programming brain when I see a project doing this. -Bertrand
