commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Pyeron" <jpye...@pdinc.us>
Subject RE: Apache-Legacy class adapters was RE: [OGNL] A new release
Date Tue, 31 Dec 2013 02:06:35 GMT
> -----Original Message-----
> From: sebb 
> Sent: Monday, December 30, 2013 17:17
> 
> On 30 December 2013 21:21, Jason Pyeron <jpyeron@pdinc.us> 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.

> 
> >>
> >> 2013/12/30 Jason Pyeron <jpyeron@pdinc.us>
> >>
> >> >
> >> > > -----Original Message-----
> >> > > From: Lukasz Lenart
> >> > > Sent: Monday, December 30, 2013 10:51
> >> > >
> >> > > 2013/12/30 Jason Pyeron <jpyeron@pdinc.us>:
> >> > > > There are a lot of formatting chenges between the version
> >> > > in git and apache svn.
> >> > > > I am still looking for "patches" in git not yet applied to
> >> > > subversion,
> >> > > > do you know of any?
> >> > >
> >> > > All should be already applied or don't affect Apache's version
> >> >
> >> > I was thinking that a set of classes to wrap the 
> org.apache classes 
> >> > should be made for users of the legacy releases until they
> >> are ready
> >> > to update their code bases.
> >> >
> >> > What does anyone else think? Ping Struts folks...
> >
> > jpyeron@black /projects/struts
> > $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test <snip/> 
> > 
> ./struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/ognl/
> > accessor/O bjectProxyPropertyAccessor.java:import ognl.OgnlContext; 
> > <snip/>
> >
> > jpyeron@black /projects/struts
> > $ grep -r 'import ognl' . | grep -v ./.svn/ | grep -v test | wc -l
> > 54
> >
> >> >
> >> > Could those be an apache package? Or must they be from 
> "elsewhere"
> >> > since they will have the non-conformant package names.
> >> >


--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message