>Yes, it’s official. XSL Tools 0.5 is now an official release. It’s available on the Web Tools update site through Ganymede and also on the Web Tools Download Site. I want to thank my fellow committers Doug Satchwell and Jesper Moller for their hard work and effort to help get to this point. A big thankyou goes out to those community members that downloaded the early milestone releases and tested the tooling out. Your feedback and contributions are much apppreciated.
So what do we have planned for the XSL Tools 1.0?
- We are planning to be part of the Galileo release train.
- Will integrate more into the Web Tools development process.
- More content assistance for XSL specific items like exclude-prefixes, known paramaters for called templates, mode content assistance, and more.
- XPath 2.0 support.
- More enhancements to the XSL Debugging.
- Ability to add non-Java processors like XSLProc to the launch configurations.
- More complete documentation.
- Better XSLT 2.0 support.
What else does the user community want to see? What do you like and don’t like. Please feel free to file a bug or enhancement request.
During the develoment of XSL Tools I learned a couple of things about the eclipse development process. Even though it has it’s roots in agile development, over the years it in some ways has become less agile as the years have gone along. Some of this is due to the IP process, some of it is due to the fact that committers now don’t necessarily practice the agile techniques consistently.
The IP process while I understand that it is there to protect adopters and members that use the code, needs some tweaking. In our case, we weren’t able to incorporate XSLT debugging support for XSLT 2.0, because of some IP concerns with Saxon 8 and 9. Saxon 6.5 was also not able to be redistributed because of the same concerns. I think Michael Kay has gone above and beyond the call of duty compared to many open source projects with his Contributions log on where code contributions have occurred.
Saxon it self is used in a wide variety of commerical applications in it’s open source form, it’s unfortunate that XSL Tools can’t redistribute this to provide the XSLT 2.0 support that is becoming more prevelant every day.