Felix Meschberger wrote: > Am Dienstag, den 27.11.2007, 12:18 +0100 schrieb Tobias Bocanegra: >>> In order to get rid of the patched copy of Jasper 5.5, I propose to not >>> store JSP transpilations and compilations in the repository anymore and >>> fall back to using standard Jasper. >> what about compiling in temp files and moving them afterwards in the >> repository ? >> 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. > > This is one of the problems we are considering to find a solution. But > as there are workarounds, this possibility by itself does not warrant > keeping the classes in the repository. > > Of course copying the classes to the repository after the fact, would be > one way to go. In fact inspecting the class files is far more valuable > than just being able to remove the class files. > >>>> ... - Cannot easily upgrade to more recent Jasper versions... >>> That's the killer IMO, the purpose of Sling is not to maintain a JSP >>> compiler, so 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. > > Not really, unfortunately. In addition, no matter how simple the patches > are, keeping up is simply not worth the effort with regard to required > work time and stability (been there, done that :-) ) > Can't we just provide a patch to the Jasper project, so the changes will be included in the next release?
Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
