Merging XWork into Struts Core

Hi, I'm considering merging XWork code base into Struts Core module. There is a lot problems when I want to write some extension points (with @Inject and BeanSelectionProvider) and when the same extension point must be defined for class from XWork - I have to translate constants to keep separation

Re: Merging XWork into Struts Core

Not any more, I guess. I'd like to see that stuff be usable on its own somehow, but realistically, few people use it standalone any more. On May 10, 2014 7:09 PM, "Lukasz Lenart" wrote: > Hi, > > I'm considering merging XWork code base into Struts Core module. There > is a lot problems when I wa

Re: Merging XWork into Struts Core

However, on second thoughts, I would like to know the purpose of keeping XWork separate. Was it to allow other clients besides Struts? And do any of those exist? My line of questioning is really about the future. If we want to clearly separate out a Struts API and Struts Core Implementation, we sh

Jenkins build is back to normal : Struts-JDK6-features #49

See - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org