Some info for the MyFaces integration, after communicating with MyFaces community, they are now working on some imprvoments for better integration with third-party containers. Except for the improvment, there might be some annotation bug fix ( Seem not covered by TCK). I am not sure whether we would have time for it, guess not, as a new MyFaces release might be required. For Tomcat, I found some improper dependencies between catalina and catalina-ha modules, I will post a message to Tomcat community, but this should not block us release new Tomcat external release, I will pull the latest Tomcat codes soon. Also, we got a bug fix (or improvment) in el-api, I think that it is better to have a new geronimo-el release. thanks.
2010/10/21 Rick McGuire <[email protected]> > We've made a lot of progress on Geronimo 3.0 since the M1 release and are > starting to get close to passing the Web Profile TCK. I'm thinking it's > time to start discussing plans for doing another release update. > > I'm assuming we'd want to do this shortly after we can be certified as > passing the Web Profile TCK. At that time, we'll have a number of SNAPSHOT > dependencies we'll need to have releases on. The biggest dependencies that > will need to resolved (and which likely can only be handled after getting > the TCK to pass cleanly) are openejb, openwebbeans, and xbean. Two other > critical components we'd need are a new tomcat external release and a Jetty > release (currently using 8.0.0.M2-SNAPSHOT) > > Other snapshots we're using: > > - the txmanager and connector (probably can only be released toward the > end) > - jaspi (probably can be released at any time) > - the ejb spec (probably can be released at any time) > - the el spec (Just had an update to a number of files, might want to wait > a little on this one). > - scout (used only for web services, so this will likely be removed). > - axiom (ditto) > - activemq 5.4-SNAPSHOT (5.4.1 is out...can we use that one? This is > something we should investigate now). > > For the 3.0-M1 release, the big hold up was the long chain of snapshot > dependencies that needed to be resolved. The more we can get resolved now, > the better the chances of avoiding the same chain-reaction pileup we > experienced the last time. > > Implicit in the above is the M2 release would receive the same sort of > pruning that was performed on the M1 release to remove all of the web > services elements that really have not had received any attention yet. If > not, then we'll need to chase after some additional components like scout. > > Rick > > > > > > -- Ivan
