> -----Original Message----- > From: Benedikt Ritter > Sent: Tuesday, December 31, 2013 6:05 > > 2013/12/31 Jason Pyeron <[email protected]> > > > > -----Original Message----- > > > From: sebb > > > Sent: Monday, December 30, 2013 17:17 > > > > > > On 30 December 2013 21:21, Jason Pyeron <[email protected]> wrote: > > > >> -----Original Message----- > > > >> From: Benedikt Ritter > > > >> Sent: Monday, December 30, 2013 14:19 > > > >> > > > >> Hello Jason, > > > >> > > > >> sorry, I don't understand what exactly you have in mind. > > > Can you give > > > >> some examples? > > > > > > > > The old OGNL (legacy) releases use the > > > > > > > > "package ognl;" > > > > > > > > declarations, where as the apache releases will use > > > > > > > > "package org.apache.commons.ognl;" > > > > > > > > I would create a set of proxy classes in the old package > > > space which > > > > call the classes in the new space. > > > > > > These will only be required for a small proportion of users, so I > > > suggest they are packaged in a separate jar. > > > > That was always assumed. The question would it be appropiate for an > > Apache release, or should it be released elsewhere. > > > > Our software usually uses the org.apache.commons namespace. > I'm not sure if this is an absolute requirement. To me it > feels like these adapters should be developed and maintained > else where. Thoughts?
The biggest user would be the struts group, that would be a strong reason for it to be an Apache release. A second reason for it to be an Apache release is, "why would a project switch to the OGNL Commons release and then install a non Apache adapter?" That being said, I would use an adaptor from a third party as long as the license worked. <snip/> -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
