Change build.xml so compiling/running the tests use the same classpath strategy as the rest

[GoogleCodeExporter]

The build.xml file has been changed recently to be more flexible about where 
the Lucene jar files are installed.
Make it so that the tasks for compiling and running the integration tests use 
the same settings for the classpath and also adapt to how the location of the 
lucene jars and junit jars are defined.

For example, to make a self-contained semanticvectors directory that compiles, 
runs and compiles and runs the unit tests, one would just have to create a 
subdirectory lib and drop in the lucene and junit jars.

Original issue reported on code.google.com by johann.petrak@gmail.com on 9 Dec 2010 at 9:35

[GoogleCodeExporter]

I have a modified build.xml for this but since there appeared to be plans to 
make a new release soon, I wont check this in until everyone is ok, to make 
sure nothing breaks.

Original comment by johann.petrak@gmail.com on 9 Dec 2010 at 9:48

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I had trouble dropping a link to JUnit into my ./lib dir - seems that the junit 
task in ant doesn't deal with classpaths in the same way as the java task.

But everything else apart from the junit task works, so I'm willing to ship 
without complete consistency here, since junit for the most part only affects a 
few developers. 

Original comment by widd...@google.com on 13 Dec 2010 at 5:21

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I have checked this in .. should not break anything and makes testing easier 
with just dropping junit into ./lib

Original comment by johann.petrak@gmail.com on 13 Dec 2010 at 10:35

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****