Besides the wrong versioning (XW 2.1.5 vs. 2.1.8), that's a reasonable plan. To clarify the possible S2.2 plan as I understand (and prefer) it, it would be a struts2-xwork module within S2 build and release cycle, providing an artifact on which struts2-core depends - could we get a consensus on this?
Dale Newfield schrieb: > Is this an accurate summary? > > struts-2.1.8: still waiting on xwork-2.1.8 > > struts-2.2.x: assuming IP clearance process passes for xwork, fork it > and have it still be a separate jar, but within the struts2 package. > (Probably the only real change would be package names.) > > struts-3.x: merge struts2 and xwork. > > -Dale > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > -- René Gielen IT-Neering.net Saarstrasse 100, 52062 Aachen, Germany Tel: +49-(0)241-4010770 Fax: +49-(0)241-4010771 Cel: +49-(0)177-3194448 http://twitter.com/rgielen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
