Quick update of the release, some questions inline... excalibur-component: OK, builds
new version: 1.2 (old:1.1) The test case for ECM auto-release of components (when a client doesn't release components it has looked up) fails, but I think the auto-release functionality was removed due to it introducing memory leaks in Cocoon. Can anyone confirm this? excalibur-sourceresolve: OK, builds new version: 1.1 (old:1.0.1) excalibur-store: OK, builds new version: 1.0 (old: ???) excalibur-xmlutil: Unsatisfied dependencies new version: 1.0 (old: ???) dep: saxon7-7.7.jar dep: saxon7-jdom-7.7.jar dep: saxon7-sql-7.7.jar dep: xml-commons-resolver-1.1.b1.jar BETA? Carsten, do you want to release xmlutil even though it is dependent on a beta? excalibur-logger: Doesn't build, will have to point out source paths for Maven. new version: 1.1 (old: 1.0.1) fortress-container: OK, builds new version: 1.1 (old: 1.1-dev) fortress-tools: OK, builds new version: 1.1 (old: 1.1-dev) /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
