[Lucene.Net] 2.9.4 release couldn't be compiled for .Net3.5
Hi, First of all thank you for the new release 2.9.4. That makes me really happy. However, I noted that current binaries are build for .Net 4.0 framework only, which is very inconvenient. The reason is we have a hard requirement to use .Net3.5sp1. We were going to build it manually as usual, but stumbled upon .Net 4.0 specific code (file CloseableThreadLocal.cs): private ThreadLocalWeakReference t = new ThreadLocalWeakReference(); For now we just replaced CloseableThreadLocal file with a version from 2.9.2, but still. What is an official strategy of the Lucene.Net team about framework versions? Is there a chance that Lucene.Net will be released in future not only for 4.0, but for 3.5 too? Kind Regards, Alexey Shcherbachev Rebel Search team Skype: Leha-2304 Web: http://rebelsearch.net/
Re: [Lucene.Net] 2.9.4 release couldn't be compiled for .Net3.5
Hi Alexey, I believe this version of Lucene.Net will be the last version that can be compiled with the .NET 2.0 runtime which is what .NET 3.5 runs on. There was a vote on supported runtime versions by the community this past year, The community widely supported to drop .NET 2.0 runtime after the 2.9.4 release in favor of the .NET 4.0 runtime. I also believe most of the committers will be focused on using generics with the next version and possibly .NET 4.0 specific code. However, since the code is open source, anyone can contribute branches that can be compiled on the .NET 2.0 runtime. There is plenty of work and only a handful of committers with a limited amount of time to work on the project and there is a need for a narrow focus from the committers in order to move the project forward with releases. But we're more than open to discussing what it would take to accomplish something like that if it has enough support from the community if that is something that interests you or anyone else reading this thread. If you search the mailing list, DIGY has some instructions on how to compile the 2.9.4 tag in a way that is compatible with .NET 2.0. If I stumble across it or someone else knows the steps, it will re-posted in this thread. But it does have to do with commenting out the ThreadLocal and uncommenting out another portion of the code. - Michael On Tue, Dec 6, 2011 at 7:42 AM, Alexey Shcherbachev ale...@renaissance-it.ru wrote: Hi, First of all thank you for the new release 2.9.4. That makes me really happy. However, I noted that current binaries are build for .Net 4.0 framework only, which is very inconvenient. The reason is we have a hard requirement to use .Net3.5sp1. We were going to build it manually as usual, but stumbled upon .Net 4.0 specific code (file CloseableThreadLocal.cs): private ThreadLocalWeakReference t = new ThreadLocalWeakReference(); For now we just replaced CloseableThreadLocal file with a version from 2.9.2, but still. What is an official strategy of the Lucene.Net team about framework versions? Is there a chance that Lucene.Net will be released in future not only for 4.0, but for 3.5 too? Kind Regards, Alexey Shcherbachev Rebel Search team Skype: Leha-2304 Web: http://rebelsearch.net/
RE: [Lucene.Net] 2.9.4 release couldn't be compiled for .Net3.5
From digy: OK, here is the code that can be compiled against .NET 2.0 http://pastebin.com/k2f7JfPd FYI, we believe there may be a memory leak related to this code ( not in this particular code though ) Sent from my Windows Phone From: Michael Herndon Sent: 12/6/2011 5:42 AM To: lucene-net-dev@lucene.apache.org Subject: Re: [Lucene.Net] 2.9.4 release couldn't be compiled for .Net3.5 Hi Alexey, I believe this version of Lucene.Net will be the last version that can be compiled with the .NET 2.0 runtime which is what .NET 3.5 runs on. There was a vote on supported runtime versions by the community this past year, The community widely supported to drop .NET 2.0 runtime after the 2.9.4 release in favor of the .NET 4.0 runtime. I also believe most of the committers will be focused on using generics with the next version and possibly .NET 4.0 specific code. However, since the code is open source, anyone can contribute branches that can be compiled on the .NET 2.0 runtime. There is plenty of work and only a handful of committers with a limited amount of time to work on the project and there is a need for a narrow focus from the committers in order to move the project forward with releases. But we're more than open to discussing what it would take to accomplish something like that if it has enough support from the community if that is something that interests you or anyone else reading this thread. If you search the mailing list, DIGY has some instructions on how to compile the 2.9.4 tag in a way that is compatible with .NET 2.0. If I stumble across it or someone else knows the steps, it will re-posted in this thread. But it does have to do with commenting out the ThreadLocal and uncommenting out another portion of the code. - Michael On Tue, Dec 6, 2011 at 7:42 AM, Alexey Shcherbachev ale...@renaissance-it.ru wrote: Hi, First of all thank you for the new release 2.9.4. That makes me really happy. However, I noted that current binaries are build for .Net 4.0 framework only, which is very inconvenient. The reason is we have a hard requirement to use .Net3.5sp1. We were going to build it manually as usual, but stumbled upon .Net 4.0 specific code (file CloseableThreadLocal.cs): private ThreadLocalWeakReference t = new ThreadLocalWeakReference(); For now we just replaced CloseableThreadLocal file with a version from 2.9.2, but still. What is an official strategy of the Lucene.Net team about framework versions? Is there a chance that Lucene.Net will be released in future not only for 4.0, but for 3.5 too? Kind Regards, Alexey Shcherbachev Rebel Search team Skype: Leha-2304 Web: http://rebelsearch.net/
