[jira] Resolved: (GERONIMO-579) UserTransaction broken after BMT calls BMT

[ http://issues.apache.org/jira/browse/GERONIMO-579?page=history ] Dain Sundstrom resolved GERONIMO-579: - Resolution: Fixed Fix Version: 1.0-M4 > UserTransaction broken after BMT calls BMT > -- > >

[jira] Assigned: (GERONIMO-579) UserTransaction broken after BMT calls BMT

[ http://issues.apache.org/jira/browse/GERONIMO-579?page=history ] Dain Sundstrom reassigned GERONIMO-579: --- Assign To: Dain Sundstrom > UserTransaction broken after BMT calls BMT > -- > > Key: GERONI

[jira] Resolved: (GERONIMO-181) Transaction propogation accross calls to stateful session beans

[ http://issues.apache.org/jira/browse/GERONIMO-181?page=history ] Dain Sundstrom resolved GERONIMO-181: - Resolution: Fixed Fix Version: 1.0-M4 > Transaction propogation accross calls to stateful session beans >

[jira] Updated: (GERONIMO-587) deployer can fail but appear to succeed

[ http://issues.apache.org/jira/browse/GERONIMO-587?page=history ] toby cabot updated GERONIMO-587: Attachment: deployer-error-patch.txt makes AbstractCommand. waitForProgress() throw DeploymentException if something goes wrong. makes the methods that c

[jira] Created: (GERONIMO-587) deployer can fail but appear to succeed

deployer can fail but appear to succeed --- Key: GERONIMO-587 URL: http://issues.apache.org/jira/browse/GERONIMO-587 Project: Apache Geronimo Type: Bug Components: deployment Versions: 1.0-M3 Environment: fedora core 2

Monitoring progress

The recent "What is going on" thread got me thinking it would be a good idea to remind everyone of other sources for gauging project progress. There are quite a few people on the [EMAIL PROTECTED] list so I thought I'd point out the scm@openejb.org list as well. There are only 18 subscribers o