Matt, This is the same question as the one you asked yesterday. A JIRA search for 'project = aries AND resolutiondate > "2010/05/26" AND resolutiondate < "2011/02/14" ' (I'm not 100% sure of the 0.3 release date, but that's about right) yields 239 issues. That's a lot to summarise.
Apache Aries 0.3 allowed us to significantly flesh out the Aries application programming model. It includes support for resolving Aries applications against Felix OBR, and provides an Equinox-based runtime capable of running multiple applications that are both isolated from each other, and capable of sharing their common dependencies, both on disk and in memory. Blueprint and persistence bundles now enjoy quiesce support, allowing them to be shut down cleanly. JNDI support has been substantially rewritten. The samples have been improved. More components work on Apache Felix. The blueprint:comp namespace was introduced, allowing blueprint's benefits to be extended to non-blueprint-managed code. Numerous bugs were fixed and a broad range of improvements made across the entire project. Please see JIRA, and of course SVN and the code itself, for more information. That's my canned summary speaking as an Apache Aries committer. Please also see my recent follow up post to your related question on the developerWorks forum, where I add a few implementation-specific footnotes to this summary. Regards, Mark On 25 October 2011 18:40, Matt Madhavan <[email protected]> wrote: > Hello, > I have to build a case for going with Aries 0.3 + and not Aries 0.1. So far > I have found few issues already with 0.1. > > I would like to have additional information on why I would recommend my > client to move to Aries 0.3 or 0.4. If some one can point me to a list of > issues and other information I would greatly appreciate it. I know I can dig > around this my self. But if some one already has a case why I should go with > atleast 0.2 (Like Johan had mentioned) I would greatly appreciate it. > > Thanks in advance! > > Matt > > > >
