> or a 'contrib'
> package/project/source folder? If it is in the main tree: the unit
> tests require mysql-connector.jar and assume you have a database at:
> jdbc:mysql://localhost/solrtestsql with user=solr and password=solr.
> Any suggestions on how this should be handled or structured.
I'm split on this one...
It seems like it would be nice if we didn't have any vendor specific
db stuff in the core or in the repository. On the other hand, if the
vast majority of people will be using this with mysql, why make them
go through the trouble.
Perhaps we could add an 'ext' directory to lib where we put libraries
used by many plugins, but are not essential to solr. These would
probably include:
commons-fileupload-1.1.1.jar
mysql-connector-java-5.0.4.jar
postgresql.jar (i don't actually know what it is called)
poi-2.5.1.jar
commons-csv-20061121.jar
If people are worried about a more lean distribution, there could be a
'core' and 'complete' version.
At least this would solve my current problem: where to put the
libraries for unit testing!
