Ok, I'll check it when I get back home tonight. Rationale for compiling against 2.0 is that some of my clients won't deploy a beta so unless 2.1 is due for release shortly we will won't be able to release NH Search for a few months.
What actual depedencies are there on the 2.1 code based - could we handle this just with an assembly binding policy so that we compile against 2.0 but have a policy to redirect to 2.1 if it's there? Paul ---------------------------------------- From: Pierre Henri Kuate <[email protected]> Sent: 26 January 2009 09:41 To: NHibernate Contrib - Development Group <[email protected]> Subject: Re: Working on NHibernate.Search It seems that your commit didn't go through. About NH 2.1, are you asking if we could conditionally compile against it or NH 2.0? If so, yes, I think it is possible using NAnt, but is it really worth the effort? I would think that all users will soon have migrated to NH 2.1... On Jan 26, 10:48 am, "Paul Hatcher" wrote: > Just done another commit - fixes problem with projection/transforms and adds > the appropriate tests. > > Shouldn't cause too many issues as I think there's only 3-4 lines changed in > the main search project. > > I think that we won't need new project files as VS 2008 uses the same > format, it's just the solution file that will vary. > > Only major issue I see is the upgrade to NH 2.1 trunk - would be nice to get > this out under some version of 2.0 as 2.1 hasn't hit official beta yet; any > way we can do this conditionally? > > Regards > > Paul > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > > Of Pierre Henri Kuate > Sent: 25 January 2009 18:42 > To: NHibernate Contrib - Development Group > Subject: Re: Working on NHibernate.Search > > So far, I have been working on the Tests only; I didn't need to change > NH.Search to make them pass. > > Before starting, I migrated NH.Search to NHibernate 2.1 because that's what > I'm using in my project. I'm developing using VS2008, so I also had to > create new csprojs and I will update the VS2005 ones when I'm done (just > need to add the new files). > > I think that we could support both NH 2.1 and NH 2.0 by adding a conditional > directive. So I will define NHIBERNATE20 and use it in the > VS2005 project. > > On Jan 24, 7:45 am, Pierre Henri Kuate wrote: > > In this case, I will continue working on 3.0. > > By the way, I want to do a lot of work on it this Sunday & Monday; so > > if you have some changes to commit, it would be nice to do it before I > > get started :) > > > Pierre Henri. > > > On Jan 21, 5:45 pm, "paulh" wrote: > > > > Pierre > > > > I'm not sure why Oren decided to go straight to Hibernate Search 3.1 > rather than working on the current port to 3.0 GA - this was picked as it > was based on a version of Hibernate that we have most of the features of > whereas the 3.1 has a dependency on Hibernate Core 3.3 which we are not > compliant with. > > > > Completion level of the current port of Seach I would estimate at 80% > with the test completion at 60-70% with a current coverage of 60%, major > lack at the moment is support of thing like projections. > > > > Any patches you have are gratefully received - I can put tests in if > needed. > > > > Regards > > > > Paul > > > > ---------------------------------------- > > > > From: Pierre Henri Kuate > > > Sent: 21 January 2009 12:52 > > > To: NHibernate Contrib - Development Group > > > > > > Subject: Working on NHibernate.Search > > > > Hi all, > > > > I would like to summarize my understanding of the status of > > > NHibernate.Search and discuss its future dev. > > > > From the history in the SVN (http://nhcontrib.svn.sourceforge.net/ > > > viewvc/nhcontrib/trunk/src/NHibernate.Search/?view=log), I see that > > > the NH.Search in NHContrib is a port of H.Search 3.0, but I don't > > > know how complete it is. > > > > Ayende has also started a port of H.Search r15224 (pre-H.Search 3.1 > > Beta2):http://nhcontrib.svn.sourceforge.net/viewvc/nhcontrib/branches/nh-sea > ... > > > By the way, H.Search 3.1 GA was released in December with some > > > interesting improvements (http://in.relation.to/Bloggers/ > > > HibernateSearch31IsOutPerformanceRobustnessAndNewFeaturesOnTheMenu) > > > > I am currently using NH.Search in my project and I have hacked it a > > > little to fix some small bugs here and there. But since these > > > changes are untested, I don't feel comfortable committing them. > > > > From my experience, the current NH.Search is still quite buggy; I > > > don't know if any of you has used it in production... > > > > So, where do we go from there? > > > > I agree with Ayende that stabilization should have a high priority. > > > I don't know if trying to fix the current NH.Search will get us > > > there faster than completing the port of H.Search 3.1... > > > > Pierre Henri. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com.ar/group/nhcdevs?hl=en -~----------~----~----~----~------~----~------~--~---
