lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paolo Castagna <>
Subject Re: Eclipse project files...
Date Thu, 15 Apr 2010 21:40:26 GMT
Erick Erickson wrote:
> <<<Why are classpath files generally not included in open source
> projects?>>>
> because they're always wrong <G>...

It is possible to get it right and when it happens users will have a
much better experience when they checkout the sources of a project.

Just a few examples of things I use:


With Maven and/or Ant+Ivy it's possible to generate Eclipse .classpath
and .project files automatically from your pom.xml file or from your
ivy.xml (Hadoop does that).

> If I put mine in c:\apache, and you put yours in c:\trunk, our classpath
> files will reflect that. And I *really* don't want to update the project and
> get my classpath file overwritten with yours.
> Not to mention that I *actually* work on a mac, where Ant has been
> installed in /usr and.......

The examples above work on Linux, Windows and should work on Mac OS X as
well, there are no absolute paths in the .classpath or .project files.

> Not to mention other libraries. And what about plugins?
> That said, one *can* include a sample classpath and, perhaps, project
> file,  that can be copied to "the correct place" and changed to reflect the
> local setup as has been done on the Wiki, see:

Eclipse .classpath and .project files can be checked into the source
code repository or they can be generated as part of the building system.

I'd love to have the same good experience with Lucene and Solr... I am
still having problems trying to configure Eclipse to run Solr tests (and
yes, I've changed the current directory... but I still have problems).


> Best
> Erick
> On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen <> wrote:
>> I spend about two days last week to import lucene and solr in eclipse. I
>> would not call it easy at all. I took the test sources away completely
>> (from
>> the source path).
>> I would like to help putting some useable project files for eclipse
>> together
>> (including the test files ;-) ).
>> Why are classpath files generally not included in open source projects?
>> Would they do any harm? I realise when you get experienced with the
>> software
>> you want to make it slim to make text search faster. But for new people in
>> a project it would be a lot nicer, I think.
>> Is there any way of distribute work on the solr project? I would not like
>> to
>> do a lot of effort to adapt to eclipse if somebody else does it the same
>> time
>> --
>> View this message in context:
>> Sent from the Solr - Dev mailing list archive at

View raw message