This fix seems to have exposed an issue where the connector builder failed to deploy plans where no parent ID was specified (instead of using the configured default). David J and I have checked in a fix for that. I also fixed the problem where the j2ee-installer assembly failed on missing release notes.
All that has been done as of SVN 356751. Aaron On 12/14/05, Aaron Mulder <[EMAIL PROTECTED]> wrote: > I'm sorry to say, but -1: the console has a dangling SNAPSHOT that > means that no database pools can be deployed from the database pool > portlet. I put all the blame on the guy who did the SNAPSHOT cleanup > in the branch, who was, umm, me. :) > > I checked the fix in to the 1.0 branch. > > Aaron > > On 12/14/05, Jason Dillon <[EMAIL PROTECTED]> wrote: > > Not gonna do a RCn series first? > > > > --jason > > > > > > On Dec 13, 2005, at 8:30 PM, Matt Hogstrom wrote: > > > > > We are currently going through the final testing phases and have > > > the binary images available for review. These images represent > > > what we will be making available to users after we confirm the > > > final set of tests. > > > > > > Please take some time to download a binary and review it for > > > completeness. The binaries you will be most interested in are: > > > > > > http://people.apache.org/~dblevins/geronimo-1.0/ > > > > > > geronimo-jetty-j2ee-1.0.tar.gz > > > geronimo-jetty-j2ee-1.0.zip > > > geronimo-tomcat-j2ee-1.0.tar.gz > > > geronimo-tomcat-j2ee-1.0.zip > > > > > > The .gz files are for *nix platforms and the .zip binaries are for > > > Windows. > > > > > > There are other files in the distribution for your reviewing > > > pleasure like source and signature files. > > > > > > Please post your votes and comments. Thanks > > > > > > [ ] +1 Release these binaries > > > [ ] -1 Veto the release (provide specific comments) > > > > > > ~ Matt > > > > > > > >