ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yakov Zhdanov <yzhda...@apache.org>
Subject Re: Ignite-1.5 Release
Date Mon, 30 Nov 2015 16:30:24 GMT

Our plan was to release over the weekend, but unfortunately that didn’t
happen due to a few bugs. And even though we have fixed all the discovered
issues I am still not comfortable with releasing the final version. Having
the great number of functionality introduced in 1.5 including (but not
limited to) - .net and cpp platforms, marshalling changes to support
platforms and massive optimizations - I would ask community whether we can
release 1.5.0-EA and have folks to play with it for a week or so and then
release the final version.

Please let me know your opinion. If community agrees I will submit 1.5.0-EA
for vote in a few hours.


2015-11-28 13:57 GMT+03:00 Yakov Zhdanov <yzhdanov@apache.org>:

> Guys,
> Small update. We are very close to submit Ignite-1.5-RC1. We currently
> fixing TeamCity in ignite-1.5 branch.
> --Yakov
> 2015-11-25 3:39 GMT+03:00 Dmitriy Setrakyan <dsetrakyan@apache.org>:
>> On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani <raulk@apache.org> wrote:
>> > It's integrated, i.e. it deploys on an OSGi container. And the Ignite
>> part
>> > works. But at soon as it delegates to Spring to parse the context XML,
>> the
>> > latter complains about namespace handlers not being found.
>> >
>> > Spring DM looks into bundles to find NS handlers. So without Spring DM
>> such
>> > problems are expected.
>> >
>> > Maybe it does work after all if we refrain from using certain namespace
>> > like util. I'll have to check that tomorrow.
>> >
>> Thanks! Dropping support for Spring XML configuration in OSGI would be a
>> huge loss. Would be great if you could investigate it and see what it
>> would
>> take.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message