[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-728?pag...
]
Sanne Grinovero commented on HSEARCH-728:
-----------------------------------------
Hi Chris,
You make good points. This is the balance we constantly try and adjust between innovation
and stability in our products. New features are made in our projects and being new we
have less feedback and don't know how stable they are. It would be foolish to claim we
can support them properly. We're putting an effort in trying to have a faster pace
between newer releases and supported releases, so that people don't have to wait for
too long for a feature.
We generally don't backport new features to products as it could endanger the
stability and the backward compatibility of the platform. This feature is a good example.
We have found several bugs since its introduction and have been fixing them over time.
That said, we do break that rule from time to time and on a case by case basis upon
customer demand and we have backported features needed by our customers when we found them
stable enough.
I see that you've implemented a solution in your project but if you still need the
feature in, please open a customer ticket and email me (sanne at hibernate dot org) or
Emmanuel (emmanuel at hibernate dot org). No guarantee but we will push in your
direction.
Backport MassIndexer to 3.1.X
-----------------------------
Key: HSEARCH-728
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-728
Project: Hibernate Search
Issue Type: Task
Components: massindexer
Affects Versions: 3.1.1.GA
Environment: Hibernate 3.3.X and any jboss server platform prior to 6.0.
Reporter: Chris Hornsey
Anyone using a non JPA2 version of hibernate is unable to utilize the capabilities of the
MassIndexer introduced in version 3.2 of search. At a cursory glance I can not determine
a dependency of the new indexer on JPA2.
It would be very beneficial to make this available as utilizing hibernate search on
existing application and manually indexing is obviously difficult with this new
massindexer.
Also anyone who chooses to use a supported version of jboss is excluded from this
functionality until most likely 2012.
If this is not possible i would appreciate an explanation of the dependencies the
massindexer has on search 3.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira