Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
I did a bit of tinkering around with the tomcat and jetty jee5, as well as minimal assemblies, and failed to find anything slap-me-in-the-face obvious, while I did pay some close attention to trying to break the various security mechanisms in it, and it seemed to withstand what I threw against it, only issues being where as Hernan and others were discussing with the plugin installations... but as I have also learned from Paul, is temporary. In all, here's my mock +1 (I'll go ahead and just call it a thumbs up) =P -- Erik B. Craig
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Thanks Paul for such detailed explanation, I still have a lot to learn on the plugin architecture. Cheers! Hernan Paul McMahan wrote: Hernan, what you are seeing is expected and is a side effect of the way that we test release candidates [1]. For a given geronimo release there are three parts of the plugin system that need to be tested: 1.) the plugin installer 2.) the plugins 3.) the plugin catalog Right now the 2.0 plugin catalog points at the 2.0-SNAPSHOT plugins because those are the only ones available in a public maven repo. This allows us to test if #1 (the plugin installer) can do its job correctly. And as you have found the plugins are downloaded and installed correctly. But in order for us to properly test #2 and #3 we need for the plugins to be deployed to a maven repo. Here is a chicken and egg problem, because the plugins are not deployed until the release candidate has passed its vote. So, unless we decide to change our plugin infrastructure to be less dependent on maven, or change the way we test release candidates we will need to sometimes overlook the type of error you saw where the plugin is downloaded and installed OK but it won't start due to some incompatibility with the server. I try to remember to point out during a vote that some plugins (which are usually SNAPSHOT) may not work in the release candidate [2]. After a release candidate has passed its vote and its plugins are deployed I usually update the catalog to point at the "real" plugins. The catalog is maintained online at geronimo.apache.org, so we can update that outside of the release process. But there is a bit of finger crossing going on here since the plugins themselves are part of the officially released bits and have already been deployed. If they don't work then we may have to crank out another release or remove them from the catalog. So far we have considered the risk of releasing broken plugins as necessary due to the amount of overhead in the release process [3]. As some aspects of our server such as the console move towards relying on the plugin system for core functionality we may need to revisit what's in the release candidate and/or how we vote on it. Best wishes, Paul [1] http://www.nabble.com/1.2-Fit-and-Finish-tf2543870s134.html#a7114633 [2] http://www.nabble.com/-DISCUSS--Geronimo-2.0-%28rc1%29-Release-tf4235631s134.html#a12059054 [3] http://www.nabble.com/1.2-Fit-and-Finish-tf2543870s134.html#a7144688 On Aug 16, 2007, at 10:30 AM, Hernan Cunico wrote: Anybody seeing plugin issues, specially when starting them? Could it be a versioning problem, I get similar errors on both Jetty and Tomcat - Unable to start configuration org.apache.geronimo.configs - org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception - org.apache.geronimo.gbean.InvalidConfigurationException: Getter method not found Attribute Name: URLFor, Type: class java.net.URL, GBeanInstance: Jetty WebApplication Context Cheers! Hernan Matt Hogstrom wrote: Initial discuss thread
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Hernan, what you are seeing is expected and is a side effect of the way that we test release candidates [1]. For a given geronimo release there are three parts of the plugin system that need to be tested: 1.) the plugin installer 2.) the plugins 3.) the plugin catalog Right now the 2.0 plugin catalog points at the 2.0-SNAPSHOT plugins because those are the only ones available in a public maven repo. This allows us to test if #1 (the plugin installer) can do its job correctly. And as you have found the plugins are downloaded and installed correctly. But in order for us to properly test #2 and #3 we need for the plugins to be deployed to a maven repo. Here is a chicken and egg problem, because the plugins are not deployed until the release candidate has passed its vote. So, unless we decide to change our plugin infrastructure to be less dependent on maven, or change the way we test release candidates we will need to sometimes overlook the type of error you saw where the plugin is downloaded and installed OK but it won't start due to some incompatibility with the server. I try to remember to point out during a vote that some plugins (which are usually SNAPSHOT) may not work in the release candidate [2]. After a release candidate has passed its vote and its plugins are deployed I usually update the catalog to point at the "real" plugins. The catalog is maintained online at geronimo.apache.org, so we can update that outside of the release process. But there is a bit of finger crossing going on here since the plugins themselves are part of the officially released bits and have already been deployed. If they don't work then we may have to crank out another release or remove them from the catalog. So far we have considered the risk of releasing broken plugins as necessary due to the amount of overhead in the release process [3]. As some aspects of our server such as the console move towards relying on the plugin system for core functionality we may need to revisit what's in the release candidate and/or how we vote on it. Best wishes, Paul [1] http://www.nabble.com/1.2-Fit-and-Finish-tf2543870s134.html#a7114633 [2] http://www.nabble.com/-DISCUSS--Geronimo-2.0-%28rc1%29-Release- tf4235631s134.html#a12059054 [3] http://www.nabble.com/1.2-Fit-and-Finish-tf2543870s134.html#a7144688 On Aug 16, 2007, at 10:30 AM, Hernan Cunico wrote: Anybody seeing plugin issues, specially when starting them? Could it be a versioning problem, I get similar errors on both Jetty and Tomcat - Unable to start configuration org.apache.geronimo.configs - org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception - org.apache.geronimo.gbean.InvalidConfigurationException: Getter method not found Attribute Name: URLFor, Type: class java.net.URL, GBeanInstance: Jetty WebApplication Context Cheers! Hernan Matt Hogstrom wrote: Initial discuss thread
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
yup, we are talking about the same plugins. I just wanted to test some of those showing as *available* first then try to export some configs as plugins. we may need to revisit those showing up as available before releasing 2.0.1. Once I get a couple to work I'll try some of my own. Cheers! Hernan Joe Bohn wrote: Hernan Cunico wrote: Anybody seeing plugin issues, specially when starting them? Could it be a versioning problem, I get similar errors on both Jetty and Tomcat - Unable to start configuration org.apache.geronimo.configs - org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception - org.apache.geronimo.gbean.InvalidConfigurationException: Getter method not found Attribute Name: URLFor, Type: class java.net.URL, GBeanInstance: Jetty WebApplication Context Where did you get the plugin that you are trying to install? Do we have any plugins yet for 2.0.1? I attempted to install a plugin for 2.0-SNAPSHOT (Jakarta JSP Examples from the 2.0 plugins repo which was the default in the console even though this is 2.0.1). The 2.0-SNAPSHOT plugins were listed as available for install for 2.0.1. As you mentioned, it installed fine but when I attempted to start it I hit the same errors you listed. At the root of all of them was an NoSuchMethodException for org.apache.geronimo.jetty6.JettyWebAppContext.getURLFor() It looks like this method was removed from both our Jetty & Tomcat WebAppConext as part of the connector changes. Is there still some plugin & plugin site prep work necessary for 2.0.1? I suspect that we need to have new plugins generated for 2.0.1 and ensure the 2.0-SNAPSHOT plugins are marked as incompatible with 2.0.1. Joe
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
On Aug 16, 2007, at 2:57 PM, Joe Bohn wrote: Hernan Cunico wrote: Anybody seeing plugin issues, specially when starting them? Could it be a versioning problem, I get similar errors on both Jetty and Tomcat - Unable to start configuration org.apache.geronimo.configs - org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception - org.apache.geronimo.gbean.InvalidConfigurationException: Getter method not found Attribute Name: URLFor, Type: class java.net.URL, GBeanInstance: Jetty WebApplication Context Where did you get the plugin that you are trying to install? Do we have any plugins yet for 2.0.1? I attempted to install a plugin for 2.0-SNAPSHOT (Jakarta JSP Examples from the 2.0 plugins repo which was the default in the console even though this is 2.0.1). The 2.0-SNAPSHOT plugins were listed as available for install for 2.0.1. As you mentioned, it installed fine but when I attempted to start it I hit the same errors you listed. At the root of all of them was an NoSuchMethodException for org.apache.geronimo.jetty6.JettyWebAppContext.getURLFor() It looks like this method was removed from both our Jetty & Tomcat WebAppConext as part of the connector changes. Is there still some plugin & plugin site prep work necessary for 2.0.1? I suspect that we need to have new plugins generated for 2.0.1 and ensure the 2.0-SNAPSHOT plugins are marked as incompatible with 2.0.1. Are there some 2.0-SNAPSHOT plugins that have been released? If so, how did that happen, as I don't recall a vote. Otherwise can't we just remove them? thanks david jencks Joe
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Hernan Cunico wrote: Anybody seeing plugin issues, specially when starting them? Could it be a versioning problem, I get similar errors on both Jetty and Tomcat - Unable to start configuration org.apache.geronimo.configs - org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception - org.apache.geronimo.gbean.InvalidConfigurationException: Getter method not found Attribute Name: URLFor, Type: class java.net.URL, GBeanInstance: Jetty WebApplication Context Where did you get the plugin that you are trying to install? Do we have any plugins yet for 2.0.1? I attempted to install a plugin for 2.0-SNAPSHOT (Jakarta JSP Examples from the 2.0 plugins repo which was the default in the console even though this is 2.0.1). The 2.0-SNAPSHOT plugins were listed as available for install for 2.0.1. As you mentioned, it installed fine but when I attempted to start it I hit the same errors you listed. At the root of all of them was an NoSuchMethodException for org.apache.geronimo.jetty6.JettyWebAppContext.getURLFor() It looks like this method was removed from both our Jetty & Tomcat WebAppConext as part of the connector changes. Is there still some plugin & plugin site prep work necessary for 2.0.1? I suspect that we need to have new plugins generated for 2.0.1 and ensure the 2.0-SNAPSHOT plugins are marked as incompatible with 2.0.1. Joe
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Thanks Vamsi...lots of little ones to fix...I'll make sure it gets included if we need to re-spin. On Aug 16, 2007, at 9:11 AM, Vamsavardhana Reddy wrote: Will not press for inclusion of this in 2.0.1, but do include rev 566694 (fix for "GERONIMO-3390 Server Logs portlet - Web Access Log Viewer is broken" when date fields are empty) in case a new RC needs to be spun for some reason. Never thought the fix would be one line :o) or else would have got it merged before RC1 was spun :o(. Vamsi PS: I sincerely do not want to delay the release of 2.0.1 :o) On 8/16/07, Matt Hogstrom <[EMAIL PROTECTED] > wrote: Upload complete ... vote away. On Aug 15, 2007, at 4:34 PM, Matt Hogstrom wrote: > Initial discuss thread >
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Anybody seeing plugin issues, specially when starting them? Could it be a versioning problem, I get similar errors on both Jetty and Tomcat - Unable to start configuration org.apache.geronimo.configs - org.apache.geronimo.kernel.config.InvalidConfigException: Unknown start exception - org.apache.geronimo.gbean.InvalidConfigurationException: Getter method not found Attribute Name: URLFor, Type: class java.net.URL, GBeanInstance: Jetty WebApplication Context Cheers! Hernan Matt Hogstrom wrote: Initial discuss thread
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Will not press for inclusion of this in 2.0.1, but do include rev 566694 (fix for "GERONIMO-3390 Server Logs portlet - Web Access Log Viewer is broken" when date fields are empty) in case a new RC needs to be spun for some reason. Never thought the fix would be one line :o) or else would have got it merged before RC1 was spun :o(. Vamsi PS: I sincerely do not want to delay the release of 2.0.1 :o) On 8/16/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: > > Upload complete ... vote away. > On Aug 15, 2007, at 4:34 PM, Matt Hogstrom wrote: > > > Initial discuss thread > > > >
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Upload complete ... vote away. On Aug 15, 2007, at 4:34 PM, Matt Hogstrom wrote: Initial discuss thread
Re: [DISCUSS] Release Geronimo 2.0.1 (rc1)
Oops...hang on ... upload problem. On Aug 15, 2007, at 4:34 PM, Matt Hogstrom wrote: Initial discuss thread
