Are you sure it's not an incompatible change? I thought the discussion was the importing of XWork and getting rid of its branding. That means all of XWork's annotations and packages would be changed to org.apache.struts. I don't believe there is any desire to keep com.opensymphony when this occurs. So my thinking would be this would be an incompatible change. Did I get it wrong?
On Wed, Aug 12, 2009 at 4:45 PM, Wendy Smoak <wsm...@gmail.com> wrote: > On Wed, Aug 12, 2009 at 2:36 PM, Paul Benedict<pbened...@apache.org> > wrote: > > I definitely agree that Struts 3 would be a good candidate to do this > XWork > > migration. It is not an appropriate candidate for 2.1, or 2.2. However, > if > > you like to do a 2.5 (I dislike superficial jumps in versions though), > then > > it might be acceptable in the 2.x branch. > > IMO "Struts 3" would imply a major change in Struts itself, the > possibility of backwards incompatible changes, etc. This isn't... > community aspects aside, it's just moving some code from one svn repo > to another. -Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
