> > I hate to be a nay-sayer here, but I, for one am using XWork outside of struts > and think it has some really serious potential as a command-pattern framework > outside of Struts. I just started using it recently and to be honest, I had to > jump through some hoops to get it working because it seems like we made some > compromises for struts (removing all of the bean definitions from xwork- > default.xml). I actually have some plans for xwork as soon as I get my current > project released. >
I was going to ask if anyone was using it outside struts, but that doesn't prevent us from making it it's own artifact. > That being said, I don't think I'd mind if we moved it into apache-space... I > think it would benefit from apache's infrastructure. If we made it a top-level > project maybe in the asf repo, next to struts1 and struts2 that would be cool > because all struts committers would have easy access to it, but it could > retain it's identity and I could keep running it in a back-end (read: non-web- > app) context. I don't think this would fix the problem, which is the duplicated effort on the builds. A good compromise would be to keep it under its own artifact under struts, just like core, that way we would need just one release and it could still be used independently. I haven't cared much before, but if it will make our releases easier/smoother, then I am +1 for it. 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
