I see. At first I was thinking that if we have the source in struts2 code base, we could do a release of ognl with fixes whenever we release webwork. Ognl development seems to be inactive for a long time. I think Pat have commit access to Ognl code, but are we allow to do a release of Ognl when felt appropriate?
But as Martin pointed out, there's going to be quite a massive responsibility in maintaining ognl docs, patches, user requests etc. So i guess its not really a feasible option right now. Cheers. Martin Cooper <[EMAIL PROTECTED]> wrote: On 11/13/06, tm jee wrote: > > Hey guys, > > What do you guys think about moving Ognl code base into Struts2, just like > what was did with Guice? I would not be in favour of that. As Don implies, that means that we would effectively be forking OGNL and taking on the responsibility to maintain it (code, documentation, etc.) ourselves, including updating to any newer releases of the "original" OGNL that came along. I'd have to see convincing reasons to take that on, which I don't see right now. -- Martin Cooper rgds > > > --------------------------------- > All new Yahoo! Mail "The new Interface is stunning in its simplicity and > ease of use." - PC Magazine > Send instant messages to your online friends http://uk.messenger.yahoo.com
