Re: New highlighter package available

[Hani Suleiman]

Yeah, this could probably be managed by ensuring that across versions 
of Lucene, care is taken to try and avoid breaking backward 
compatibility with plugins. Where it's unavoidable, the release notes 
should be very explicit about the old/new usage, so plugin authors can 
trivially support the latest versions.

It's pretty much the standard plugin problem, and as long as 
lucene-core shows love to those plugin authors, all is well.

On Tuesday, September 30, 2003, at 06:39 PM, [EMAIL PROTECTED] 
wrote:

My intention is for this submission to be used however you see fit.
If that's in the core or not I dont really mind.
What I would like to see however is any none-core projects that are 
considered useful having an
automated mechanism for building and Junit testing against the latest 
Lucene release.
That way when something in the core changes that breaks none-core code 
(PriorityQueue being a recent example)
the core developers are aware.

I suspect there's a number of sandbox projects that simply dont work 
with the latest release and theres
no automated build mechanism to highlight (no pun intended) problems

Cheers
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]