> > As for Wes having to fix some stuff to make it work, that's a question of > how long it's been not working properly, and how many people have needed an > update during that period. That nobody else happened to report an issue > during that timeframe says nothing about how many people out there are using > it. For all you know, 20 people might have downloaded it the day after Wes > fixed it. Sounds crazy? Perhaps, but so does assuming nobody is using it > just because there's no noise on the list.
Besides, bug fixes (things in which these ninja users might be interested) in xwork are very few on every release of xwork. We usually need a new release because new things get added, like lets say the classpath scanner, or the reloading class loader. Because we have this "invisible" line, that divides struts from xwork, these things get added to xwork, instead of struts. If we were to add these new features to struts, then xwork releases would be needed very far between them. We can argue about the ninja users all we want, but there are 2 hard facts: 1. We depend on xwork and need it released to release struts 2 2. There is only one person that does xwork releases When I see someone volunteering on #2, then I will believe that #1 doesn't need to be fixed. The only ways I see of fixing #1 is to bring xwork in, as suggested, or to stop putting new code in xwork, which will eventually grow quieter and quieter until it is abandoned, and then, when we do have to fix an issue in it, we will have this argument again. Any volunteers for #2? 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
