On Mon, Aug 10, 2009 at 9:57 PM, Musachy Barroso <musa...@gmail.com> wrote:
> Although I agree in theory, looking at it from a practical point of > view, that wouldn't make sense. Nobody seems to be interested in using > XWork outside Struts(yes, yes except that dude), and the proof is that > it didn't actually work until the other day. Why would we try to > support something for which there is no use case? It would be like > supporting supporting Struts on java 1.1 just for those users still > using java 1.1. > > That's one side of it, the other is that we *need* to consolidate > releases. There aren't many of us contributing, and there are less > willing to build releases (for example, I have never volunteered to > make an XWork release). Before, building Struts was a bottleneck > because it was largely undocummented, that got partially fixed and now > there is more people that are willing/able to release Struts. Now > XWork is the bottleneck because we have to depend on one brave dude to > have free time. If everything was under the Struts umbrella, anyone > with time to do a release could run the whole thing. OK, here's a question that's been on my mind for a while. Why is it that, for almost every S2 release, we need to make changes to something as core as XWork? Why isn't XWork stable enough by now that we don't have to be changing it all the time? It's often bothered me that we always seem to need to wait for an XWork release, not so much because of the wait, but because we seem to be so dependent on constant change in that library. What's up with that? That is what seems to be the real issue here. -- Martin Cooper > > > musachy > > On Mon, Aug 10, 2009 at 9:33 PM, Paul Benedict<pbened...@apache.org> > wrote: > > To say it has no value outside of Struts, I believe, downplays its > ability > > to be an independent framework / dependency injection container. I am not > > for binding it to Struts. I would vote for being it's own independent > Maven > > module or vote for it to join Apache Commons. > > > > On Mon, Aug 10, 2009 at 7:30 PM, Musachy Barroso <musa...@gmail.com> > wrote: > > > >> On Mon, Aug 10, 2009 at 5:22 PM, Don Brown<donald.br...@gmail.com> > wrote: > >> > 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 > >> > >> That's what I meant. A subproject is a no-go for me, as it would be > >> the same thing that we have now. > >> > >> musachy > >> -- > >> "Hey you! Would you help me to carry the stone?" Pink Floyd > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > >> For additional commands, e-mail: dev-h...@struts.apache.org > >> > >> > > > > > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org > For additional commands, e-mail: dev-h...@struts.apache.org > >
