<<<Why are classpath files generally not included in open source projects?>>>
because they're always wrong <G>... 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....... 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: http://wiki.apache.org/lucene-java/HowToContribute Best Erick On Thu, Apr 15, 2010 at 5:04 PM, hkmortensen <ko...@yahoo.com> 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: > http://n3.nabble.com/Eclipse-project-files-tp708987p722342.html > Sent from the Solr - Dev mailing list archive at Nabble.com. >
