Dan, I've been forced to make some minor changes to the Corona code to accommodate the latest Axsis2. I'm currently in synch with the 1.1 code line as of yesterday - I'm in the process of re-integrating and testing with Muse today. Thus far I haven't had to make any changes to org.apache.anything, but I'd like to reserve the option of updating the SOAPProvider interface in org.apache.muse.soa.core unless you strenuously object.
Cheers, Joel -----Original Message----- From: Daniel Jemiolo [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 11:30 AM To: [email protected] Subject: update on release schedule and dependencies Axis2 code freeze: Monday 9/25 I assume this is when they will post the RC build and start the vote. If not, we start our vote when they start theirs. Axis2 release: Friday 9/29 I believe that "Friday" is on WS02 time, which is Thursday night for all of the Muse committers. Thus, we should have our release confirmed by Thursday night and release on Friday the 29th with no delay because of Axis2. Assuming all is well with the Axis2 JAR files themselves, we can have our vote start and end at the same time as Axis2 1.1. If, for some reason, the Axis2 1.1 release is pushed out, I propose that we ship without the Axis2 WAR and ask users to download it to MUSE_HOME/lib (any alternative ideas?). You can follow the progress of the 1.1 release on axis-dev. Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
