Fred, The patch for
http://issues.apache.org/jira/browse/WSS-70 hasn't been applied yet. +1 from me to all of your suggestions. Colm. -----Original Message----- From: Fred Dushin [mailto:[EMAIL PROTECTED] Sent: 07 April 2008 16:26 To: wss4j-dev Subject: 1.5.4 release I'd like to gear up for a 1.5.4 release over the next few weeks, but I think we have a lot of work to do. The last release of WSS4J was 1.5.3, on Sept 7, 2007. So far, the fixes that have gone in since Sept 7 are: http://issues.apache.org/jira/browse/WSS-37* http://issues.apache.org/jira/browse/WSS-38* (dup of 37) http://issues.apache.org/jira/browse/WSS-51* http://issues.apache.org/jira/browse/WSS-56 http://issues.apache.org/jira/browse/WSS-68 http://issues.apache.org/jira/browse/WSS-70* http://issues.apache.org/jira/browse/WSS-74 http://issues.apache.org/jira/browse/WSS-89 http://issues.apache.org/jira/browse/WSS-92 http://issues.apache.org/jira/browse/WSS-95 http://issues.apache.org/jira/browse/WSS-103 http://issues.apache.org/jira/browse/WSS-105 http://issues.apache.org/jira/browse/WSS-100 http://issues.apache.org/jira/browse/WSS-101 http://issues.apache.org/jira/browse/WSS-106* * Indicates the ticket is still open in Jira, but can be closed -- I can't close it, because I do not have administrative privileges. Of the bugs that remain, I've filtered the existing unclosed high priority tickets, and have come up with 31. The following bugs have patches submitted, and I'll review them for inclusion in the next release: http://issues.apache.org/jira/browse/WSS-49 http://issues.apache.org/jira/browse/WSS-52 http://issues.apache.org/jira/browse/WSS-63 http://issues.apache.org/jira/browse/WSS-66 http://issues.apache.org/jira/browse/WSS-88 http://issues.apache.org/jira/browse/WSS-93 http://issues.apache.org/jira/browse/WSS-94 http://issues.apache.org/jira/browse/WSS-97 http://issues.apache.org/jira/browse/WSS-98 The following bugs do not have submitted patches, but have test cases for diagnosis -- they may get resolved for this release, if we have time: http://issues.apache.org/jira/browse/WSS-60 http://issues.apache.org/jira/browse/WSS-96 The following bugs have no test cases, and will have to be analyzed for criticality: http://issues.apache.org/jira/browse/WSS-36 http://issues.apache.org/jira/browse/WSS-39 http://issues.apache.org/jira/browse/WSS-40 http://issues.apache.org/jira/browse/WSS-42 (should be closable?) http://issues.apache.org/jira/browse/WSS-54 http://issues.apache.org/jira/browse/WSS-62 http://issues.apache.org/jira/browse/WSS-64 http://issues.apache.org/jira/browse/WSS-78 http://issues.apache.org/jira/browse/WSS-81 http://issues.apache.org/jira/browse/WSS-82 http://issues.apache.org/jira/browse/WSS-85 http://issues.apache.org/jira/browse/WSS-87 http://issues.apache.org/jira/browse/WSS-90 http://issues.apache.org/jira/browse/WSS-102 Would folks be open to a release, if we could address some of these issues? After 1.5.4 goes out, we can discuss further changes to WSS4J. I'd like to propose that we branch the 1.5 source onto a fixes branch, and that we use the mainline for 2.0 development. For 2.0, I'd like to consider: * Porting to JDK 1.5 * Using maven for building and deploying * Supporting WS-Security using JAX-B generated types, in much the same way as XWSS3 What do people think? Thanks, Fred --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---------------------------- IONA Technologies PLC (registered in Ireland) Registered Number: 171387 Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
