Aaron, Ok..I agree...lets filter antlr and Spring for 1.1 and fix the classloaders post 1.1. Do you want to take this one (filter) or should I? If you don't think you can get to it today, I am happy to put in the filters.
Jeff Aaron Mulder wrote: > I don't think the class loaders are fixable for 1.1, whereas the > exclude list is. > > Dain and David J have some ideas for how to fix the classloaders to > separate apps from server internals, which I'd like to do shortly post > 1.1. I think there's a separate JIRA for that. > > Are there other things we know of beyond Spring, Commons Logging, Antlr? > > Thanks, > Aaron > > On 4/24/06, Jeff Genender <[EMAIL PROTECTED]> wrote: >> This goes beyond Spring (and Commons Logging). It affects antlr too >> when using Hibernate. I am sure there are a plethora of other >> jar/packages this will affect too. >> >> Should we take a closer look at our classloaders and figure out why we >> need to do this? >> >> Jeff >> >> Aaron Mulder (JIRA) wrote: >>> Add Spring to default class ignore list >>> --------------------------------------- >>> >>> Key: GERONIMO-1903 >>> URL: http://issues.apache.org/jira/browse/GERONIMO-1903 >>> Project: Geronimo >>> Type: Bug >>> Security: public (Regular issues) >>> Components: web >>> Versions: 1.1 >>> Reporter: Aaron Mulder >>> Priority: Blocker >>> Fix For: 1.1 >>> >>> >>> It's pretty dumb that anyone deploying a Spring app has to manually add >>> classloader excludes to their Geronimo plan. We should support Spring out >>> of the box. Which until we improve our CL structure means that we need to >>> add default excludes for Spring itself plus potentially any libraries >>> commonly shared between Spring/Acegi/etc. and Geronimo. >>> >>> I guess we need a test app for this. >>>
