Re: Creating a complete Lucene distribution

[Jeff Linwood <je...@greenninja.com>]

Moved to Dev....

Sounds like a decent idea to me.  I can get to work on making web pages 
for some of these projects, but how many of them are still actively 
maintained?

Jeff

Otis Gospodnetic wrote:

>Hello Jeff,
>
>Thanks for offering your help.
>My take on this is that those who are new to Lucene need to get
>acquainted with the core Lucene first before they start needing things
>like stemmers for different languages, a web crawler, etc.
>
>Then as long as we make it easy for people to read and learn about each
>Sandbox project and make it easy for them to download their JARs, we
>will make it simple for them to start using those projects.
>
>Currently only Indyo and LARM projects include overview/tutorial-like
>documentation, but they do not provide pre-built JARs - the only way to
>get them is from CVS directly, which is a bit more of a pain.
>Snowball stemmers don't have any docs (do they even need them?), but
>the project includes a link to the JAR, which makes it easy for a
>developer to include it in their projects.
>
>SearchBean is buried completely, and so are all other Sandbox
>contributions and projects (circa 10 of them).
>
>If you want to help I think it would be nice to expose some of those
>contributions/projects the same way LARM, Indyo, and Snowball Stemmers
>are.
>I'm not sure if you feel like doing that, as it's not the most exciting
>work :)
>
>Thanks,
>Otis
>P.S.
>This thread may be more suitable for lucene-dev - lucene-user
>subscribers probably don't care about this type of decisions much.
>
>
>--- Jeff Linwood <je...@greenninja.com> wrote:
>  
>
>>Hi,
>>
>>Is there any interest in creating an additional distribution for
>>Lucene that
>>contains some of the code from the sandbox and the contributions?  I
>>was
>>thinking about bringing in the SearchBean, LARM, the optional
>>analyzers,
>>etc. I know there has been  some discussion on this list of what
>>should and
>>shouldn't be in the core distribution, but I would like to have the
>>option
>>to download a complete distribution.  I think this will make it much
>>easier
>>to get started developing with Lucene.
>>
>>I guess the first step would be to see if other people on this list
>>would be
>>interested in this project at all, and then the next step would be to
>>figure
>>out what could go into an application framework build (licensing,
>>dependent
>>library issues, etc.), and to work on an Ant build file that calls
>>the
>>individual component files.
>>
>>I definitely don't want to replace the existing source and binary
>>distributions of Lucene - this would be a larger, more bulky download
>>for
>>most people.
>>
>>Anyway, shoot it down if you like :)
>>
>>Thanks,
>>Jeff
>>
>>    
>>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Creating a complete Lucene distribution

[Otis Gospodnetic <ot...@yahoo.com>]

--- Jeff Linwood <je...@greenninja.com> wrote:
> Moved to Dev....
> 
> Sounds like a decent idea to me.  I can get to work on making web
> pages 
> for some of these projects, but how many of them are still actively 
> maintained?

I'd link pretty much everything in sandbox/contributions:

ant - already linked
fulcrum - functional
indyo - already linked
javascript - functional
miscellaneous - single class, functional
parsers - single PDF extractor, not sure about functionality
searchbean - already linked
snowball - already linked
webcrawler-LARM - already linked
WordNet - functional
XML-Indexing-Dem0 - functional

There is also projects/appex, but I think that is pretty much abandoned
and may get superseded by LARM.

Thanks for helping.
Otis


> Jeff
> 
> Otis Gospodnetic wrote:
> 
> >Hello Jeff,
> >
> >Thanks for offering your help.
> >My take on this is that those who are new to Lucene need to get
> >acquainted with the core Lucene first before they start needing
> things
> >like stemmers for different languages, a web crawler, etc.
> >
> >Then as long as we make it easy for people to read and learn about
> each
> >Sandbox project and make it easy for them to download their JARs, we
> >will make it simple for them to start using those projects.
> >
> >Currently only Indyo and LARM projects include
> overview/tutorial-like
> >documentation, but they do not provide pre-built JARs - the only way
> to
> >get them is from CVS directly, which is a bit more of a pain.
> >Snowball stemmers don't have any docs (do they even need them?), but
> >the project includes a link to the JAR, which makes it easy for a
> >developer to include it in their projects.
> >
> >SearchBean is buried completely, and so are all other Sandbox
> >contributions and projects (circa 10 of them).
> >
> >If you want to help I think it would be nice to expose some of those
> >contributions/projects the same way LARM, Indyo, and Snowball
> Stemmers
> >are.
> >I'm not sure if you feel like doing that, as it's not the most
> exciting
> >work :)
> >
> >Thanks,
> >Otis
> >P.S.
> >This thread may be more suitable for lucene-dev - lucene-user
> >subscribers probably don't care about this type of decisions much.
> >
> >
> >--- Jeff Linwood <je...@greenninja.com> wrote:
> >  
> >
> >>Hi,
> >>
> >>Is there any interest in creating an additional distribution for
> >>Lucene that
> >>contains some of the code from the sandbox and the contributions? 
> I
> >>was
> >>thinking about bringing in the SearchBean, LARM, the optional
> >>analyzers,
> >>etc. I know there has been  some discussion on this list of what
> >>should and
> >>shouldn't be in the core distribution, but I would like to have the
> >>option
> >>to download a complete distribution.  I think this will make it
> much
> >>easier
> >>to get started developing with Lucene.
> >>
> >>I guess the first step would be to see if other people on this list
> >>would be
> >>interested in this project at all, and then the next step would be
> to
> >>figure
> >>out what could go into an application framework build (licensing,
> >>dependent
> >>library issues, etc.), and to work on an Ant build file that calls
> >>the
> >>individual component files.
> >>
> >>I definitely don't want to replace the existing source and binary
> >>distributions of Lucene - this would be a larger, more bulky
> download
> >>for
> >>most people.
> >>
> >>Anyway, shoot it down if you like :)
> >>
> >>Thanks,
> >>Jeff
> >>
> >>    
> >>
> 
> 
> 
> --
> To unsubscribe, e-mail:  
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-dev-help@jakarta.apache.org

Re: Creating a complete Lucene distribution

[Erik Hatcher <li...@ehatchersolutions.com>]

On Tuesday, January 28, 2003, at 12:53  AM, Jeff Linwood wrote:
> Moved to Dev....
>
> Sounds like a decent idea to me.  I can get to work on making web 
> pages for some of these projects, but how many of them are still 
> actively maintained?

I'm actively maintaining the 'ant' contribution area.  In fact, in a 
few weeks I'll likely have some big enhancements committed there.  At 
that time I'll generate documentation for the Ant task that lives there 
into HTML format and we can hook that into the main pages.

	Erik


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>