Re: New highlighter package available

[Erik Hatcher]

I'll see what I can do about putting some sandbox build process 
infrastructure in place so that all projects with build.xml gets run 
from a central process.  This certainly won't happen overnight, but 
I'll put it on my to-do list, but others are welcome to beat me to it.  
Once we have a master build for the sandbox, we can integrate it into 
Gump pretty easily.  In fact, we could probably integrate the ones that 
have a build process into Gump already - although I'll have to go 
relearn Gump.

	Erik

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]