On Jan 3, 2008 5:44 AM, Brian Pontarelli <[EMAIL PROTECTED]> wrote: > What is the policy for Struts committers getting access to XWork? While > updating the convention plugin I had to change a few things in XWork and I > want to make sure that they get committed to trunk before I start using the > convention plugin on projects. I have a few bugs open, but it could take a > while to get those in. Since Struts and XWork as so tightly coupled and > still separate projects, would it make sense for all Struts committers to > also have access to XWork?
Yep, send me an email with your desired user name and your sha1-encoded password, and I'll add you. > Also, as a separate topic, what are the future plans for all the external > dependencies for Struts core? One of the difficult things I've found is that > the two most major dependencies, OGNL and XWork, are not only confusing for > some of my employees since the need to import from packages other than > org.apache.struts2, but also not accessible to me for modification and > updates and such. At this point, our plan is to leave them where they are. I'd like to get rid of OGNL through the JUEL plugin, and perhaps just include the xwork code inside the Struts jar, dropping our dependency list down to just Freemarker. Don > > -bp > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
