Well, it shouldn't be in the struts2-core jar, but it should be in the main Struts project as something like struts2-xwork.jar. There is little value trying to bring it in as a new subproject with its own release cycle.
I really don't understand the resistance to completely getting rid of xwork. This silly division, while noble at the start, has proven to provide no value and heaps of confusion. If someone wants to use xwork by itself, the code will always be at opensymphony, but from all accounts, that only affects like three people. Don On Tue, Aug 11, 2009 at 10:12 AM, Musachy Barroso<musa...@gmail.com> wrote: > I think we have a consensus on bringing XWork in, but we still have to > get to an agreement on where it will actually land (inside core vs its > own artifact), can we get the IP clearing process rolling? > > musachy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
